gurucomputing
Question: How far back does the UI support Headscale
I'd like to try the UI but I guess it only supports the latest version of headscale right? Or is it backwards compatible?
There's a compatibility chart in the readme. There is no backwards compatibility short of using an older image/release.
Versioning
The following versions correspond to the appropriate headscale version
| Headscale Version | HS-UI Version |
|---|---|
| 26+ | 2025-05-22+ |
| 25+ | 2025-03-14+ |
| 24+ | 2025-01-20+ |
| 23+ | 2024-10-01+ |
| 19+ | 2023-01-30+ |
| <19 | <2023-01-30 |
Ok thanks. I installed the UI and seeing a blank white page. So that's probably the reason. I am still on 22 and wanted to update but haven't yet.
There's a compatibility chart in the readme. There is no backwards compatibility short of using an older image/release.
I still have problem after updating to headscale 0.26. Still getting a blank white page. I am accessing the webserver by https://mytsdomain:8443/ I am not sure if or how port 8080 is needed, I have not exposed it on nginx because it is the listen address of headscale. I amnot using docker just downloaded the app and put it in /var/www/web. I assume that is not enough. But I could not find any installation notes apart from the docker stuff.
Do you have any advise?
@n0valis as I understand it the way this works is that the singe web-page, which is downloaded into your browser, will attempt to talk to the headscale API to make necessary changes, and to do that without breaking various browser restrictions preventing certain stuff being executed from one domain source to affect another you need the API to be visible to the browser on the same 'domain'... if your browser cannot access domain where the API is hosted then it won't be able to work.
Now I don't know if that's the problem you have or if the blank page is simply representative of the page not loading at all.. but I hope the explanation helps you.
You might want to either inspect the page source in your browser (to see if there is anything being presented) and you might consider debugging the webserving setup e.g. put a simple page in the location you think you are serving from to try to get things working.
I think in fairness it's highly likely that the problem you have is not an issue with the software so much as with your use of it and possibly whether you have the API accessible to your browser (and I don't think that the person who wrote the page will have the resources to be able to provide user support to debug your particular situation - hence I've dropped this note into the thread). If this doesn't make enough sense to you then I would suggest you put your whole situation into a modern LLM with all the context you can - what you're hosting, what you want to do, the name of this repository, the symptoms you are finding etc.. you will probably be able to get better help than leaving an open issue on this..
...on which note, I wonder if you could close off this issue since it probably isn't strictly a software issue and it confuses people coming to the project trying to work out if the project is faulty or not. Thanks.
