You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues getting the integration agent working properly in 0.70.0-beta-2. I see by the release notes it now uses a consolidated Headscale API key which i have set in the Headplane config.yaml. I am using Headscale v0.28.0
I can't see anything in the Headplane logs relating to the agent starting or syncing, but in the UI, the agent is showing as healthy, however there is no agent showing in the UI like previous versions, and pressing the sync button doesn't do anything.
After entering the container shell and running the below commands with the API key i had specified in the headscale section of the config.yaml file i got the following logs which appeared to start the agent, as it then showed up in the UI. But even after this the sync button does not work in the UI.
LOG INFO tsnet running state path /var/lib/headplane/tailscaled.state
LOG INFO tsnet starting with hostname "headplane-agent", varRoot "/var/lib/headplane"
LOG INFO LocalBackend state is NoState; running StartLoginInteractive...
LOG INFO Connected to Tailnet (PublicKey: nodekey:caxxxxxxxxxxxxxxx)
LOG INFO AuthLoop: state is Running; done
I am probably doing something wrong in my config. I had the agent working in v0.62 using the seperate auth key method as per documentation, but struggling with this. I moved to 0.70.0-beta-2 due to the fixes which were added for web SSH, which wasnt working for me in v0.62.
I'm new to Headscale / Headplane, so would appreciate any help in identifying whether this is actually a bug, or just something i'm not doing correctly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am having issues getting the integration agent working properly in 0.70.0-beta-2. I see by the release notes it now uses a consolidated Headscale API key which i have set in the Headplane config.yaml. I am using Headscale v0.28.0
headscale:
url: http://headscale:8080
public_url: redacted
api_key: "hskey-api-redacted"
config_path: "/etc/headscale/config.yaml"
config_strict: true
integration:
agent:
enabled: true
host_name: "headplane-agent"
cache_ttl: 60
work_dir: "/var/lib/headplane/agent"
executable_path: "/usr/libexec/headplane/agent"
I can't see anything in the Headplane logs relating to the agent starting or syncing, but in the UI, the agent is showing as healthy, however there is no agent showing in the UI like previous versions, and pressing the sync button doesn't do anything.
After entering the container shell and running the below commands with the API key i had specified in the headscale section of the config.yaml file i got the following logs which appeared to start the agent, as it then showed up in the UI. But even after this the sync button does not work in the UI.
/docker$ docker exec -it headplane /bin/sh
/app # /usr/libexec/headplane/agent \ --url http://headscale:8080 \ —key hskey-api-_redacted \ --hostname headplane-agent \ --workdir /var/lib/ headplane/agent
LOG INFO tsnet running state path /var/lib/headplane/tailscaled.state
LOG INFO tsnet starting with hostname "headplane-agent", varRoot "/var/lib/headplane"
LOG INFO LocalBackend state is NoState; running StartLoginInteractive...
LOG INFO Connected to Tailnet (PublicKey: nodekey:caxxxxxxxxxxxxxxx)
LOG INFO AuthLoop: state is Running; done
I am probably doing something wrong in my config. I had the agent working in v0.62 using the seperate auth key method as per documentation, but struggling with this. I moved to 0.70.0-beta-2 due to the fixes which were added for web SSH, which wasnt working for me in v0.62.
I'm new to Headscale / Headplane, so would appreciate any help in identifying whether this is actually a bug, or just something i'm not doing correctly.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions