EMBY and PLEX SSL and port issue for external

csjjpm

Contributor
Joined
Feb 16, 2015
Messages
126
I have a commercial SSL certificate for my domain which worked fine in my JAIL yesterday. I've updated to SCALE today and installed an emby container but I seem to be stuck on 9096 as the only port and my SSL certificate is no longer considered valid.
If I try https://mydomain.com:9096 I get an "SSL_ERROR_RX_RECORD_TOO_LONG" error. I am using the same PFX file and password as yesterday. This is also happening with Plex. I've tested the certificate and extract keys and created pem files to check the password is correct.

The Plex issue seems to be that the certificate is overwritten by Plex.tv themselves with a LetsEncrypt one so I've sent them logs.

The emby issue seems to be to do with a naming conflict between the certificate for my domain and how it is redirected in the container, it has gone to host1 when I'd expect mydomain.com
2023-03-14 20:28:26.231 Info Server: http/1.1 POST http://host1:9096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=1576cd04-5e0d-4229-9ca5-09a054a6beb5&X-Emby-Client-Version=4.7.11.0&X-Emby-Language=en-gb&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
2023-03-14 20:28:26.233 Info Server: http/1.1 Response 204 to host2. Time: 1ms. http://host1:9096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=1576cd04-5e0d-4229-9ca5-09a054a6beb5&X-Emby-Client-Version=4.7.11.0&X-Emby-Language=en-gb&reqformat=json
 

csjjpm

Contributor
Joined
Feb 16, 2015
Messages
126
I think this can be resolved by Traefik if I can work out how to configure it
 
Top