API key not working

[SirAry]

So, instaled in docker/portainer, headscale:latest and headscale admin. Both on same network for rproxy. the headscale is serving on 8080 and 9090 as default. The rproxy is pangolin. I can access https://hs.mydomain.com which is the headscale-admin on 8080. But after creating an API key, copied and pasted settings testing shows X. And of course nothing works. Any Ideea? It seems that the web-ui cannot comunicate with the headscale as nothing in logs shows trying that?

[SirAry]

services: headscale: image: 'headscale/headscale:latest' container_name: 'headscale' restart: 'unless-stopped'

ports:
  - "0.0.0.0:8085:8080"
  - "0.0.0.0:9095:9090"
volumes:
  - '/home/ubuntu/tailscale/data:/var/lib/headscale'
  - '/home/ubuntu/tailscale/configs/:/etc/headscale'
networks:
  - pangolin      
environment:
  TZ: 'Europe/Bucharest'
entrypoint: headscale serve

headscale-admin: image: ghcr.io/gurucomputing/headscale-ui:latest #'goodieshq/headscale-admin:latest' container_name: 'headscale-admin' restart: 'unless-stopped' networks: - pangolin ports: - "85:8080" - "446:8443" volumes: - "/var/run/docker.sock:/var/run/docker.sock:ro" depends_on: - headscale networks: pangolin: external: true name: pangolin

[routerino]

Neither headscale or the ui are designed to work behind an authentication proxy such as pangolin. You are unlikely to get headscale to work at all that way.

I am not familiar enough with pangolin to understand if you can disable the authentication components or if pangolin will prevent the bearer token from being passed through.

[SirAry]

Hello, and thanks for reading. Somehow I did it modifying the traefik config file behind pangolin :). I connected with API key, I can see users page, and create users, but if I go to group or device view, I get 500 Internal server error. Nothing interesting in headscale logs Any ideea?

[nmd2k]

Somehow I got thing work just by disable ufw

[cryolite-ai]

@SirAry Glad you found a solution, now, can you close this issue please asap - it looks to the world from your title that there is a problem with the app when in fact it was a configuration issue at your end.

The reason that tidying up after yourself with issues is important is because people commonly look at the total number of issues a project has when they assess project quality - by leaving your issue unclosed, despite knowing the answer to your issue, you are doing a disservice to the people who write the free software you use (and you also leave noise when it comes to any developers trying to work out where to dig in to help a project). Thank you.