Emby not using assigned folders after 3.3.0.0 upgrade

[PortableStick 1]

I've got a server that's been running Emby, Nextcloud, and a couple other services for over a year now.  It's all been flawless until yesterday.  Everything runs behind an Nginx proxy.  Nextcloud is running great, but Emby has become very slow to load, and the front page only loads the My Media section.  The error I get in my console is:

Firefox can’t establish a connection to the server at wss://<<my.domain>>/embywebsocket?api_key=<<mykey>>&deviceId=<<my device id>>

Safari and Chrome give me similar errors.  The Nginx logs don't say much, but I checked Emby's, and noticed this:

System.IO.DirectoryNotFoundException: Could not find a part of the path '/var/lib/emby-server/metadata/library/f1/f137a2dd21bbc1b99aa5c0f6bf02a805/poster.png'.

It's strange that it should be looking in there since the path in my configuration is `/var/lib/emby/`. 

 

 

I tried reverting to 3.2.6.0, but I get the same problem.  Is there some other place that this setting lives which would override what's on the admin page?

 

Any help here is appreciated.

[Luke 42078]

hi, for the metadata path, when you change the setting it only applies to new items going forward. there might be items in the database with those paths saved pointing to the old folders. usually a library scan will clear it up.

[PortableStick 1]

Rather than do the scan, I just copied my `/var/lib/emby/` directory to `/var/lib/emby-server`, but the larger point here is that I didn't make any changes.  I didn't do anything other than upgrade Emby to 3.3.0.0.

 

Now the path exception is gone from the logs, but I'm seeing

System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> Interop+OpenSsl+SslException: SSL Handshake failed with OpenSSL error - SSL_ERROR_SSL. ---> Interop+Crypto+OpenSslCryptographicException: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown

and

2018-02-26 12:21:12.061 Error HttpServer: Could not find handler for /embywebsocket

[Luke 42078]

I think you may have originally installed using our legacy install package, and rather than continue to update using apt-get update, you installed our new package over the top. It has some differences and they are separate installations.

 

As far as ssl can you please attach the complete emby server log? thanks.

[PortableStick 1]

I think you may have originally installed using our legacy install package, and rather than continue to update using apt-get update, you installed our new package over the top. It has some differences and they are separate installations.

 

 

That is indeed what I did.  Do you have a recommended way of resinstalling?  I tried `apt remove emby-server && dpkg -i emby-server.3.3.0.0.deb`, which seemed to have worked, but I'm getting a 502 response from Nginx.

 

 

I've attached my most recent log.  Thanks for your help so far!

[Luke 42078]

Did you forget to attach the log?

[PortableStick 1]

Apparently, I did.

log1 copy.txt

[Luke 42078]

So you're unable to receive traffic over https right?

[PortableStick 1]

Yes, but only when accessing Emby.  When I connect without https, I'm still not seeing my media, though it seems to not have a problem with the websocket connection.

[Luke 42078]

You might just need to remove your libraries and re-add them. At this point it's just hard to guess what the problem might be. You've essentially combined two install packages, moved the program data folder, etc. It's just a lot of variables to deal with here.