Emby stops responding to https every couple days

[Luke 42077]

I realize there is a very small group that still reported issues. For right now what we've done is simply bring things back to the way they were in 3.2.70. Any new issues could be certificate related, could be related to TLS 1.3 which a lot of platforms are requiring now, and also could require brand new development, meaning the issue would also reproduce in 3.2.70. If any of you fall into that bucket, I'll be happy to assist. Thanks.

[mirkonline 0]

I realize there is a very small group that still reported issues. For right now what we've done is simply bring things back to the way they were in 3.2.70. Any new issues could be certificate related, could be related to TLS 1.3 which a lot of platforms are requiring now, and also could require brand new development, meaning the issue would also reproduce in 3.2.70. If any of you fall into that bucket, I'll be happy to assist. Thanks.

Hi, I see that the new release was published on Emby.media, but isn't available when checking in my Emby Server...

[Luke 42077]

It can take a little time. You can always grab it from the website if you want it immediately.

[mirkonline 0]

It can take a little time. You can always grab it from the website if you want it immediately.

Can I do a manual installation over the actual one?

[Luke 42077]

Yes.

[extensive 20]

well that was a big fat fail.  wasn't even up 24 hours

 

https://www.dropbox.com/s/hqwdmhqxtp3ycfw/embyserver.txt?dl=0

https://www.dropbox.com/s/1wrol8rp3zi4ltg/embyserver-63660902400.txt?dl=0

 

yay i get to wait a couple of months to get a release again.

 

some items of note

i was playing an audio book via my android phone...it was actually paused but connection was still open

i also had a session via firefox to that same audio book playing the beginning of the tracks to get the chapter names

i also had a session via firefox with metadata manager open entering new titles

Edited May 3, 2018 by extensive

[mirkonline 0]

Problem still persist with the 3.4 release!

It happen when I was connected to my Lan and disconnect Chromecast from Emby on Chrome Android, after tried to watch a movie on my TV.

I had to restart Emby!

[Luke 42077]

Problem still persist with the 3.4 release!

It happen when I was connected to my Lan and disconnect Chromecast from Emby on Chrome Android, after tried to watch a movie on my TV.

I had to restart Emby!

 

There's no https connection involved?

[mirkonline 0]

There's no https connection involved?

 

I was using port 80 on my internal LAN. Only use https when connecting from outside.

I can replicate the problem, that i can recap here:

 

1 - Switch my TV's source on Chromecast HDMI

2 - Using my Android phone and Chrome Browser (without HTTPS), I click on the cast button in the home screen of Emby and select my Chromecast.

3 - Click on play button on the first movie (from "to be continued" movie category)

4 - Click on the hamburger button (3 linees) on the botton right corner (near to the Pause button)

5 - Now I click on Pause, then on Stop

6 - Click on the back button

7 - Click on the cast buttom from the home screen of Emby and then disconnect from my Chromecast.

8 - Wait 1 or 2 minutes to get Emby unavailable from outside! (It's still available on my LAN)

 

Please, solve that problem, I'm running 2 month with this terrible releases of Emby! 

[Happy2Play 9780]

And if you used http from external network does it work properly?

[mirkonline 0]

And if you used http from external network does it work properly?

 

I can't test using http after the problem happens, because Emby is set to revert all http traffic to the https...

[mbnwa 49]

How many people here are relying on UPNP or NAT-PMP to deal with the port forwarding from external? I have my ports hard mapped in my router / firewall and I have yet to experience this issue on SSL or NON-SSL. I would say that something has to be in common with those having this issue ether all are using UPNP to deal with the mapping or something else. I know that reports have come in from Linux users as well as Windows users, I setup a linux box just to see if I can duplicate this and I was not able to duplicate this, however again I am port forwarding in my firewall to Emby and not relying on UPNP.

 

Would someone that is having this issue be willing to try to port forward to emby both the HTTP and HTTPS ports (HTTPS only if you do not allow HTTP from external)

[mirkonline 0]

How many people here are relying on UPNP or NAT-PMP to deal with the port forwarding from external? I have my ports hard mapped in my router / firewall and I have yet to experience this issue on SSL or NON-SSL. I would say that something has to be in common with those having this issue ether all are using UPNP to deal with the mapping or something else. I know that reports have come in from Linux users as well as Windows users, I setup a linux box just to see if I can duplicate this and I was not able to duplicate this, however again I am port forwarding in my firewall to Emby and not relying on UPNP.

 

Would someone that is having this issue be willing to try to port forward to emby both the HTTP and HTTPS ports (HTTPS only if you do not allow HTTP from external)

 

I'm not using UPNP, I set manual port forwarding on both port 80 and 8920 (tcp and udp)

[mbnwa 49]

I'm not using UPNP, I set manual port forwarding on both port 80 and 8920 (tcp and udp)

 

Do you have the ability to view your firewall logs when Emby stops responding? Can you verify that your router / firewall is still attempting to send the packets to Emby and are not being discarded?

 

If you are running on Windows can you disable Windows Firewall (temporarily) and see if that improves the situation?

 

Can you provide any details about your network setup?

 

My Network is setup as follows:

 

Comcast Gigabit service -->

PFSense Firewall / Router (All port forwarding happens here) -->

10GB fiber connection to core switch (No VLAN's) -->

10GB fiber connection to Emby server (Windows 10 for Workstation Pro, Windows Firewall disabled, IPv6/IPv4 enabled)

Edited May 3, 2018 by mbnwa

[RunningMomma 0]

And if you used http from external network does it work properly?

Same problem as it's always been. Https goes down http works

[Happy2Play 9780]

So could this be certificate issue then?  Has anyone redone their ssl certificate?

[extensive 20]

So could this be certificate issue then?  Has anyone redone their ssl certificate?

ive changed certs and so have others

[Happy2Play 9780]

Well it only applies to a specific configuration, as I haven't experienced it and can't reproduce it.  Unless it only applies to a specific client.

[mirkonline 0]

I finally found the root cause!

I disabled DDOS protection on my Asus RT-AC68u with Merlin Firmware.

Since I disabled DDOS, I tested and Emby worked fine, even replicating the step I wrote some hours ago...

But the problem started when Emby 3 release was published. 

So, there is somethings that isn't working as it should!

Does anybody have an Asus router?

[extensive 20]

I finally found the root cause!

I disabled DDOS protection on my Asus RT-AC68u with Merlin Firmware.

Since I disabled DDOS, I tested and Emby worked fine, even replicating the step I wrote some hours ago...

But the problem started when Emby 3 release was published. 

So, there is somethings that isn't working as it should!

Does anybody have an Asus router?

i have an asus router...checking now

[Luke 42077]

Well done.

[killride 47]

I don't have an asus router but I still have the issue on Emby 3.4.0.0

[Crestj 68]

No Asus router here (netgear and Google wifi) and I don't use ssl certs and it happens here too.

 

Dont know what causes it as it just happens when I try to connect to my server via the android emby app from out of the house.

[Happy2Play 9780]

I know my Netgear router has a "Disable Port Scan and DoS Protection " option.  

[mirkonline 0]

I don't have an asus router but I still have the issue on Emby 3.4.0.0

 

 

No Asus router here (netgear and Google wifi) and I don't use ssl certs and it happens here too.

 

Dont know what causes it as it just happens when I try to connect to my server via the android emby app from out of the house.

 

 

Could you try to disable DDOS or Firewall and check if the problem persist?

In my case, if I disable DDOS or the entire Firewall, I can't reproduce the problem, so I assume that the problem is solved disabling DDOS. But I don't like that solution, the problem are the latest releases of Emby!