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

    Compatibility with Debian 12

    General Discussion
    2
    4
    117
    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.
    • william siqueiraW
      william siqueira
      last edited by

      Hello everyone, I hope you are doing well.

      I'm facing a problem here with the triggercmdagent, I updated my pc from ubuntu 22 to debian 12, until then in ubuntu the agent was working normally. Now in debian 12 when I run the agent on it, I can register the new pc, but after that the agent does not show the interface so that I can create my scripts. I already uninstalled it and installed it again, removed the pc and re-registered on the platform, turned off the computer and restarted. I would like to know if triggercmdagent is not compatible with debian 12 or am I doing something wrong?

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

        @william-siqueira, I haven't tried it yet, but I'd like to make sure it works. I'm downloading it now.

        If the only problem is the GUI Editor won't work, you could edit your ~/.TRIGGERcmdData/commands.json file manually until I get it workin on Debian 12.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • william siqueiraW
          william siqueira
          last edited by

          In my case, the interface no longer appears after I login with the token. After this process, the triggercmdagent interface does not open at all.

          About the file you asked me to change, what should I change exactly?

          ![alt text](e85f30a5-80fc-4594-8869-05a78b251cb3-image.png image url)bolded text

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

            @william-siqueira, first you could make sure the default commands you have in your commands.json run when you click the green Trigger button in your account.

            The background commands (the commands with ground = background) will run if you've installed the background service using installdaemon.sh, but you'll need to use ps -ef to check whether they ran because they don't run in the foreground where you can see them.

            After that, you can add your own commands by copying one of those lines, and editing the command field to be your own command.

            Russell VanderMey

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