Austin

For sure! So yes, the compiled HTML version is provided in each release as just a simple folder. That folder is all that is required to serve headscale-admin. When deploying...

> nm, I've got it installed. Apparently this frontend needs a reverse proxy like Caddy to serve the static pages. Obvious for the informed user, but not for somebody with...

I believe the issue has been resolved in the dev branch by assembling the API URL in a different way. Please let me know if you still have issues and...

> [@zmweske](https://github.com/zmweske) It is annoying to force the use of `/admin` instead of something like `admin.hs.ex.com` which used to work but not anymore! I agree with you and went back...

@Enissay understood. I think `headscale-admin-root` has the connotation of running as a root user which is by not the intended effect, so if you have any suggestions for names of...

Hello, the 0.26 branch is the correct branch to use for 0.26. I always keep the major version of headscale-admin inline with headscale for guaranteed compatibility, so if you want...

Huh, I have absolutely no idea where this is coming from... Can anyone help me replicate this issue in a dev environment of some kind? I'm happy to try and...

@jd-apprentice @iBisakol @mojrs10 The example caddy implementation provided within the repo uses Caddy in a dockerized environment: https://github.com/GoodiesHQ/headscale-admin/tree/main/example

Can you enable console debugging, click save, and then provide any relevant output from the development console? This usually happens if there's a CORS or some kind of communication issue...

The solution at least as of right now is to rename the actual user to an object with an @ in the name (generally just adding @ to the end...