Jump to content

Subtitle download not working after last update (3.2.0.0)


Loggy
Go to solution Solved by Luke,

Recommended Posts

I'm on Synology 216+2 and after the last update (version in Emby gui 3.2.0.0, Package Manager reports Emby version 3.2.0.0-1) no subtitles get downloaded. I have reentered my opensubtitles login information and  restarted Emby but without success. I'am able to login to opensubtitles web site with the same credentials without problem. I ran the scheduled task "Download missing subtitles" and the log file reports error message "forbidden"...

 

 

I have some more errors in the log file but they existed before the last update and I have no clue why they appear there.

 

EmbyLog.txt

Link to comment
Share on other sites

Not sure about the previous version numbers but I installed Emby in january and have upgraded two times almost immediately when new versions have been presented in Synology Package Manager.

I've just confirmed that it's working in Kodi but not in Emby.

Link to comment
Share on other sites

solabc16

Hello @@Loggy

 

Release 3.2.1.0-1 will now be available in Package Center. Once you've updated, can you confirm if this issue is still present.

 

Best

- James

Link to comment
Share on other sites

Hello @@Loggy

 

Release 3.2.1.0-1 will now be available in Package Center. Once you've updated, can you confirm if this issue is still present.

 

Best

- James

James, it's still present.

 

Yesterday I installed 3.2.1.0 on my laptop (Win10) and that installation does not have this problem. Unfortunately I dont want my laptop to be my media server :).

Link to comment
Share on other sites

Uninstalled Emby today... did a new install... changed password on opensub... changed ip-address on Synology... same result... forbidden. It still works on my laptop...

Link to comment
Share on other sites

solabc16

Hello @@Loggy

 

Sorry to hear you're still having problems. From the platform side, there were no changes in the most recent release, so this would appear to be related to the Emby Server release itself.

 

If possible, can you send us your support logs using the procedure detailed on the Wiki here: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs

 

I just need the file reference you'll get when the process completes.

 

Best

- James

Link to comment
Share on other sites

Hello @@Loggy

 

Sorry to hear you're still having problems. From the platform side, there were no changes in the most recent release, so this would appear to be related to the Emby Server release itself.

 

If possible, can you send us your support logs using the procedure detailed on the Wiki here: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs

 

I just need the file reference you'll get when the process completes.

 

Best

- James

Sendlogs_LOGGY_synology_braswell_216+II_20170214T164255UTC.tgz

 

Thanks

//@Loggy

Link to comment
Share on other sites

@@solabc16, just for a little context on this, about 4-6 weeks ago we started seeing http request failures with OpenSubtitles. It turns out their was some kind of issue with OpenSubtitles server. Users found a workaround by adding a hosts file entry that maps api.opensubtitles.org to 92.240.234.122. After some research, this IP appears to be owned by OpenSubtitles.

 

So I followed up and updated the server to use that exact IP address instead of the domain name and things started working again. A few weeks later, the domain name started working again so I updated the server to use the proper domain name rather than the IP Address.

 

If he happened to be one of the users who updated his hosts file, then that could explain his issue as it should probably be changed back. I'm guessing not though, because I'm assuming he would have mentioned it. So the server has gone back to using the domain name as that appears to be working now, except now we have Loggy reporting that it's not.

Link to comment
Share on other sites

@@solabc16, just for a little context on this, about 4-6 weeks ago we started seeing http request failures with OpenSubtitles. It turns out their was some kind of issue with OpenSubtitles server. Users found a workaround by adding a hosts file entry that maps api.opensubtitles.org to 92.240.234.122. After some research, this IP appears to be owned by OpenSubtitles.

 

So I followed up and updated the server to use that exact IP address instead of the domain name and things started working again. A few weeks later, the domain name started working again so I updated the server to use the proper domain name rather than the IP Address.

 

If he happened to be one of the users who updated his hosts file, then that could explain his issue as it should probably be changed back. I'm guessing not though, because I'm assuming he would have mentioned it. So the server has gone back to using the domain name as that appears to be working now, except now we have Loggy reporting that it's not.

Yes, I can confirm that I have not changed the hosts file. And I'm sure the domain name works too, cause I have tested it with some other programs and as I mentioned in a previous post, it (Emby) works on my Windows laptop. My guess is that it has something todo with...

-password saved incorrectly from the GUI (Though I have changed the password from both iPad and Windows with no luck)

-encryption/decryption of the password

-no authentication call

-something with the token handling

-....

Link to comment
Share on other sites

Well those other applications may be using the ip address, or may have been using it. In my research googling around, we are not the only ones who switched to the ip address while the server was having issues.

Link to comment
Share on other sites

Well those other applications may be using the ip address, or may have been using it. In my research googling around, we are not the only ones who switched to the ip address while the server was having issues.

True, but I downloaded the source code to one and it used the domain name. I built it in Visual Studio, did some tests and it worked. I switched to the ip-address but that did not work. I don't remember why and I didn't do any research why.

Link to comment
Share on other sites

Yes, I can confirm that I have not changed the hosts file. And I'm sure the domain name works too, cause I have tested it with some other programs and as I mentioned in a previous post, it (Emby) works on my Windows laptop. My guess is that it has something todo with...

-password saved incorrectly from the GUI (Though I have changed the password from both iPad and Windows with no luck)

-encryption/decryption of the password

-no authentication call

-something with the token handling

-....

I can confirm that the password stored in the xml-file is correct after decryption...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...