Jump to content

Emby client breaks Emby Server connection


b074f3ba
 Share

Go to solution Solved by b074f3ba,

Recommended Posts

Emby client started a conversion process and I noticed it and stopped the process on the server-side. Now, the client's device tries polling the server on the conversion/sync progress and it appears to make Emby refuse all connections from that source (from my nginx proxy, so basically any connections through my duckdns.org domain) and results in a 502 error.

My setup is:

Router port forward ports 80, 443 --> nginx-proxy-manager hosted on docker on my Ubuntu (192.168.1.13), which routes to my Emby Server on Docker

Nginx logs attached, Emby Server logs attached as well.

# EMBY SERVER LOGS
2022-02-08 02:27:26.449 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/6/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.450 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/3/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.451 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/4/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.453 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/5/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.455 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/7/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.462 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/8/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/9/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.464 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/10/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/14/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/12/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/13/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.465 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/15/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
2022-02-08 02:27:26.466 Info Server: http/1.1 GET http://emby.mydomain.duckdns.org/Sync/JobItems/16/File. UserAgent: Emby/1 CFNetwork/1327.0.4 Darwin/21.2.0
# EMBY SERVER LOGS
2022-02-08 02:32:31.007 Info Server: http/1.1 Response 204 to 192.168.1.3. Time: 13ms. http://192.168.1.13:8096/emby/Sessions/Playing/Progress
2022-02-08 02:32:39.741 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313277ms. http://emby.mydomain.duckdns.org/Sync/JobItems/9/File
2022-02-08 02:32:39.955 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313501ms. http://emby.mydomain.duckdns.org/Sync/JobItems/5/File
2022-02-08 02:32:40.006 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313193ms. http://emby.mydomain.duckdns.org/Sync/JobItems/25/File
2022-02-08 02:32:40.130 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313313ms. http://emby.mydomain.duckdns.org/Sync/JobItems/24/File
2022-02-08 02:32:40.276 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313809ms. http://emby.mydomain.duckdns.org/Sync/JobItems/16/File
2022-02-08 02:32:40.675 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 313840ms. http://emby.mydomain.duckdns.org/Sync/JobItems/38/File
2022-02-08 02:32:40.812 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312229ms. http://emby.mydomain.duckdns.org/Sync/JobItems/57/File
2022-02-08 02:32:40.897 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312303ms. http://emby.mydomain.duckdns.org/Sync/JobItems/59/File
2022-02-08 02:32:40.974 Info Server: http/1.1 Response 200 to 108.170.192.1. Time: 312381ms. http://emby.mydomain.duckdns.org/Sync/JobItems/67/File
# NGINX ERROR LOGS
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/3/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/4/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/5/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/6/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/7/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/8/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/9/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/10/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/11/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/12/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/13/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/14/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/15/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET /Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733 HTTP/2.0", upstream: "http://192.168.1.13:8096/Sync/JobItems/16/File?api_key=e387a9519d7f440ca1e089afc076f733", host: "emby.mydomain.duckdns.org:443"
2022/02/02 04:40:19 [error] 944#944: *10661 connect() failed (111: Connection refused) while connecting to upstream, client: 108.170.192.1, server: emby.mydomain.duckdns.org, request: "GET 

 

embyserver_redacted.txt embyserver-63779937295_redacted.txt nginx_error_redacted.txt

Link to comment
Share on other sites

Hello b074f3ba,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

Link to comment
Share on other sites

visproduction

Just a guess, some server or connection has flagged this traffic as inappropriate and is refusing further connections.  it may clear when a timeout period is reached.  Perhaps security backend firewall setting picks up failed packet traffic and blocks it...  maybe even your host.  Search for failed connection traffic blocked security and your OS info.

Hope that helps.

Link to comment
Share on other sites

  • Solution

I think I have have fixed my problem. I routed the connections directly to the docker0 network on 172.17.0.1:8096 and let that route to my Emby Server instead of going through the local LAN IP address of 192.168.1.13:8096. Haven't had it error out since.

  • Like 1
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...