no redirect
om3ga6400 opened this issue · 16 comments
whenever i click Connect via Tailscale it just says "Loading network code..." and then dose nothing
We cannot reproduce this problem, we have recently upgraded the networking mechanism, so please make sure of clearing your browser cached (or use Incognito mode).
If that does not help, please provide the following additional information:
- Any logging in the Developer Tools console from both the "Tailscale login" page and the main "WebVM" page
- What browser are you using
We cannot reproduce this problem, we have recently upgraded the networking mechanism, so please make sure of clearing your browser cached (or use Incognito mode).
If that does not help, please provide the following additional information:
- Any logging in the Developer Tools console from both the "Tailscale login" page and the main "WebVM" page
- What browser are you using
can you add a manual redirect?
and im using chrome
and there are no logs
can you add a manual redirect?
The page needs to load the network stack, it will automatically redirect you when that is done. Manually redirecting would not work anyway.
Please follow these steps from Incognito mode.
- Open https://webvm.io
- Open the Developers Tools
- Click on the "Connect via TailScale" link
- Make sure there is no message in console and the debugger is not stopped on an exception.
yeah nothing
okay im trying it on my windows pc
Can you also confirm if you see this message on the WebVM page after clicking of "Connect via Tailscale"
Can you also confirm if you see this message on the WebVM page after clicking of "Connect via Tailscale"
yes i see that
but it gets stuck on starting sign in
@alexp-sssup so is there any way to fix this?
Can you provide a screenshot of the network tab from the main WebVM page when the loading is stuck?
Can you provide a screenshot of the network tab from the main WebVM page when the loading is stuck?
sure
I was referring to the "network tab" of the developer tools
cant rn i will send when i get on my pc
Without further information we won't be able to debug this matter, and it's likely that it could have been caused by a temporary network failure. Closing for now.