Hey all, I’m pretty illiterate when it comes to networking. I’m trying to set up a Foundry server on my PC, using Tailscale to bypass not having a public IP. The first time I set Tailscale up it worked perfectly, I asked a buddy to try and access and he reached the log in screen. The second time, when a session was supposed to happen, it didn’t work; tailscaled.exe would launch and immediately quit . I was a few versions behind so I uninstalled, rebooted, installed the new version. Now, I’m getting those same errors regardless of what I do. I’m honestly not sure what to mess with to fix it. Any help would be appreciated.

  • MoonguideOP
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    7 days ago

    Hey thanks for the reply. Yeah, tried it loads. The window still closes as soon as the cmd window fills up with the above. It might be a NRPT thing, but I don’t really know how to fix that, literally the first time I’ve read about it.

    Edit; Reading the log, it’s different. (logID "555145fdaa0b46c9a68cad9b4d5ed78fced1f92800cb4bae1074f9fb56be9728") 2024-12-14T23:25:25.145-06:00: Program starting: v1.78.1-t8903926f7-gc4163954e, Go 1.23.3: []string{"C:\\Program Files\\Tailscale\\tailscaled.exe"} 2024-12-14T23:25:25.147-06:00: LogID: 555145fdaa0b46c9a68cad9b4d5ed78fced1f92800cb4bae1074f9fb56be9728 2024-12-14T23:25:25.147-06:00: logpolicy: using dir C:\ProgramData\Tailscale 2024-12-14T23:25:25.147-06:00: dns: using *dns.windowsManager 2024-12-14T23:25:25.154-06:00: running ipconfig /registerdns ... 2024-12-14T23:25:25.155-06:00: flushing log. 2024-12-14T23:25:25.363-06:00: WSL: found 1 distributions 2024-12-14T23:25:25.625-06:00: safesocket.Listen: namedpipe.Listen: open \\.\pipe\ProtectedPrefix\Administrators\Tailscale\tailscaled: Access is denied.

    So, some access is still being denied, despite launching as admin.

    • breakingcups@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      7 days ago

      Is it possible that another instance of tailscale is still lurking in the background? If it’s ran as administrator and still blocking acess to the named pipe, it’s usually because some other process is already using it.

      • MoonguideOP
        link
        fedilink
        arrow-up
        1
        ·
        7 days ago

        That’s what I thought at first. The IPN is running, of course, and there is a service running in the background automatically for tailscale as well on top of the IPN. As soon as I kill the process it starts again. I don’t have any VPNs on my machine, and the firewall isn’t the culprit either.

        As far as I can tell there isn’t a duplicate process running.