Skip to content

Headscale 0.28.0 does not work with Headplane #432

@pippo73

Description

@pippo73

Description

I'm trying to make work headscale with headplane.
I know both projects are developed so maybe is a temporary "mismatch" but maybe you can help me

Headscale is running on a server as a service
I would like now to configure headplane in a docker container

$ cat compose.yaml 
services:
  headplane:
    image: ghcr.io/tale/headplane:0.6.2-beta.4-shell
    container_name: headplane
    restart: unless-stopped
    ports:
      - 3000:3000
    volumes:
      - ./config.yaml:/etc/headplane/config.yaml
      - ./headplane-data:/var/lib/headplane
      - /etc/headscale/config.yaml:/etc/headscale/config.yaml
    environment:
      ROOT_API_KE: "hskey-api-nDa[...]"
      HEADPLANE_ADMIN_TOKEN: "KITi3/TX0/a[simple_string]"
cat config.yaml
server:
  host: "0.0.0.0"
  port: 3000
  base_url: "http://0.0.0.0:3000"
  cookie_secret: "kvnfZgFBPFjnP2iOwvoJrcHv2WjAI3so"
  cookie_secure: false
  cookie_max_age: 86400 # 1 day in seconds
  data_path: "/var/lib/headplane"
headscale:
  url: "https://mi.site:8443"
  config_path: "/etc/headscale/config.yaml"
  config_strict: true
integration:
  agent:
    enabled: false
    pre_authkey: "hskey-auth-qzia[...]-"
    host_name: "headplane-agent"
  docker:
    enabled: false
    container_label: "me.tale.headplane.target=headscale"
    socket: "unix:///var/run/docker.sock"
  kubernetes:
    enabled: false
    validate_manifest: true
    pod_name: "headscale"
  proc:
    enabled: true
  headscale_api_key: "hskey-api-7hIt[...]"

the fact is that when I reach with the browser the firs time the admin page, it asks me the api key and then it says that is not a good one :-(

Any idea where I mistake?

Headplane Version

ghcr.io/tale/headplane:0.6.2-beta.4-shell

Headscale Version

headscale version v0.28.0-beta.1

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingUpstreamCaused by changes in Headscale or other upstream tools

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions