Stavros

Thank you, it is now working! I had done the approval, but just realized that I originally did it for 192.168.1.0 but never went back and approved for 192.168.10.x and in my console that approval was sitting there waiting. Did so any it’s back to working as it was before! Excellent! I prefer the plugin as my array doesn’t have to be up for Tailscale to work, so gladly keeping this implementation.

Hello! I, like many others here, found this plugin after suddenly finding out that my Tailscale docker was no longer working properly at a very poor time. Thank you so much for creating this and putting it out there! After reading Goldmasters post a few above this one with the terminal command, I was able to get the plugin to act as an exit node and can connect to the tailnet when on cellular/off-network by accessing the IP listed in the app. However, I cannot access the webGUIs for my various services using the internal LAN ip (192.168.10.x), which I was able to do so when using the container. This was extremely useful in the past as all of my bookmarks could remain the same. Is there a way to address this and I am approaching the configuration in the wrong way? Or is there a different approach to how I should be utilizing Tailscale and update all of my bookmarks To that last question, should I have Tailscale on for ALL of my devices, all of the time, and set up hostnames for each exit node (i.e. Tower in place of 192.168.10.x) and update my bookmarks accordingly? Admittedly, I do not have a full grasp on how Tailscale would work, but my initial sense would be that there would be conflicts with other devices on networks that may not have Tailscale installed that I'd have to resolve, if all of my devices were connected all the time. Have to sort through this thought, appreciate any insight on the meat of this question though. Thank you!