HTTPS not working after update to 4.4.0.40-1

[432r90f34f34 0]

After updating to 4.4.0.40-1 HTTPS is not working anymore. Emby is only available via HTTP. There is no information about anything related to HTTPS (port, key, etc.) in the logs.

 

Model: DS1019+

Logs: sendlogs_nas_synology_apollolake_1019+_20200404T073930UTC.tgz

 

admin@nas:~$ wget http://localhost:8096
--2020-04-04 09:41:34--  http://localhost:8096/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:8096... connected.
HTTP request sent, awaiting response... 302 Found
Location: web/index.html [following]
--2020-04-04 09:41:34--  http://localhost:8096/web/index.html
Reusing existing connection to localhost:8096.
HTTP request sent, awaiting response... 200 OK
Length: 2579 (2.5K) [text/html]
Saving to: 'index.html'

index.html                                  100%[========================================================================================>]   2.52K  --.-KB/s    in 0s      

2020-04-04 09:41:34 (173 MB/s) - 'index.html' saved [2579/2579]

admin@nas:~$ wget https://localhost:8920
--2020-04-04 09:41:49--  https://localhost:8920/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:8920... failed: Connection refused.

 

[Luke 37057]

Hi, you're trying to do https on localhost?

[432r90f34f34 0]

That's not the issue. As stated before, HTTPS was working, after update it's not anymore. It doesn't matter if I'm calling localhost or the lan interface, because emby is bound to both interfaces.

The least I would expect here is that wget returns with a certificate problem, but it's not emby is not bound to port 8920 but it should, so something is wrong during startup.

admin@nas:~$ wget http://192.168.178.2:8096
--2020-04-05 09:29:15--  http://192.168.178.2:8096/
Connecting to 192.168.178.2:8096... connected.
HTTP request sent, awaiting response... 302 Found
Location: web/index.html [following]
--2020-04-05 09:29:15--  http://192.168.178.2:8096/web/index.html
Reusing existing connection to 192.168.178.2:8096.
HTTP request sent, awaiting response... 200 OK
Length: 2579 (2.5K) [text/html]
Saving to: 'index.html'

index.html                                  100%[========================================================================================>]   2.52K  --.-KB/s    in 0s      

2020-04-05 09:29:15 (151 MB/s) - 'index.html' saved [2579/2579]

admin@nas:~$ wget https://192.168.178.2:8920
--2020-04-05 09:29:20--  https://192.168.178.2:8920/
Connecting to 192.168.178.2:8920... failed: Connection refused.

Edited April 5, 2020 by 432r90f34f34

[Seger 110]

Maybe stupid question, but:

 

 

 

Did you integrate the certificate into the Emby dashboard?

 

-> the path may not be correct after the update.

 

 

 

Anyway, ask me how you did it in Emby Dashboard under Synology. Did you ensure that the certificate is linked from the internal paths and that it is still valid?

 

 

 

I can understand @@Luke frag that there is always a message from the internal IP on https that is not valid. Did you enter a DDNS address or a fixed IP?

 

 

 

I use a proxy reserve to access Emby via HTTPS, this works correctly even after the update.

 

 

 

Many greetings,

 

Seger

[432r90f34f34 0]

Okay, I think that's it. The path is still there but the key-cert-bundle is not, so probably that's the issue. But I would expect an error message in the log in this case.

[Seger 110]

Okay, I almost thought so. Actually, you would expect Synology to be better or more customer-friendly . Do yourself a favor and solve it through a backup proxy. You can find it in Control Panels->Applications.

 

 

 

Then you don't have to keep the certificate in one place and everything will run as long as the certificate is valid.

 

 

 

You enter your external https port first and redirect to your internal http port.

 

 

 

If you have any further questions I am at your disposal.

 

 

 

Many greetings,

Seger

[FrostByte 5049]

Actually, you would expect Synology to be better or more customer-friendly . 

 

LOL.  If you and James worked at Synology the world would be a much better place.