Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    "Tailscale is not online" problem

    Scheduled Pinned Locked Moved
    Tailscale
    5
    34
    3.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mcury @chudak
      last edited by mcury

      @chudak said in "Tailscale is not online" problem:

      But in general, I am puzzled ...

      Any clues?

      Any logs when the problem starts ?
      What happens when you try to ping the other node ?
      What status it shows in the GUI ?

      I have been using that script with the following scenario, which works fine:

      I have a customer that runs multi WAN in their headquarters.
      One of this links is a CGNAT and other is not.

      The branch office connects directly to the primary non CGNAT link (I have opened a port in the firewall for that connection).
      If a link failover happens in the headquarters, sometimes it loses connections to the TS network and that's when the script "fixes" the problem by forcing the headquarter firewall to restart the service but now using the CGNAT link, thus connecting through the TS node and not a directly connection anymore.

      The reverse is also true, I mean, when the primary link which is not CGNAT comes back online.

      chudakC 1 Reply Last reply Reply Quote 0
      • chudakC
        chudak @mcury
        last edited by

        @mcury

        I don't know exactly where to look :(

        On a high level, only what I see is TS service is green (which is confusing but that's in a different thread and unrelated) and TS connection status is down.

        My use case is:

        pfS runs TS
        iPad runs TS
        iPhone runs TS
        Windows 11 VM runs TS

        So when psF is down, others actually work fine.
        I even noticed that routes get resolved.

        M 1 Reply Last reply Reply Quote 0
        • M
          mcury @chudak
          last edited by

          @chudak said in "Tailscale is not online" problem:

          TS connection status is down.

          isn't the script working for that ?
          script tries to ping and if it fails, it will restart the service.

          chudakC 1 Reply Last reply Reply Quote 0
          • chudakC
            chudak @mcury
            last edited by

            @mcury said in "Tailscale is not online" problem:

            @chudak said in "Tailscale is not online" problem:

            TS connection status is down.

            isn't the script working for that ?
            script tries to ping and if it fails, it will restart the service.

            That's an interesting part.
            Yesterday I found TS down

            I tried to start it manually, and switched Kea DHCP to ISC DHCP and back, removed /tmp/kea4-ctrl-socket.lock and could not make it start.

            Then today in the morning - everything is up and running normally

            ??!!

            M 1 Reply Last reply Reply Quote 0
            • M
              mcury @chudak
              last edited by

              @chudak said in "Tailscale is not online" problem:

              I tried to start it manually, and switched Kea DHCP to ISC DHCP and back, removed /tmp/kea4-ctrl-socket.lock and could not make it start.

              Then today in the morning - everything is up and running normally

              ??!!

              I don't see how one thing could interfere with each other.

              But, I'm still using ISC-DHCP for that customer.
              Can't switch to KEA yet...

              chudakC 1 Reply Last reply Reply Quote 0
              • chudakC
                chudak @mcury
                last edited by

                @mcury said in "Tailscale is not online" problem:

                @chudak said in "Tailscale is not online" problem:

                I tried to start it manually, and switched Kea DHCP to ISC DHCP and back, removed /tmp/kea4-ctrl-socket.lock and could not make it start.

                Then today in the morning - everything is up and running normally

                ??!!

                I don't see how one thing could interfere with each other.

                But, I'm still using ISC-DHCP for that customer.
                Can't switch to KEA yet...

                Do you know by chance how to catch related to TS stop/start errors/warnings in the logs?

                M 1 Reply Last reply Reply Quote 0
                • M
                  mcury @chudak
                  last edited by

                  @chudak said in "Tailscale is not online" problem:

                  Do you know by chance how to catch related to TS stop/start errors/warnings in the logs?

                  You can search old system logs in /var/log directory if I'm not mistaken. Shouldn't be hard to find it, I mean, if problem started yesterday at 15:00hrs, so there you go.

                  1 Reply Last reply Reply Quote 0
                  • chudakC
                    chudak
                    last edited by

                    TS in conjunction with pfS instability is really frustrating
                    I’m travelling now and TS is simply down with the error:

                    Error executing command (/usr/local/bin/tailscale status)

                    Health check:

                    - not logged in, last login error=invalid key: API key does not exist

                    unexpected state: NoState

                    So far nothing I’ve done, rebooting, deleting a lock file, nothing helped.

                    Thx G.. I still have OpenVPN as a backup option.
                    I’m surprised no one else is complaining about this…

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mcury @chudak
                      last edited by mcury

                      @chudak did you create the key at the tailscale's console and then imported it to pfsense ?
                      also, set the key to do not expire.

                      chudakC 1 Reply Last reply Reply Quote 0
                      • chudakC
                        chudak @mcury
                        last edited by

                        @mcury said in "Tailscale is not online" problem:

                        @chudak did you create the key at the tailscale's console and then imported it to pfsense ?
                        also, set the key to do not expire.

                        I did set my key to not expire.
                        I have used the original key with pfS and did not regenerate it
                        And have seen it’s working normally after this error.
                        So suspecting it’s unrelated

                        I’m hesitant to mess up with keys now as it used to work literally two days ago.

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          mcury @chudak
                          last edited by

                          @chudak said in "Tailscale is not online" problem:

                          @mcury said in "Tailscale is not online" problem:

                          @chudak did you create the key at the tailscale's console and then imported it to pfsense ?
                          also, set the key to do not expire.

                          I did set my key to not expire.
                          I have used the original key with pfS and did not regenerate it
                          And have seen it’s working normally after this error.
                          So suspecting it’s unrelated

                          I’m hesitant to mess up with keys now as it used to work literally two days ago.

                          Ok, if the problem happens again, try to create a key, import it, and then set it to "don't expire".

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post