You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm using v0.1 build 50, based on yggdrasil 0.5.12 on iOS 18.2. I have set up the peers and can connect to them successfully, however, when I try to open any yggdrasil page in safari it just leads to an infinite load and a timeout. The other peers can access the page just fine, so I assume it's an iOS/app problem.
Debug steps I've tried:
Checked that the VPN is on and setup correctly
Reset the configuration and restarted the app completely
Used a different browser (firefox) just in case
Used different peers, including ones from the public list
Tested on a second iPhone running iOS 18.1.1
The issue was present in the previous 0.5.9-based build as well and I assumed that it was due to inter-version incompatibility, but now that 0.5.12 is out and it still doesn't work I'm pretty sure something's wrong here.
Thank you for all the amazing work on yggdrasil btw!! Would be more than happy in helping with debugging this and providing any other information that might be needed :)
The text was updated successfully, but these errors were encountered:
Hi! I'm using v0.1 build 50, based on yggdrasil 0.5.12 on iOS 18.2. I have set up the peers and can connect to them successfully, however, when I try to open any yggdrasil page in safari it just leads to an infinite load and a timeout. The other peers can access the page just fine, so I assume it's an iOS/app problem.
Debug steps I've tried:
The issue was present in the previous 0.5.9-based build as well and I assumed that it was due to inter-version incompatibility, but now that 0.5.12 is out and it still doesn't work I'm pretty sure something's wrong here.
Thank you for all the amazing work on yggdrasil btw!! Would be more than happy in helping with debugging this and providing any other information that might be needed :)
The text was updated successfully, but these errors were encountered: