Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BrowseNX closes after a few minutes when watching videos with the message "This screen will now close" #29

Open
muxi1 opened this issue Sep 11, 2023 · 7 comments

Comments

@muxi1
Copy link

muxi1 commented Sep 11, 2023

BrowseNX closes after a few minutes when watching videos with the message "This screen will now close". The problem exists with the last version 0.4.1, as well as a self-compiled version (with libnx 4.4.2-1). I am using AMS v1.5.5 with dns_mitm and exosphere enabled under an emuMMC on FW 16.1.0. BrowseNX is run by title override to use the maximum available memory. I have already searched for solutions to the problem on the web, but nothing can be found. Any ideas? Thanks in advance.

@Lliakos
Copy link

Lliakos commented Nov 4, 2024

Did you find any solution/fix for this?

@vgmoose
Copy link

vgmoose commented Nov 8, 2024

The browser timeout mechanism is not well understood, but for the 20 minute timer in the connection applet, it's a result of doing 600 failed GETs to the connection URL.

To troubleshoot this, it might be interesting to set the DNS (either via dns-mitm or in network settings) to use 207.246.121.77 (90dns) for the connection test domain.

In dns-mitm, the line would look like: 207.246.121.77 ctest.cdn.nintendo.net

If the share applet is doing some kind of similar check, these DNS changes could address it by making sure that "success" is returned for that check.

@muxi1
Copy link
Author

muxi1 commented Nov 8, 2024

In dns-mitm, the line would look like: 207.246.121.77 ctest.cdn.nintendo.net

Thanks for the tip! I will try it with this line in my host file (dns_mitm).

Edit:
It does not work. No connection is established.

@vgmoose
Copy link

vgmoose commented Nov 8, 2024

Huh, it should at least succeed the connection test. Maybe a conflict with another dns-mitm rule?

I tried on PC with /etc/hosts but got:

$ curl ctest.cdn.nintendo.net -v
< HTTP/1.1 200 OK
< X-Organization: Nintendo

That X-Organization header and the 200 is what makes the connection test pass. If you don't want to keep testing, i can try to replicate later today. Last I tried to reproduce the issue in browsenx though, I wasn't able to get it to timeout.

Could you post your latest FW info, and dns-mitm config?

@muxi1
Copy link
Author

muxi1 commented Nov 8, 2024

AMS 1.8.0
FW 19.0.1
default.txt

However, even without this entry, I can no longer connect to the Internet with BrowseNX. The HB Appstore, on the other hand, works perfectly.

@vgmoose
Copy link

vgmoose commented Nov 8, 2024

Thanks, also at least for the switchbru entry (Line 14) the IP has changed to 92.204.211.16:

92.204.211.16 *switchbru*.*

That should make the BrowseNX landing page load (unsure about timeout still)

@muxi1
Copy link
Author

muxi1 commented Nov 8, 2024

Thanks! Timeout problem still exists, but at least the browser establishes a connection again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants