Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't load web ui #102

Closed
Majobaga opened this issue May 8, 2023 · 4 comments
Closed

Can't load web ui #102

Majobaga opened this issue May 8, 2023 · 4 comments

Comments

@Majobaga
Copy link

Majobaga commented May 8, 2023

** Supporting Details **
Provide the following:

  • Browser Version: Chrome Version 112.0.5615.138
  • Headscale Version: 0.22.1
  • Any Browser Errors (control+shift+i in chrome to see)

Headscale UI issue

Describe the bug
A clear and concise description of what the bug is. Screenshots if applicable.

The web ui was working when I got it set up initially but a few hours later when after I had connected my Pfsense and Android phone as nodes it wouldn't work anymore. I get a full white page when I go to the headscaleURL/web with the errors as shown by the attached image.

I'm running headscale and headscale-ui as docker containers and ngninx proxy manager as a reverse proxy. I had the configuration set up per the documentation and nothing really was changed. I have tried restarting the containers, npm, reinstalled the containers, changed the domain, network within portainer, ports, etc etc. I appreciate the help, thanks!
@routerino
Copy link
Contributor

CSP error means that the web page thinks its been modified. The bunch of 404 errors means that it isn't resolving the web application static files.

Your web application has either stopped being served or isn't being routed correctly by your reverse proxy. Try clearing cache or restarting your docker containers.

@Majobaga
Copy link
Author

Unfortunately I'm not as savyy about linux and docker to understand fully what to do and what's going on. I've restarted the containers, restarted npm, removed them and pulled new images, changed ports, changed the subdomain, nothing works. Now at least it's not doing the same thing, now it's fully giving me a 404 type error.

I've tried to do everything I can. I'm not being successful at getting it to work again. It's probably something I don't know about or something wrong I'm doing. But I have another 20 proxy hosts on nginx p m working fine and no issues. Any insight would be very much appreciated. And sorry for the ignorance. TY.

Screenshot 2023-05-10 155114

@routerino
Copy link
Contributor

error 400 means bad request, it's still a disconnect somewhere between how nginx proxy manager is serving the site and how it is being presented. Bare in mind that the site is a statically hosted site. You can put a site that has <html><body>hello world</body></html> in the same spot, if it doesn't load hello world then you know it's a problem with the proxy configuration.

I did write a guide for setting up headscale ui with caddy but that will only be limited use to troubleshoot nginx proxy manager.

@routerino
Copy link
Contributor

closing as stale, cannot reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@routerino @Majobaga