![]() Changing the system's DNS resolvers to my internal wireguard accessible DNS server.Running Wireguard with the config option DNS= in the section is not enough to reproduce the problem. I suspect any public resolver would have been fine. menu item didn't do anything until I changed the system's DNS resolver to 1.1.1.1 and restarted Tailscale. Despite everything running and resolving correctly with the Wireguard tunnel up, the Tailscale Log in. ![]() The only DNS resolver available on the system was through the Wireguard tunnel. Ultimately the problem is triggered by my DNS configuration. Stopping Wireguard, and trying the uninstall/reinstall dance again did nothing, same behavior. Uninstalling and reinstalling Tailscale made no difference. ![]() I had Wireguard running with an active tunnel during the installation. I had the same issue as #355 (comment), where the Log in. Since deleting the Keychain entries removes any frame of reference to this user profile/computer for Tailscale’s servers, when you reinstall and log back in, you will appear as a completely new device, with a new IP address.Ī data point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |