-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
opensubtitles.org API available only for logged users #51
Comments
This is my output today:
|
So register on opensubtitles.org, add the username and password to lines 61 and 62 of OpenSubtitlesDownload.py. |
I tried to use OpenSubtitlesDownload.py for the 1st time today because for quite a while now when I've tried to get subs via Kodi it's failed and I finally decided to try another method. I already registered with opensubtitles.org so when I opened the script to see how it worked and saw you can (or need to) enter a username and password, I went ahead and added them. Even though I've done that, when I try to use the script I get the same messae as ManuLinares has reported. Now... this might be related but I'm not sure... Australian ISPs are now required to block access to opensubtitles.org (as well as other subtitle services) so I'm running openvpn to tunnel out of Australia. Currently I have openvpn set to the US so when I use: I don't know why this is happening or what it means or whether it might explain why the OpenSubtitlesDownload.py script isn't working for me but I thought I should mention it just in case. Any help would be appreciated. |
Same thing happened to me today, 401 errors solved by using my account. |
Just some info regarding using an OpenSubtitles account. For me this didn't work if I had some long password with underscores like "batboy_cost_smudge_cornbread_overlying_vertical_alto". I'm not sure if this is the issue with the script itself, because the login did work on OpenSubtitles web page with that long password. When I changed the password to something shorter, with no underscores the script started working again. |
Allright thanks for the report, I"ll have a lot at this issue tomorrow! |
Ok it looks like OpenSubtitles actually limits password to 32 characters, the other ones are just cutted, so I did the similar thing and you should now be able to use long password with underscore again. I also took this opportunity to improve the 401 error handling. Now there should be a proper explanation directly in the application, indicating how and why the log in is required. |
Hi thanks a lot for your effort! I can confirm it works now with longer password. |
Just letting you know that since I posted my comment, I found out that Australia has started blocking subtitle providers. So my local machine which runs kodi and I used to use to grab subs is not able to connect to opensubs or any other block subtitle site. Now I'll either have to download them to my seedbox and then transfer them to the local machine afterwards (which is what I've been doing recently) or I have to run openvpn on the kodi box so that I can get around the blocks and gain access to the subs sites. |
In France changing the DNS used in the computers or directly in the routers is usually enough to bypass blocked sites, maybe that's worth a try? |
opensubtitles.org is no more, and neither is this issue. |
Here is a communication from opensubtitles.org
Following a recent policy change from opensubtitles.org, the API is now available only for logged users.
To continue using applications like OpenSubtitlesDownload you simply need to:
Updated
Now as far as I can tell, most users are experiencing these 401 errors, if not every users.
Maybe this limitation triggers only for softwares with high volume of requests, for instance I cannot use kodi embedded subtitles downloader without using an account, but I've been using OpenSubtitlesDownload without account from the same IP.
So let's use this thread to discuss issues with using accounts.
Let me know if you've had success with OpenSubtitlesDownload without using an user account, or if you needed to set one up!
The text was updated successfully, but these errors were encountered: