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.

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

[Bug] Unable to access Headscale http server after installation #2238

Closed
2 of 4 tasks
jaeger-2601 opened this issue Nov 16, 2024 · 4 comments
Closed
2 of 4 tasks

[Bug] Unable to access Headscale http server after installation #2238

jaeger-2601 opened this issue Nov 16, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@jaeger-2601
Copy link

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I've completed the installation of Headscale on Ubuntu 24.04 LTS. Headscale is being run as a systemd service and the server address is the default one provided in config: 127.0.0.1:8080. I've ensured no other program is using that port. The logs also indicate there is no error. Trying to access the http server by curling on the local machine doesn't seem to be working.

2024-11-16T06:46:41Z WRN
WARN: The "dns.use_username_in_magic_dns" configuration key is deprecated and has been removed. Please see the changelog for more details.

2024-11-16T06:46:41Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite
2024-11-16T06:46:41Z INF Setting up a DERPMap update worker frequency=86400000
2024-11-16T06:46:41Z INF listening and serving HTTP on: 127.0.0.1:8080
2024-11-16T06:46:41Z INF listening and serving debug and metrics on: 127.0.0.1:9090

Expected Behavior

Should be able to access Headscale http server of machine

Steps To Reproduce

  1. In Ubunutu 24.04 LTS
  2. Install Headscale server using official guide using .deb package
  3. Curl 127.0.0.1:800 on the machine.

Environment

- OS: Ubuntu 24.04
- Headscale version: v0.23.0
- Tailscale version:

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

@jaeger-2601 jaeger-2601 added the bug Something isn't working label Nov 16, 2024
@nblock
Copy link
Collaborator

nblock commented Nov 16, 2024

Can you give the output of these commands (run those on the same machine where headscale installed):

  • curl http://localhost:8080
  • sudo ss -tlpn | grep headscale
  • sudo ss -tlpn | grep 8080

If you want to reach headscale from the outside, you'll need to update the configuration to set at least:

server_url: http://your-headscale.exaple.com:8080 
listen_addr: 0.0.0.0:8080 

@jaeger-2601
Copy link
Author

jaeger-2601 commented Nov 16, 2024

image
image
image

I've also completely turned off my firewall btw to check if that was somehow the problem.

@nblock
Copy link
Collaborator

nblock commented Nov 16, 2024

This is actually fine. Headscale does not provide a web interface by default. You can visit http://localhost:8080/windows which shows how to setup a windows client. Same with http://localhost:8080/apple .

See also: https://headscale.net/ref/integration/web-ui/

@jaeger-2601
Copy link
Author

Yeah that works lol. Wish someone would add this in the documentation though. It was not very clear at the end.

nblock added a commit to nblock/headscale that referenced this issue Nov 17, 2024
@nblock nblock mentioned this issue Nov 17, 2024
6 tasks
nblock added a commit that referenced this issue Nov 18, 2024
* Link back to node registration docs
* adjust wording in apple docs
* Mention client specific page to check if headscale works

Ref: #2238
hopleus pushed a commit to hopleus/headscale that referenced this issue Nov 18, 2024
* Link back to node registration docs
* adjust wording in apple docs
* Mention client specific page to check if headscale works

Ref: juanfont#2238
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants