Website unaccessible after last update?

[PLV]

Hello,

It would appear that after the last Nest Wifi update some websites can't be accessed via the router 🤔

My SW version is 14150.43.80 and I can no longer access my prepaid online/web TV which I prepaid for 1 year. 

The domain is www.lepsi.tv. It worked just fine before the update and works still using my old router. I tried all three DNS settings on the Nest with no luck. Thanks for suggestions. 

Petr 

[MichaelP]

Hello @PLV 

It looks like this is related to the known issue regarding DNS resolution of hostnames that have extended characters. In this case, the domain name you've provided does not itself contain any special characters, but when accessing it, the server returns a redirection to a new hostname that does contain special characters (which trips over the new issue). This issue has been escalated and a fix should be coming soon.

[PLV]

Many thanks @MichaelP.

Hope it does get fixed before my subscription expires 😂

[MichaelP]

You may be able to work around this by configuring Chrome (or another browser) to use "Secure DNS" itself for hostname resolution. I was able to load that web site with my browser configured to use Secure DNS with Google's DNS servers. Here's a page from Cloudflare that summarizes how to configure various desktop browsers to do their own DNS resolution instead of using your WiFi system: https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/encrypted-dns-browsers/ 

[PLV]

Well, thanks for the tip. The website itself I am able to access e.g. by switching to mobile data. My main issue are the Android TV and iOS apps of this IPTV provider which also don't work due to the same error. I do not tend to watch TV in a web browser.

[MichaelP]

So, you may be able to get the Android TV to work by changing it from using DHCP to static network configuration so you can enter DNS server addresses that bypass your local WiFi system (something like Google's 8.8.8.8 and 8.8.4.4 or Cloudflare's 1.1.1.1, for example). On iOS, you should be able to leave the network configured using DHCP, but just override the DNS server to use "Manual" instead of "Automatic" and configure 8.8.8.8 and 8.8.4.4 to bypass the local WiFi DNS resolver. These should be worth a try at least (I'd try the iOS one first, since it is easier to set up and revert if it doesn't end up working).

[PLV]

Thanks again for the ideas. I haven't yet tried on iOS, but on Android phone I could set Private DNS and it works great so supposedly iOS will work too. 

On the Android TV the Private DNS setting is not available. The static IP configuration you suggested does not do the trick. I tried several combinations and DNS servers. The settings get stored fine, but somehow look like the Nest Wifi is not circumvented.

Currently I installed NordVPN on the TV to bypass the router. It does the trick, but of course with the limitations on speed and stability etc. But better than nothing for the time being. 

[MichaelP]

Whew – well, that's progress at least! I'm glad you have some way of watching until this gets fixed properly.

[Jeff]

Hi, everyone.

I got word that the fix for this should be going out now. If you're still seeing the issue, try restarting your network to see if it prompts the update to install for you. If you still see issues, please let me know.

Thanks.

[PLV]

Hi Jeff. Thanks for checking. I am still on the same SW version even after restart. Hence the issue persist. Guess I need to wait a bit longer. Located in Europe.

Cheers, Petr 

[Jeff]

I haven't been able to verify if the version number will change on the update, POS, but you will definitely notice right away the change in URL functionality. Hopefully that update hits soon.

Thanks.

[Jeff · Accepted solution]

Hi, all.

The version number will change on the update, and most of you should have it by now. Rather than ending in 80, the new release ends in 81.

Thanks.

[PLV]

Hi Jeff.

I can now confirm the fix has been applied with the version number you referenced. 

Thanks. You can now close this thread. 

[Jeff]

Perfect. I'm happy to hear it's working correctly, PLV. I'll mark this as resolved, but if you need anything else going forward, please feel free to open up a new thread.

Thanks.