Jump to content

Problem with WAN HTTPS

pacoyoh

By pacoyoh
in Linux

 Share

Recommended Posts

pacoyoh

pacoyoh   2

Posted
Posted

Hello !

 

I am new here, but i try to resolve my problem with my Emby server, and i just cant find anything.

 

I will try to explain what is my problem, sorry if my english is bad, i am french :D

 

I installed few weeks ago Emby on my server (Debian 8). I tested Plex before but i really don't like it. I though the installation was simple, this is not my first think i install on my server, and everything was ok.

 

I got a letsencrypt certificate (i already own some for my others websites), installed it, everything ok. Internal access HTTP ok, internal HTTPS ok, WAN HTTP ok and WAN HTTPS ok too. I changed HTTPS port to 8097.

 

My problem is after a certain amount of time (it can be like 30 min or 8 hours), i can't reach my site in HTTPS in local and WAN. I still get time out, without any reason. I still can have access in HTTP, but i just cant in HTTPS.

 

I can't see anything in log, so i really duno where can be my problem....

 

Any idea? I really dont want to go with Plex :(

Link to comment
Share on other sites
Swynol

Swynol   375

Posted
Posted

Hello !

 

I am new here, but i try to resolve my problem with my Emby server, and i just cant find anything.

 

I will try to explain what is my problem, sorry if my english is bad, i am french :D

 

I installed few weeks ago Emby on my server (Debian 8). I tested Plex before but i really don't like it. I though the installation was simple, this is not my first think i install on my server, and everything was ok.

 

I got a letsencrypt certificate (i already own some for my others websites), installed it, everything ok. Internal access HTTP ok, internal HTTPS ok, WAN HTTP ok and WAN HTTPS ok too. I changed HTTPS port to 8097.

 

My problem is after a certain amount of time (it can be like 30 min or 8 hours), i can't reach my site in HTTPS in local and WAN. I still get time out, without any reason. I still can have access in HTTP, but i just cant in HTTPS.

 

I can't see anything in log, so i really duno where can be my problem....

 

Any idea? I really dont want to go with Plex :(

Is your http port and https port the same? This shouldn’t work if they are. You will need to specify a different port for each

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
pacoyoh

pacoyoh   2

Posted
  • Author
Posted

No my port are different. 8096 for HTTP, 8097 for HTTPS. HTTP still work, i can connect on my emby on it, but HTTPS stop working after sometine its random, sometime 30 min sometine 8h :(

Link to comment
Share on other sites
pacoyoh

pacoyoh   2

Posted
  • Author
Posted (edited)

Here is an example of log when i lost access in HTTPS.

2018-03-14 11:38:12.977 Info HttpResultFactory: Transmit file /var/lib/emby/cache/images/resized-images/1/17761b44-aa73-b6c8-bf38-d41bb7e36f4f.webp
2018-03-14 11:38:12.978 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 144ms. https://emby.mydomain.com:8097/Items/50da5dbb2e943ab6554c72c3df85140d/Images/Primary?maxHeight=537&maxWidth=359&tag=c135001ecaddb5bd99252be7e752a4aa&quality=40 
2018-03-14 11:38:13.163 Info HttpServer: HTTP GET https://emby.mydomain.com:8097/Items/8efca06d9e9fb7b5a20466cb3726e8ba/Images/Primary?maxHeight=972&tag=de647463fd4b6c38ffa5aa0bebcd53ce&quality=40. UserAgent: Mozilla/5.0 (Linux; Android 7.1.2; ONEPLUS A3003 Build/NJH47F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/65.0.3325.109 Mobile Safari/537.36
2018-03-14 11:38:13.391 Info HttpResultFactory: Transmit file /var/lib/emby/cache/images/resized-images/9/90496d63-6d91-ffe8-a6f9-98c7ddc3ee75.webp
2018-03-14 11:38:13.392 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 230ms. https://emby.mydomain.com:8097/Items/8efca06d9e9fb7b5a20466cb3726e8ba/Images/Primary?maxHeight=972&tag=de647463fd4b6c38ffa5aa0bebcd53ce&quality=40 
2018-03-14 11:38:13.837 Info HttpServer: HTTP GET https://emby.mydomain.com:8097/Users/e03bedb8340e4f61a9270cfc49104de4. UserAgent: Mozilla/5.0 (Linux; Android 7.1.2; ONEPLUS A3003 Build/NJH47F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/65.0.3325.109 Mobile Safari/537.36
2018-03-14 11:38:13.839 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 2ms. https://emby.mydomain.com:8097/Users/e03bedb8340e4f61a9270cfc49104de4 
2018-03-14 11:38:13.842 Info HttpServer: HTTP GET https://emby.mydomain.com:8097/Items/8efca06d9e9fb7b5a20466cb3726e8ba/Images/Logo?maxWidth=810&tag=e06779cd7301607f9833589b1c6b2536&quality=50. UserAgent: Mozilla/5.0 (Linux; Android 7.1.2; ONEPLUS A3003 Build/NJH47F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/65.0.3325.109 Mobile Safari/537.36
2018-03-14 11:38:14.034 Info HttpResultFactory: Transmit file /var/lib/emby/cache/images/resized-images/a/a9a45f13-8149-e905-df36-1a359d84588b.webp
2018-03-14 11:38:14.035 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 193ms. https://emby.mydomain.com:8097/Items/8efca06d9e9fb7b5a20466cb3726e8ba/Images/Logo?maxWidth=810&tag=e06779cd7301607f9833589b1c6b2536&quality=50 
2018-03-14 11:39:01.125 Info HttpServer: HTTP GET http://emby.mydomain.com:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.127 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 2ms. http://emby.mydomain.com:8096/emby/system/info/public?format=json 
2018-03-14 11:39:01.224 Info HttpServer: HTTP GET http://emby.mydomain.com:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.225 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 1ms. http://emby.mydomain.com:8096/emby/system/info?format=json 
2018-03-14 11:39:01.325 Info HttpServer: HTTP GET http://emby.mydomain.com:8096/mediabrowser/users/e03bedb8340e4f61a9270cfc49104de4?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.326 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 1ms. http://emby.mydomain.com:8096/mediabrowser/users/e03bedb8340e4f61a9270cfc49104de4?format=json 
2018-03-14 11:39:01.471 Info HttpServer: HTTP POST http://emby.mydomain.com:8096/emby/Sync/Data?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.499 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 28ms. http://emby.mydomain.com:8096/emby/Sync/Data?format=json 
2018-03-14 11:39:01.609 Info HttpServer: HTTP GET http://emby.mydomain.com:8096/emby/Sync/Items/Ready?TargetId=a99955d489dedfa6&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.629 Debug App: Returning 0 ready sync items for targetId a99955d489dedfa6
2018-03-14 11:39:01.640 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 32ms. http://emby.mydomain.com:8096/emby/Sync/Items/Ready?TargetId=a99955d489dedfa6&format=json 
2018-03-14 11:39:01.789 Info HttpServer: HTTP POST http://emby.mydomain.com:8096/emby/Sync/Data?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; ONEPLUS A3003 Build/NJH47F)
2018-03-14 11:39:01.791 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 2ms. http://emby.mydomain.com:8096/emby/Sync/Data?format=json 
2018-03-14 11:39:29.983 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source.
2018-03-14 11:39:29.983 Debug SessionManager: Disposing session controller WebSocketController
2018-03-14 11:47:12.956 Info HttpServer: HTTP GET http://emby.mydomain.com:8096/emby/system/info/public. UserAgent: python-requests/2.18.4
2018-03-14 11:47:12.958 Info HttpServer: HTTP Response 200 to XXX.XXX.XXX.XXX. Time: 2ms. http://emby.mydomain.com:8096/emby/system/info/public

I changed my IP and my domain. I am on Kodi on my phone, i log in, ok i am in HTTPS. And duno why, no error, it switch in HTTP, cause HTTPS stop answering (log in Kodi say timeout).

 

I have other website on my server with apache, all in https, and i have really no problem with them when Emby act like that :(.

 

Say me if you need something anyway.

Edited by pacoyoh
Link to comment
Share on other sites
torinn

torinn   3

Posted
Posted

I appreciate it's not particularly helpful to "me too" this thread but I'm seeing identical behavior. I'd be happy to provide logs or metadata if it's helpful Luke. The relevant snippet (I think) is:

2018-03-20 19:29:47.689 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to transfer data on the transport connection: Connection reset by peer.
2018-03-20 19:29:47.689 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to transfer data on the transport connection: Connection reset by peer.
2018-03-20 19:31:42.901 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source.
Link to comment
Share on other sites
Luke Emby Team

Luke   37049

Posted
Posted

 

I appreciate it's not particularly helpful to "me too" this thread but I'm seeing identical behavior. I'd be happy to provide logs or metadata if it's helpful Luke. The relevant snippet (I think) is:

2018-03-20 19:29:47.689 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to transfer data on the transport connection: Connection reset by peer.
2018-03-20 19:29:47.689 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to transfer data on the transport connection: Connection reset by peer.
2018-03-20 19:31:42.901 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source.

 

First can you please describe the problem that you're having? thanks.

Link to comment
Share on other sites
torinn

torinn   3

Posted
Posted (edited)

Absolutely! I'm running Emby 3.3.1.0 on a Debian 9 VM. I'm also using a LetsEncrypt certificate. Internal access over HTTP has been up 100%, internal and remote HTTPS behave exactly as expected when the service starts (I've set HTTPS only for remote access). I'm using the default HTTPS port.

 

"My problem is after a certain amount of time (it can be like 30 min or 8 hours), i can't reach my site in HTTPS in local and WAN. I still get time out, without any reason. I still can have access in HTTP, but i just cant in HTTPS." mirrors the behavior I see exactly. Sifting through the logs don't show an obvious reason why it falls over. netstat shows that there are a couple ESTABLISHED connections along with a lot of CLOSE_WAIT connections that haven't cleaned themselves up. Restarting the emby-server service resolves the issue temporarily.

 

If it's interesting, I've configured emby-server to run as a systemd service.

Edited by torinn
Link to comment
Share on other sites
torinn

torinn   3

Posted
Posted (edited)

I'd be happy to! I've just upgraded to Version 3.3.1.6 beta. I'll bump this thread if I see the behavior reoccur.

 

EDIT: I saw that 3.3.1.7 was released this afternoon. I've upgraded accordingly (I figure there's some new goodies in there). 

Edited by torinn
Link to comment
Share on other sites
torinn

torinn   3

Posted
Posted

I'm seeing the same behavior described in the OP and my second post. Many CLOSE_WAIT connections after running netstat | grep 8920. Running v3.3.1.7. I see 3.3.1.8 was released 18h ago. Should I expect that to behave similarly?

Link to comment
Share on other sites
Luke Emby Team

Luke   37049

Posted
Posted

If you could try the betas that would be helpful as we are actively working on resolving it. 3.3.1.8 may not, but hopefully the next one will. Thanks.

Link to comment
Share on other sites
pacoyoh

pacoyoh   2

Posted
  • Author
Posted

Hello, sry i can't respond these days :(

 

I upgraded my server in 3.3.1.9 beta, i will say you if its better or not.

 

I had a solution anyway, use my apache in proxy on the HTTP local port (8096) to 443, even better for me, no more port to mention for login.

 

I got some problem anyway, i will report them shortly.

Link to comment
Share on other sites
torinn

torinn   3

Posted
Posted

3.3.1.9 hasn't exhibited the same behavior since I upgraded on 3/26 ~2pm EST. I'll still upgrade to 3.3.1.10 as I see that's been released.

Link to comment
Share on other sites
  • 3 weeks later...
torinn

torinn   3

Posted
Posted

Err... Ok. Here's a direct copy-paste from when I initially reported this issue about ~10 comments ago:

 

 

Absolutely! I'm running Emby 3.3.1.0 on a Debian 9 VM. I'm also using a LetsEncrypt certificate. Internal access over HTTP has been up 100%, internal and remote HTTPS behave exactly as expected when the service starts (I've set HTTPS only for remote access). I'm using the default HTTPS port.

 

"My problem is after a certain amount of time (it can be like 30 min or 8 hours), i can't reach my site in HTTPS in local and WAN. I still get time out, without any reason. I still can have access in HTTP, but i just cant in HTTPS." mirrors the behavior I see exactly. Sifting through the logs don't show an obvious reason why it falls over. netstat shows that there are a couple ESTABLISHED connections along with a lot of CLOSE_WAIT connections that haven't cleaned themselves up. Restarting the emby-server service resolves the issue temporarily.

 

If it's interesting, I've configured emby-server to run as a systemd service.

 

As I mentioned, after 3.3.1.9 the behavior went away. I upgraded to 3.3.1.10 and 3.3.1.11 as they became available and was unable to upgrade again until 3.3.1.18. I now see EXACTLY the same behavior described in the quoted comment (which itself is a quote from the OP of the thread) with the server. Local and remote HTTPS connections fail, plenty of CLOSE_WAITs in the output of netstat, HTTP works like a charm.

Link to comment
Share on other sites
ElDitcho

ElDitcho   0

Posted
Posted

Hello !

 

I am new here, but i try to resolve my problem with my Emby server, and i just cant find anything.

 

I will try to explain what is my problem, sorry if my english is bad, i am french :D

 

I installed few weeks ago Emby on my server (Debian 8). I tested Plex before but i really don't like it. I though the installation was simple, this is not my first think i install on my server, and everything was ok.

 

I got a letsencrypt certificate (i already own some for my others websites), installed it, everything ok. Internal access HTTP ok, internal HTTPS ok, WAN HTTP ok and WAN HTTPS ok too. I changed HTTPS port to 8097.

 

My problem is after a certain amount of time (it can be like 30 min or 8 hours), i can't reach my site in HTTPS in local and WAN. I still get time out, without any reason. I still can have access in HTTP, but i just cant in HTTPS.

 

I can't see anything in log, so i really duno where can be my problem....

 

Any idea? I really dont want to go with Plex :(

 

I have the exact same problem

 

https can't be reached after some random time put http can 

 

I had some ssl errors in logs but sometime there's nothing. I'll put my logs in this thread.

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
Go to topic listing
×
×
  • Create New...