You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When scraping a profile, I sporadically get HTTP 403 errors when attempting to download various bits of media. These pop up both in post and message scrapes. The errors are not necessarily successive. In other words if I am scraping successive posts/messages A, B, and C then I may get a 403 on post/message B media but have success scraping posts/messages A and C. I am scraping behind ProtonVPN, and have encountered this issue with their DNS filter turned both on and off.
Configuration
App type: Docker image
Version: 1.7.83
CRM: not configured
Anyone who is familiar with the codebase have any guidance on this? I saw a similar issue reference in #543, but the issue was resolved by the user using the latest release of the project at the time. I'm currently using the latest release.
Description
When scraping a profile, I sporadically get HTTP 403 errors when attempting to download various bits of media. These pop up both in post and message scrapes. The errors are not necessarily successive. In other words if I am scraping successive posts/messages A, B, and C then I may get a 403 on post/message B media but have success scraping posts/messages A and C. I am scraping behind ProtonVPN, and have encountered this issue with their DNS filter turned both on and off.
Configuration
App type: Docker image
Version: 1.7.83
CRM: not configured
Example
This was a trial scrape on a free subscription account which was not scraped before.
The text was updated successfully, but these errors were encountered: