EDACerton

Community Developer
  • Posts

    340
  • Joined

  • Last visited

  • Days Won

    1

EDACerton last won the day on March 28 2023

EDACerton had the most liked content!

1 Follower

Converted

  • Gender
    Male
  • URL
    https://github.com/dkaser

Recent Profile Visitors

1980 profile views

EDACerton's Achievements

Contributor

Contributor (5/14)

163

Reputation

2

Community Answers

  1. There used to be a button in the Tailscale web interface to do the reauth, but it looks like that is gone. I'll have to get in touch with the Tailscale folks on that one. In the meantime, you could disable key expiration via the Tailscale admin console, or use the CLI to do a reauth: tailscale up --force-reauth
  2. This has never been required with the plugin.
  3. That’s because in most cases it’s not a restriction (as you mention, particularly for Docker containers). For plugin developers, the Unraid version is more important.
  4. This is normal. Docker containers don't show up independently in the Tailscale console; they're just treated as a part of the server. If you're using a bridge Docker network (the usual default), you can just connect to tailscaleIP:dockerPort just like you would with the local IP. If you're using br0/etc. networks in Docker (so that your containers get a separate IP address on your LAN), you'll have to do extra work to make them available via Tailscale. There are generally two ways to do this: Use a subnet router to make the LAN IPs accessible over Tailscale (this is what basically everyone in that situation does), or Configure Tailscale "sidecars" for each of your br0 containers.
  5. Your Tailscale state appears to be corrupt. Delete the server from the Tailscale admin console. Erase the plugin configuration (there’s a button in the plugin settings, I think it’s in advanced mode.) Log back in to Tailscale via the plugin.
  6. I can see incoming pings and WebGUI traffic in the Tailscale log. I'd probably have to see Tailscale logs from your clients to see if there's anything interesting there. It might just be easier to reset the config on your server, though. Here's what I'd recommend if you want to try that: Delete the Unraid server from the Tailscale admin console. Erase the plugin configuration (there’s a button in the plugin settings, I think it’s in advanced mode.) Reboot your Unraid server. Log back in to Tailscale via the plugin.
  7. From the Tailscale side, everything looks fine. If you've been accessing the WebGUI from your phone, you might be accidentally crashing the WebGUI. There's been a known issue with the WebGUI and mobile devices (in particular Android devices)... essentially, if a tab with the WebGUI gets left open (even in the background), it eventually causes problems for the server.
  8. You need to turn NetBIOS off in SMB settings. Do you access the WebGUI via mobile device (phone/tablet)? I see some errors in the log that remind me of problems that occur when mobile devices have WebGUI tabs open for long periods of time. It seems like Tailscale DNS is enabled on both servers... I recommend that folks turn that off because it's not usually needed on servers.
  9. If you want the latest update as soon as Tailscale releases it, install the preview version of the plugin from CA (you don't have to uninstall the existing plugin, it will replace it on install). I released a preview update the same day that Tailscale released the last update. I'll probably be pushing that version to the main plugin tonight. For everyone else: I promise, I haven't forgotten you, I've just been very busy lately, I'm going to try to catch up this evening.
  10. Please generate diagnostics from inside the plugin settings and post on the support thread. Also, a better explanation of "plugin is crashing my server overnight" would be helpful... that could mean many things. Questions to consider/answer in your post over there: Does the server freeze (i.e., can you do anything at the console)? Can you access WebGUI? Can you access shares? Can you access Docker containers? What happens if you use local IP? What happens if you use Tailscale IP?
  11. There's already discussion happening on how to support this better.... we're over a year away from this being a potential issue, so there's plenty of time to solve that problem.
  12. My comment is valid with the latest copy of the privacy policy... the "callback" data is transmitted to the remote server as part of the query string. From the privacy policy (I just copied this section seconds ago): A devtools network capture in a browser shows that the server details are leaving the local browser by being transmitted to account.unraid.net when the "Update OS" button is clicked in the WebGUI. This behavior contradicts the statement above.
  13. Diagnostics from inside the plugin settings please.
  14. It looks like the connection is starting, but the server with UD seems to be terminating the connection ("got RST by peer") when it gets a response: You might want to check logs on that server to see if that helps show what it's unhappy about.
  15. The IP would be a better choice here... you'll lose the logs from while Tailscale isn't running, but once Tailscale comes up it should work. As you've seen, rsyslog won't be able to resolve a MagicDNS name on boot.