taaaylo

This was strange because I had no issues previously with running this exact command tailscale funnel 32400 and was never given a notification in the webGUI about a conflict or a config reset because of it. I guess it was the result of a new tailscale version along with updating the plugin. Sat down and spent some time reading through the --help and new syntax. Didn't realize that tailscale was defaulting to 443 (or that there was a conflict issue until this problem presented itself) as the initial indications was that the funnel was disabled without any other notifications (until I was able to replicate the issue and generate the webGUI alert). Also wasn't quite understanding how to switch the port tailscale was using because of the new funnel syntax. Long story short, for anyone having this particular issue, running tailscale --bg --https 8443 127.0.0.1:32400 is the command I was looking for to avoid the unRAID port conflict and resolve the problem. Pretty annoying, but I guess I learned a little bit from it.

I've found a way around this issue. Seems to stem from the unRAID gui and Tailscale both utilizing port 443. Updated to 7.2.2 and attempted to enable the funnel and then try again, but no luck. I didn't really feel comfortable moving the unRAID gui off of 443, so I eliminated that from a list of options. I tried several configurations to allow Tailscale to avoid the use of 443, but also no go. I'm not completely sure what the correct and proper answer is, but I utilized nohup since leaving the terminal up allowed the funnel to persist. Would love a proper answer on this as it is currently my only way past CGNAT. Bonus: if someone could explain to me if using funnel on my OPNsense router and somehow routing the traffic through my tailnet to unRAID/Plex is possible/viable, I'm all ears. I like the idea of moving these types of services OFF of my server.

I am also having the same issue on 7.1.2. The "fix" I've had is to leave a terminal window open after the command has been run. If I try to run with the --bg flag, the funnel goes down within seconds, but this is obviously not ideal and the terminal window either closes itself eventually or I restart, shut down, or put the computer I am accessing from to sleep. Should upgrading to 7.2 resolve this problem?