TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Suddelny agent wont connect

    General Discussion
    2
    6
    273
    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.
    • F
      fennectech
      last edited by

      oken saved for next time.
      Tokenfile: /home/fennectech/.TRIGGERcmdData/token.tkn
      ComputerIDfile: /home/fennectech/.TRIGGERcmdData/computerid.cfg
      Logging in with saved token to run foreground tasks.
      Computer ID 5fe6b77c5191360019a0b662 saved for next time.
      Write backup completed.
      Initiated command removals
      Initiated command adds
      Added volume

          Socket is trying to reconnect to https://www.triggercmd.com...
      

      -|>- (attempt #1)

          Socket is trying to reconnect to https://www.triggercmd.com...
      

      -|>- (attempt #2)

      RussR 1 Reply Last reply Reply Quote 0
      • RussR
        Russ @fennectech
        last edited by

        @fennectech, is it still happening or was it a temporary problem? I just tested it on my computer and it's working for me.

        If it's still happening, please confirm that computer has Internet access.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • F
          fennectech
          last edited by

          Computer DEFINITLY has network access and its able to connect and stuff for the initial setup. And I’m able to use the internet from the machine. And the issue is still happening.

          RussR 1 Reply Last reply Reply Quote 0
          • RussR
            Russ @fennectech
            last edited by Russ

            @fennectech, can you run this command to verify you're not using a proxy server?

            env | grep -i proxy
            

            It seems normal API calls are working but the websocket won't connect. I've seen that when I've tried to use a proxy server.

            Do you have a special firewall that decrypts and re-encrypts your traffic by chance?

            EDIT: We figured it out - @fennectech's Linux box had Node JS version 15 installed and apparently that doesn't work. We downgraded to version 14 and it worked fine.

            Russell VanderMey

            1 Reply Last reply Reply Quote 0
            • F
              fennectech
              last edited by fennectech

              After doinga bit of testing i can confirm it breaks between nodejs-15.0.1-1 and nodejs-15.3.0-1 Ill keep looking and see if I can get a hold of any other versions of node so I can tell you the last version it worked on Narrowing dow the search for what broke it šŸ™‚

              RussR 1 Reply Last reply Reply Quote 0
              • RussR
                Russ @fennectech
                last edited by

                Thanks @fennectech. Good info.

                Russell VanderMey

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