I posted something semi unrelated a few weeks ago about the same problem on the same ATV at a different location. I am completely unable to connect to my server remotely from any of these tvs, manually or using connect, via 80 or 443. I get an immediate "connection failed" message after hitting OK. I am able to connect to the server using every other non-TV device on the same network w/o issue. Since I have until tomorrow morning to get this figured out or try again in a couple months, I'm hoping we can figure something out. My server is behind nginx, 80 and 443 are forwarded to my local internal IP on 8096. nginx and emby are on the same box, emby is running in a docker container in host mode. I did some digging this morning and found this in the nginx error log, which corresponds to the time I was trying to connect from the TV (sensitive stuff redacted): 2018/03/30 21:58:06 [error] 20801#20801: *84301 connect() failed (111: Connection refused) while connecting to upstream, client: client_ip, server: , request: "GET /emby/System/Info HTTP/2.0", upstream: "http://10.0.1.152:8096/emby/System/Info", host: "my_domain_name" There are success entries in the access.log from the same timeframe when I was testing other devices on the same network. Here is my nginx config: server { listen 80 default_server; listen [::]:80 default_server; server_name my_domain.com 10.0.1.152; return 301 https://$server_name$request_uri; } server { # SSL configuration include /etc/nginx/proxy.conf; listen 443 ssl http2 default_server; listen [::]:443 ssl http2 default_server; include /etc/nginx/snippets/strong-ssl.conf; ssl_certificate /etc/letsencrypt/live/my_domin.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/my_domain.com/privkey.pem; # Root location root /var/www/html; # Add index.php to the list if you are using PHP index index.html index.htm index.php index.nginx-debian.html; # Basic Auth to protect the site # auth_basic "Restricted"; # auth_basic_user_file /etc/nginx/.htpasswd; # Change the client side error pages (4xx) to prevent some information disclosure error_page 401 403 404 /404.html; # First attempt to serve request as file, then as directory, # then fall back to displaying a 404. # Deny access to .htaccess files, if Apache's document # root concurs with nginx's one location ~ /\.ht { deny all; } # Let's Encrypt Webroot plugin location -- allow access location ^~ /.well-known/acme-challenge/ { auth_basic off; autoindex on; } # Location settings for reverse proxy; enable those you wish to use # by removing the # from the section between the location line and the last } # location / { #emby at root of webserver proxy_pass http://10.0.1.152:8096; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #Next three lines allow websockets proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } I don't understand why literally every other device I've tried work, but not these TVs. 2 TVs on this network, 1 TV on a different network, all the same brand. Please help! EDIT: I'm not sure how those entries got into the nginx error log. I'm trying to connect from a TV again and it's failing, but I'm not seeing any corresponding entries in the error.log.

what happens with this config? #server { # # listen 80 default_server; # listen [::]:80 default_server; # # server_name my_domain.com 10.0.1.152; # return 301 https://$server_name$request_uri; # #} server { # SSL configuration include /etc/nginx/proxy.conf; listen 80; #added port 80 listen [::]:80; #added port 80 ipv6 listen 443 ssl http2; #removed default server listen [::]:443 ssl http2; #removed default server server_name my_domain.com 10.0.1.152; #moved listen info #Add HSTS Header add_header Strict-Transport-Security "max-age=15552000; preload" always; include /etc/nginx/snippets/strong-ssl.conf; ssl_certificate /etc/letsencrypt/live/my_domin.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/my_domain.com/privkey.pem; # Root location root /var/www/html; # Add index.php to the list if you are using PHP index index.html index.htm index.php index.nginx-debian.html; # Basic Auth to protect the site # auth_basic "Restricted"; # auth_basic_user_file /etc/nginx/.htpasswd; # Change the client side error pages (4xx) to prevent some information disclosure error_page 401 403 404 /404.html; # First attempt to serve request as file, then as directory, # then fall back to displaying a 404. # Deny access to .htaccess files, if Apache's document # root concurs with nginx's one location ~ /\.ht { deny all; } # Let's Encrypt Webroot plugin location -- allow access location ^~ /.well-known/acme-challenge/ { auth_basic off; autoindex on; } # Location settings for reverse proxy; enable those you wish to use # by removing the # from the section between the location line and the last } # location / { #emby at root of webserver proxy_pass http://10.0.1.152:8096; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #Next three lines allow websockets proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; #fixed connection header } }

3 Sony ATVs, all exhibit the same issue

By mastrmind11
March 31, 2018 in Android TV / Fire TV

Followers 1

Go to solution Solved by pir8radio, March 31, 2018

Prev
1
2
3
Next
Page 3 of 3

Sign In

3 Sony ATVs, all exhibit the same issue

Recommended Posts

pir8radio 1292

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Activity