Tripadvisor Reviews Scraper
Pricing
$2.00 / 1,000 reviews
Tripadvisor Reviews Scraper
Get and download reviews for chosen places on Tripadvisor. Extract the review text, URL, rating, date of travel, published date, basic reviewer info, owner's response, helpful votes, images, review language, place details. Download reviews in XML, JSON, CSV.
4.3 (6)
Pricing
$2.00 / 1,000 reviews
95
Total users
4.6K
Monthly users
550
Runs succeeded
98%
Issues response
15 hours
Last modified
2 days ago
The worker is returning an error and is not working anymore.
Closed
We got those messages from the apify last runs:
{"type":"run-failed","message":"Actor run did not succeed (run ID: jH1Jt4LVyhJ3HzScE, status: FAILED)."}
{ "error": { "type": "run-failed", "message": "Actor run did not succeed (run ID: jH1Jt4LVyhJ3HzScE, status: FAILED)." } }
statistiche.bi
2025-07-15T08:52:35.879Z ACTOR: Pulling Docker image of build dIWwDfemJz93TftKL from registry.
2025-07-15T08:52:35.881Z ACTOR: Creating Docker container.
2025-07-15T08:52:36.064Z ACTOR: Starting Docker container.
2025-07-15T08:52:36.277Z Will run command: xvfb-run -a -s "-ac -screen 0 1920x1080x24+32 -nolisten tcp" /bin/sh -c npm run start:prod --silent
2025-07-15T08:52:37.560Z INFO System info {"apifyVersion":"3.1.15","apifyClientVersion":"2.8.4","crawleeVersion":"3.7.2","osType":"Linux","nodeVersion":"v20.19.3"}
2025-07-15T08:52:37.832Z ERROR Did not expect property useApifyProxy to exist, got true in object rest
2025-07-15T08:52:37.833Z ArgumentError: Did not expect property useApifyProxy to exist, got true in object rest
2025-07-15T08:52:37.834Z at ow (/home/myuser/node_modules/ow/dist/index.js:33:28)
2025-07-15T08:52:37.835Z at new ProxyConfiguration (/home/myuser/node_modules/apify/proxy_configuration.js:98:26)
2025-07-15T08:52:37.836Z at parseConfiguration (file:///home/myuser/dist/input/configuration.js:52:35)
2025-07-15T08:52:37.836Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-07-15T08:52:37.837Z at async main (file:///home/myuser/dist/main.js:13:20)
2025-07-15T08:52:37.838Z at async /home/myuser/node_modules/apify/actor.js:153:23
2025-07-15T08:52:37.838Z at async file:///home/myuser/dist/entrypoint.js:4:1
Hi, thanks for reporting this!
The Actor is now fully up and running again. The issue was caused by a feature that accidentally made it past testing — sorry about that! We’ve fixed it and are making sure it doesn’t happen again.
