AVR cannot utilize SNI

[llagendijk]

In my attempts to get ycast running, I ran into a small isse:

• on my R-N500 it worked pretty much immediately when using the sample configs
• My HTR4067 however did no work and remained at the please wait. It turned out the receiver was connecting to the IP-address of my ycast server without the expected SNI (I guess, did not do a packet trace, but as the server field in the errorlog shows as I assume that it did not include the SNI). 2019/11/23 13:42:46 [error] 858#0: 21 open() "/usr/share/nginx/html/setupapp/Yamaha/asp/BrowseXML/loginXML.asp" failed (2: No such file or directory), client: 192.168.155.11, server: _, request: "GET /setupapp/Yamaha/asp/BrowseXML/loginXML.asp?token=0 HTTP/1.1", host: "192.168.150.39:80" 2019/11/23 13:42:46 [error] 858#0: 22 open() "/usr/share/nginx/html/setupapp/Yamaha/asp/BrowseXML/loginXML.asp" failed (2: No such file or directory), client: 192.168.155.11, server: , request: "GET /setupapp/Yamaha/asp/BrowseXML/loginXML.asp?token=0 HTTP/1.1", host: "192.168.150.39:80" 2019/11/23 13:42:57 [error] 858#0: *23 open() "/usr/share/nginx/html/setupapp/Yamaha/asp/BrowseXML/loginXML.asp" failed (2: No such file or directory), client: 192.168.155.11, server: , request: "GET /setupapp/Yamaha/asp/BrowseXML/loginXML.asp?token=0 HTTP/1.1", host: "192.168.150.39:80"

I solved this by adding the IP-address to the server_name in my NGINX ycast.conf: server_name *.vtuner.com 192.168.150.39;

[milaq]

Thanks for reporting :+1:

Other users also reported that some AVRs don't use any server names like yours. The workaround you used is fine. It should also work if you set the default_server directive in your nginx config like so: listen 80 default_server;

We may need to find out some time whether a server behavior causes this issue or if the AVRs themselves are just designed that way.

[milaq]

Keeping open for visibility