-
Notifications
You must be signed in to change notification settings - Fork 54
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
Comments
Im also getting a similar error
|
I'm getting the same error: An error occurred: Response status code does not indicate success: 403 (Forbidden) |
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. |
I am also getting the same as the others in this thread. I am using version 1.7.58 |
Are you using your own Wildvine keys or CDRM Project? |
I am also receiving the same error message: StackTrace: at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() I tried using both CDRM Project and my own keys. |
Well, upon retrying later, my random issue disapeared. Since I'm using CDRM, I assume it was a temporary problem on that side. |
Try with/without a VPN. If you have your own keys, I would always use them to remove CDRM as a potential source of problems. |
how do you get your own keys/wildvine/whatever? |
|
Also tried again. This time without VPN and it worked. |
thanks! but that doesn't seem to be the issue. I can download the streams manually with FetchV, but the downloader still immediately throws that error |
Did you use "OF-DL Auth Helper" (that browser extension) to generate the Try to delete those unnecessary |
I've not seen that myself, so if it does help, it's an edge case. |
Are you all on 1.7.59 now? It's the only release that has come out since a recent OF update that required a new release on our end. |
Yes, I'm on 1.7.59 now and this issue persisted from 1.7.57. I can also reproduce this issue and fix it again with my mentioned solution in my environment. On my Firefox, that extension will also save the |
Mine looks like the following: {
"USER_ID": "REDACTED",
"USER_AGENT": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36",
"X_BC": "REDACTED",
"COOKIE": "csrf=YZe1QVva156e747ed1c791d9327931ed24cebbe8; __stripe_mid=58e47573-8d67-440d-8f41-40af27ca40822d0076; lang=en; auth_id=REDACTED; fp=1869e2a74cd6c595090f4dfbebe0e288c03492b6; sess=12ogjugrui95s73tc5evl7rubm; auth_uid_REDACTED=EN86KebL5oe2iwa5WxZHQrFgZ4ei0CDS; st=9d6d33fed82d7d3a91398053192eda9268cfc63d7f3d8ea9ffe4c37765e0cacc; __cf_bm=Dw.FJ35z4.ZifHwPRwA1tfOB_2_OyregVvMB7yMI_x4-1715904653-1.0.1.1-61XXcqLZ5RPuDAN9VfSIalVUQtz9mFUI6qbHakhT.HQVSil5rSVnnlOroMEJdOnr8veGnjUuHqJZS.xfzit.6w; _cfuvid=DzYb3ZdWvug1RduCy0BDlXCaUeBnvdz5chVSXFEg5SE-1715904654000-0.0.1.1-604800000; streams=dc1-room-7rFMwun8uXge6s1_; __stripe_sid=7db7c4a4-409d-441f-b533-c4afdd60f515b91644;"
} |
no change, but getting a different error today. and the ffmpeg could not save the file |
I changed the cookie to only have "sess" info and it stopped giving this error. I was using the of cookie helper before. |
seems to work now edit: nevermind, it's back |
Tried this workaround, but I am still getting the same error. I have all the DRM files as well |
Its back again, but this time with just auth failure. Both manually added values and browser extension.
|
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).
The text was updated successfully, but these errors were encountered: