Some questions and suggestions about headscale-ui about headscale-ui

[routerino]

For Question 1, you might be misunderstanding how the UI works. The docker container doesn't do any direct communication to headscale. All requests leave and arrive via your browser, and your browser definitely isn't inside a docker container.

Question 2 not really sure what you're asking for here. If you need additional authentication methods you can put in a forward auth proxy. Anything more sophisticated is only feasible with a backend authentication platform, and headscale UI is frontend only.

Question 3, I default to https as a security measure. You can make a custom caddyfile and place it in /data/Caddyfile via a bind mount if you want a non-secure connection. I may redo the caddyfile to use caddy's JSON at some point so I can be more sophisticated about environment variables.

[routerino]

I'll close for now, Question 3 will be addressed with #37

[LOVECHEN]

Authentication failed, but browser access is no problem

[routerino]

Can you tell me what the console error says when this happens? You can find out by opening the dev console (control+shift+i) and reading out the error.

theoretically what you are trying to do should work, but it all works on the browser fetch method, which sometimes gets unhappy with insecure sites. I suspect you're having CORS problems because the browser doesn't think it's the same domain.

Easiest fix is to make sure both sites get served on the same IP and port, that will most likely fix your issue.

[LOVECHEN]

headscale must be served over TLS/HTTPS
Remote access does not support unencrypted traffic.

thanks bro
i found this comment on headscale project ， problem resolve