Emby SSL port disappeared all the sudden?

[rechigo 364]

Of course this has to happen the night before a trip. The only time I ever have issues I can't figure out is always last minute. Please help me. I'm sure I'll figure out what's wrong 5 minutes after posting this and making myself look like an idiot. I'm stressing out right now.

I am no longer able to access my Emby server remotely. The web dashboard reports only "Running on http port 8096", and my remote address is http://mydomain.com:8096 (normally its https://mydomain:443). I am unable to access server via 443 remotely or locally. I confirmed I can start another service on port 443 on my server and access it remotely. This has to be some weird Emby issue but I genuinely don't know what's wrong.

Why is there NOTHING in the logs indicating Emby even tries to bind to port 443? No mention of access errors to SSL, literally zero errors relating to the web server. Why is Emby refusing to listen on this port?

 

UPDATE: FIXED. when I was messing around my compose a while back, I must have accidentally deleted the bind-mount containing my certfile. For some reason the error message wasn't found in my initial logs, only in a later log file did I find the message that my certfile was missing. LOL. Like I said at the beginning of the post.. 5 minutes after posting on the forum I find the stupid mistake I made and fix it. 

embyserver.txt

Edited November 15, 2025 by rechigo

[Q-Droid 989]

For future reference the only time the Emby server will complain about the certificate is during startup. Messages related to the cert will not show up in rotated logs so to troubleshoot this type of problem your first step should be to restart the server and review the new log.

 

 

 

 

[rechigo 364]

6 hours ago, Q-Droid said:

For future reference the only time the Emby server will complain about the certificate is during startup. Messages related to the cert will not show up in rotated logs so to troubleshoot this type of problem your first step should be to restart the server and review the new log.

 

 

 

 

That's what got me though.. I checked the most recent log file (the embyserver.txt it created at startup) and didn't see it... either something weird was going on behind the scenes or (more likely) I was tweaking out and made a typo when trying to search the path to my certfile in the logs I was tired, it was like 3:30 AM and I was about to lose it. 

[Luke 42077]

Thanks for following up.