Jump to content

Emby ssl ports not working


blim5001

Recommended Posts

So this is a bit wierd, emby on my nas was all working fine over https until this google outage this morning. (Why this should make a difference, no idea, but it's the only thing that has changed)

Now it does not seem to be working. I have tried the default port (8920) and the one I want to use: (9920)

And it does not seem to be listening on either of these ports.

If I run a port checker on my local network the port does not appear to be listening (and fwiw I see no mention of the https port in the start up logs)

I have disabled the firewall on the nas, but it has made no difference.

I have rebooted the nas and reinstalled emby, again these made no difference

The 9920 port is listed in my config file

I have to admit I am confused.

Before I would see these lines:

2020-12-04 19:36:21.263 Info App: Adding HttpListener prefix http://+:8196/

2020-12-04 19:36:21.263 Info App: Adding HttpListener prefix https://+:9920/

 

But now I only see:

2020-12-14 13:26:52.310 Info App: Adding HttpListener prefix http://+:8196/

the second line is missing...

Link to post
Share on other sites

Have just tried uninstalls and reinstalls of both the current version and the beta, and it just will not add a listener for the https port...

And netstat does not show the port in use either, so it's not like it is already tied up

Edited by blim5001
Link to post
Share on other sites

Yep I have a certificate and it was working all ok earlier.

although should it still not listen on the ssl port even without a cert.

As if I choose to uncheck the 

Allow remote connections to this Emby Server.

Then it still allows me to set both https and http ports. (But I do not have the option to set a certificate)

I have my:

Local HTTPS port number:

set to 9920

Link to post
Share on other sites

You need to either setup an SSL certificate or a reverse proxy, or you won't be able to use https.

The certificate option is about in the middle of the network settings screen, so look there.

Link to post
Share on other sites

doh, what a duffer I am...

I had the wrong filename in the:

Custom SSL certificate path:

cx-emby.px rather than cx-emby.pfx

But why it was working previously, no idea. I guess I must of changed it accidentally, or renamed the file accidentally.

Thanks for your time.

 

 

Edited by blim5001
Link to post
Share on other sites

As an aside in trying to solve my problem I upgraded to the beta version and then rolled back to the current release.

From emby-server-synology_4.5.3.0 -> emby-server-synology_4.6.0.8 -> emby-server-synology_4.5.3.0

Will this cause me problems, as I saw in another thread you cannot rollback due to DB changes?

Thanks

Link to post
Share on other sites
Quote

Will this cause me problems, as I saw in another thread you cannot rollback due to DB changes?

We haven't tested this ourselves, so we don't know for sure, but probably you will have issues, yes.

Link to post
Share on other sites

ahh, ok.

From what I can see so far, It appears to be ok, but will take that into consideration.

If it does start to play up I will consider installing the beta again.

Thanks 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...