Upgrade to 3.2.35 broke stuff.

[mythman 5]

OK maybe I should have known since it had not appeared in the repo as normal upgrade but I thought why not it was bugging me to upgrade anyway. So downloaded and installed the 3.2.35 deb and all seemed ok, until I went to look at my library and found all my Movies and Music and TV Shows had vanished. That is they would not show on the home page. Collections were there and Podcasts but nothing else.

 

So panicking I decided to downgrade to 3.2.34.0+60.1, but nothing changed. So knowing I had system backups I thought stuff it I would  uninstall and reinstall emby.

 

So that went ok. Except all of a sudden I cannot connect to it over port 8290 using SSL or using the hostname over 8096 only the ip address.

 

According to the logs it is listening on the right ports I think:

2017-11-02 01:35:25.194 Info HttpServer: Adding HttpListener prefix http://+:8096/
2017-11-02 01:35:25.196 Info HttpServer: Adding HttpListener prefix https://+:8920/

But when I look at the Dashboard is does not show it running https

 

 

 

I cannot see any errors in the log it just refuses to start SSL on port 8920 and also refuses to allow connections to http://hostname:8096, only http://w.x.y.x:8096 ?

 

What is going on ?

[Luke 37191]

Hi, check your settings under Advanced and make sure that you've enabled requiring of https. Thanks.

[mythman 5]

I did restore from backup so it should have been the same.

 

 

[Luke 37191]

The settings changed slightly from these versions so you'll need to check the box to require https.

 

Additionally, we won't allow you to require https unless you provide a trusted SSL certificate such as LetsEncrypt.

[mythman 5]

 

The settings changed slightly from these versions so you'll need to check the box to require https.

 

Additionally, we won't allow you to require https unless you provide a trusted SSL certificate such as LetsEncrypt.

 

Trouble is I have no intention of opening up to the internet I have it on a VPN and LAN instead. So self signed certs are no longer supported or supplied?

[Luke 37191]

If you're only using it on a LAN then why use ssl at all? 

 

We're not supplying a self signed cert at this time but there are plenty of tools to create one. The reason we don't want to bother with it anymore is because most devices will reject the self signed cert and it just creates a lot of connection-related troubleshooting for us if there's no way for us to force a device to accept it.

[mythman 5]

Regardless if it is on a LAN or not using SSL is just good network etiquette. You never know WHO will be sniffing your WIFI or logging your traffic. So yes SSL is default on EVERYTHING on my network from the routers to my PBXI. I don't really care if I have to add my own CA to list because it is MY CA and I can.

 

Bottom line is if I create a self signed cert with openssl and put in place with a certificate.pfx like described will it work? If not, why not?

 

I just don't know why the behaviour has changed from earlier versions. it makes the OOTB experience of Emby just that little bit less professional.

[Luke 37191]

It will work if the devices and apps you use accept the SSL cert. That is really the deciding factor.

[Luke 37191]

I just don't know why the behaviour has changed from earlier versions. it makes the OOTB experience of Emby just that little bit less professional.

 

I don't really understand. What is the value of a self signed cert if you're just going end up with a connection failure when you try to use it? And again, it's not possible to force all devices to accept it so in most cases it is out of our control.

 

I respectfully disagree with your comment about professionalism. I think it would be less professional of us to provide a feature that many will feel "only half works". So now it will work perfectly, so long as you provide a cert.