Jump to content

Emby Server HTTPS stops responding


runtimesandbox
 Share

Recommended Posts

runtimesandbox

I posted about this a few months back.

I use https externally to access my library away from home. Internally I use the normal port

 

Occasionally the server will stop responding altogether on the https port and I get the error no response from server

 

If I connect via a vpn and try the local connection the server is running fine. I have to restart emby from the command line to get it to work.

 

Is anyone else having this issue? What logs can I upload to help identify this issue?

 

I'm running Ubuntu server 14.04 Lts 64bit and the latest emby server stable

Link to comment
Share on other sites

runtimesandbox

It's currently online with the external access not working. I'll get these logs to you when I'm next back with the server

Link to comment
Share on other sites

runtimesandbox

Okay so there are 5 different log files which are all huge. They also contain my IP so I would rather not post them.. is there anything I should be looking for in particular? 

Link to comment
Share on other sites

runtimesandbox

I just reinstalled a fresh copy of the server on Debian 8.3 64bit

 

The same thing appears to happen here. I can access it via the internal IP fine, however when going to the external address it will work, 5 mins later its not responding. To get it to work again I have to reboot.

 

I've not managed to find a pattern to cause this to stop working yet, sometimes it doesn't happen for a week. sometimes a few days. Can I DM you a link to the logs?

 

EDIT: I am also now using a proper SSL certificate. 

Edited by spudy12
Link to comment
Share on other sites

Can you connect to https:// internally?

Are you NAT'd and if so are you statically forwarding ports or trying to do it dynamically?

Link to comment
Share on other sites

I posted about this a few months back.

I use https externally to access my library away from home. Internally I use the normal port

 

Occasionally the server will stop responding altogether on the https port and I get the error no response from server

 

If I connect via a vpn and try the local connection the server is running fine. I have to restart emby from the command line to get it to work.

 

Is anyone else having this issue? What logs can I upload to help identify this issue?

 

I'm running Ubuntu server 14.04 Lts 64bit and the latest emby server stable

 

Have you seen "netstat -anoe" inside the server after the problems occurs?

 

As I reported in http://emby.media/community/index.php?/topic/31100-emby-isnt-closing-used-network-ports/ and asked for help in http://emby.media/community/index.php?/topic/31259-i-need-help-reproducing-an-inssue-anyone/ (but nobody helped) , I've noticed that Emby has some problems closing it's network ports in some cases.

 

After lots of open simultaneous ports, the server stops responding correctly (too much load)

 

 

In my case, only restaring Emby service resolves the issue (temporarily).

 

Can you try to reproduce that?

Edited by anderbytes
Link to comment
Share on other sites

runtimesandbox

Thanks, I'll keep an eye out next time the issue happens. I've checked whilst it currently is working and it is closing the ones after i close a session but it maybe that it only happens under certain conditions?

 

Next time i loose access I will check this out.

 

Do you loose access on both the 8096 and 8920 ports? are you using ssl on the 8920 port?

What OS are you running?

Link to comment
Share on other sites

Thanks, I'll keep an eye out next time the issue happens. I've checked whilst it currently is working and it is closing the ones after i close a session but it maybe that it only happens under certain conditions?

 

Next time i loose access I will check this out.

 

Do you loose access on both the 8096 and 8920 ports? are you using ssl on the 8920 port?

What OS are you running?

When happens, I only lose access on https port. I avoid using default ports so no, I wasn't using 8920

Link to comment
Share on other sites

runtimesandbox

When happens, I only lose access on https port. I avoid using default ports so no, I wasn't using 8920

 

Sounds very similar to my situation then. Will post back with results next time it happens

Link to comment
Share on other sites

  • 7 months later...

I have the same issue.

I am running it as a service. Will try to get a log across next time i notice it.

I have to restart the service to get access to the HTTPS port again.

 

Did you guys solve your issue?

 

Edit: Sorry just realised this was in the linux section will create another thread

Edited by mselley
Link to comment
Share on other sites

  • 2 months later...

Reviving this to see if anyone else has had an issue with HTTPS.  I am experiencing the same issue as anderbytes.  After a few days HTTPS simply stop responding whatsoever and I have to bounce the emby service.  Once I do everything is working fine again.  I am running emby via a docker on an Unraid build if that helps.

 

Thanks

Link to comment
Share on other sites

Reviving this to see if anyone else has had an issue with HTTPS.  I am experiencing the same issue as anderbytes.  After a few days HTTPS simply stop responding whatsoever and I have to bounce the emby service.  Once I do everything is working fine again.  I am running emby via a docker on an Unraid build if that helps.

 

Thanks

 

Hi there @@sansoo22, we're sorry to hear about this. Please provide the emby server log when this happens. You can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks !

Link to comment
Share on other sites

Reviving this to see if anyone else has had an issue with HTTPS.  I am experiencing the same issue as anderbytes.  After a few days HTTPS simply stop responding whatsoever and I have to bounce the emby service.  Once I do everything is working fine again.  I am running emby via a docker on an Unraid build if that helps.

 

Thanks

My "solution" was to use Emby in Docker with a Host network. It's not the best scenario, but the Host network avoids the always-open network ports..... AFAIK.

 

The non-responding HTTPS at the time was caused by the flood of open ports. So today HTTPS responds fine in any connection try.

Link to comment
Share on other sites

  • 2 weeks later...

Shortly after reporting this issue i installed the ngnix-letsencrypt plugin in my unraid build to get a working SSL cert.  I've had that running for 10 days now and my HTTPS connection is still going solid.  I've watched/cast more movies than normal while away from home in the last 10 days as well.  Not exactly sure how this problem got solved but i seem to have killed 2 birds with one stone.  My HTTPS connection seems to be stable and the 2 pesky users that have iOS devices can quit complaining at me now too.


Link to comment
Share on other sites

 

Shortly after reporting this issue i installed the ngnix-letsencrypt plugin in my unraid build to get a working SSL cert.  I've had that running for 10 days now and my HTTPS connection is still going solid.  I've watched/cast more movies than normal while away from home in the last 10 days as well.  Not exactly sure how this problem got solved but i seem to have killed 2 birds with one stone.  My HTTPS connection seems to be stable and the 2 pesky users that have iOS devices can quit complaining at me now too.

 

 

Now that LetsEncrypt root certificate is trusted by Mozilla (since launch of Firefox v50), probably Mono updated it's mozroots and now we'll see less HTTPS trusting issues.

 

Just a guess.

Link to comment
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
 Share

×
×
  • Create New...