undefined
Sorry, it sounds like a new kind of error. Let me know if anything seems to help resolve it.
If you (or anyone else) has a PC on the same network, it might be interesting to try CaptiveDNS, and see if the same issue occurs: https://browsedns.net/topic/2072/release-captivedns-access-the-browser-on-the-switch-locally-self-host-instructions
Can you try connecting to the Internet without the DNS, and doing a system update? (whether or not an update is available doesn't matter). A reboot might also help. Is this on Switch 1 or 2?
Is it a Switch 1 or a Switch 2?
On Switch 2, this message is occasionally is displayed, and doesn't appear to fix itself until you go online normally without the DNS configured. It seems intended to ensure that the browser receives any necessary security updates.
What file type, and did it used to work? Pretty much only common image formats and text files are supported.
The Switch 2 browser is actually a bit nicer than the Switch 1's, but it's very similar in terms of the limitations (20 minute timeout, no video support). I'd say that the OG Switch has a ~2015 browser, meanwhile the Switch 2 has a ~2022 one.
So it has better HTML compatibility, higher resolution, and a little bit more power. This means it can render some more "modern" pages at faster speeds, and even render ads surprisingly. But if it's one of your primary use cases, it's not worth getting just for the limited browser.
@TheAndyboi That's really cool! Reminds me of the firebug lite bookmarklet, which used to be one of the only reliable ways to debug mobile websites: https://css-tricks.com/snippets/html/use-firebug-in-any-browser/
@Larryfire85 This is for web developers! For example, I used this the other day for troubleshooting forum issues on Switch, where there's no browser console.
Eruda is a javascript tool that displays a web developer console directly in the website itself. This allows it to be used to debug errors on other devices, such as the Switch, WiiU, 3DS, etc.
To use it, embed it on the page like this:
<script src="https://cdn.jsdelivr.net/npm/eruda"></script>
<script>eruda.init();</script>
And then click the gear icon in the bottom right of the page. This is really useful if investigating errors that only occur on the device, and no web console is available.
Docs / more info:
https://eruda.liriliri.io/docs/
Screenshot:
@bugsinbread The problem seemed to be related to the latest Switch update (21.0.0) changing how some Javascript methods work.
One of the methods that stopped working: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toLocaleString
It was erroring early and preventing the full page from finishing to load. Probably other websites on the Internet are also affected.
The fix on our end was to avoid these methods and use other methods of calculating times/dates across the forum.
I just mean using a custom DNS to access other websites on the fridge itself. I wouldn't want any fridge ads! I'm also surprised Apple even was okay with it, since that's an ad for their new show.
Apparently new Samsung smart fridges display Internet ads, like this: https://www.reddit.com/r/assholedesign/comments/1ow6cpu/apparently_my_samsung_fridge_has_ads_now/
I'd be very curious if setting up BrowseDNS displays a browser on these fridges! It will depend on the connection test URL that they use, and also whether they have captive browsers in the first place.
Okay, I think I found the root cause of the issues on Switch, and sending/receiving messages should be working again. Can anyone that had issues before try again?
Can anyone that had issues on Switch let me know if it's any better now? It seems to be an issue related to the fading animation that runs in-between page loads.
Sorry, it's fixed now. The certificate expired and had to be renewed. It's supposed to happen automatically, but it didn't due to server config issues.
I'll take a look at this with my Switch to see if it can be improved, I have also heard other users are having similar issues recently.
@eden Are there any specific pages that give you this error more often? This site is supposed to be optimized for low-memory browsers like the Switch's.