Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response status code does not indicate success: 403 (Forbidden) #317

Open
shapman88 opened this issue Mar 30, 2024 · 3 comments
Open

Response status code does not indicate success: 403 (Forbidden) #317

shapman88 opened this issue Mar 30, 2024 · 3 comments

Comments

@shapman88
Copy link

I began seeing the below error message this morning when trying to download single posts or scrape an entire account. I confirmed that my auth information is correct and that I have not been logged out, but this seems to be happening randomly in between items that get downloaded. I am using version 1.7.52.

StackTrace: at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at OF_DL.Helpers.APIHelper.GetDRMMPDPSSH(String mpdUrl, String policy, String signature, String kvp, Auth auth)
Exception caught: Response status code does not indicate success: 403 (Forbidden).

image

@banjobbw
Copy link

banjobbw commented Mar 31, 2024

Im also getting a similar error

Exception caught: Response status code does not indicate success: 500 (Internal Server Error). StackTrace: at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OF_DL.Helpers.APIHelper.GetMedia(MediaType mediatype, String endpoint, String username, String folder, Auth auth, List 1 paid_post_ids)

@MussInBootss
Copy link

I'm getting the same error: An error occurred: Response status code does not indicate success: 403 (Forbidden)
I'm using the latest version and even tried with version OF.DL.V1.7.44 which used to work before. For some reason it'll download some posts but then reaches a point where it keeps repeating this error several dozen times.
I've got all the DRM files and it worked fine 6 weeks ago but I haven't tried it since.

@ducmic
Copy link

ducmic commented May 11, 2024

I've got the same in V1.7.56, but what's worth noting is that it happens randomly.

The same URL for instance, for a single-URL download, will give this 403 error, then upon retrying it will work without trouble.
Runing a full scrape on a single account will yield, in my case, roughly 30% of the content, the rest being subjected to 403 error. Then re-running the same full scrape will yield an additionnal roughly 15% of the content.
Not sure running the full scrape repeatedly will lead to a ban, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants