starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-12 04:10:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Main branch - server cannot connect to itself #588

New Issue
Closed
opened 2025-12-29 02:20:52 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:20:52 +01:00
Owner
Copy Link

Originally created by @Nickiel12 on GitHub (Dec 3, 2023).

Bug description

I have been having the issues described in issue #1572 , so I switched to the recommended PR (#1564) and I was able to re-register all of my devices, except for the server itself. I then switched to :main to see if that fixed the issue, and after some troubleshooting in the discord, rolled back to the latest stable (0.22.3) which then fixed the issue.

The issue was that when I ran tailscale up --login-server https://<domain> and navigating to the provided URL and running the supplied command, either the node would successfully register, but tailscale would not connect - giving the "go to URL to authenticate" message -, or headscale would fail to add the nodes with the error

github.com/juanfont/headscale/cmd/headscale/cli/utils.go:141 > Could not connect: context deadline exceeded error="context deadline exceeded"

Environment

  • Tested using :main 0153e26392506ad389aca2f633e3b638644baa1c and kradalby:1561-online-issue . Issue not preset in stable 0.22.3
  • Tailscale 1.54.0, go version: go1.21.4
  • Linux, NixOS 24.05 with unstable nixpkgs
  • 6.1.62
  • I don't know what configuration parameters would be relevant
headscale nodes register output:

2023-12-03T13:30:42-08:00 FTL github.com/juanfont/headscale/cmd/headscale/cli/utils.go:141 > Could not connect: context deadline exceeded error="context deadline exceeded"

I do use nginx to proxy traffic to headscale, however I'm not sure if that counts as a reverse proxy, and this issue was not present when running on the latest stable

To Reproduce

Install headscale on the latest :main version, and try to register the same device running headscale as a node.

Originally created by @Nickiel12 on GitHub (Dec 3, 2023). ## Bug description I have been having the issues described in issue #1572 , so I switched to the recommended PR (#1564) and I was able to re-register all of my devices, except for the server itself. I then switched to `:main` to see if that fixed the issue, and after some troubleshooting in the discord, rolled back to the latest stable (0.22.3) which then fixed the issue. The issue was that when I ran `tailscale up --login-server https://<domain>` and navigating to the provided URL and running the supplied command, either the node would successfully register, but tailscale would not connect - giving the "go to URL to authenticate" message -, or headscale would fail to add the nodes with the error ```sh github.com/juanfont/headscale/cmd/headscale/cli/utils.go:141 > Could not connect: context deadline exceeded error="context deadline exceeded" ``` ## Environment - Tested using `:main 0153e26392506ad389aca2f633e3b638644baa1c` and kradalby:1561-online-issue . Issue not preset in stable 0.22.3 - Tailscale 1.54.0, go version: go1.21.4 - Linux, NixOS 24.05 with unstable nixpkgs - 6.1.62 - I don't know what configuration parameters would be relevant ``` headscale nodes register output: 2023-12-03T13:30:42-08:00 FTL github.com/juanfont/headscale/cmd/headscale/cli/utils.go:141 > Could not connect: context deadline exceeded error="context deadline exceeded" ``` I do use nginx to proxy traffic to headscale, however I'm not sure if that counts as a reverse proxy, and this issue was not present when running on the latest stable ## To Reproduce Install headscale on the latest `:main` version, and try to register the same device running headscale as a node.
adam added the bug label 2025-12-29 02:20:52 +01:00
adam closed this issue 2025-12-29 02:20:52 +01:00
adam commented 2025-12-29 02:20:53 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Dec 10, 2023):

0.23.0-alpha2 addresses a series of issues with node synchronisation, online status and subnet routers, please test this release and report back if the issue still persist.

@kradalby commented on GitHub (Dec 10, 2023): [0.23.0-alpha2](https://github.com/juanfont/headscale/releases/tag/v0.23.0-alpha2) addresses a series of issues with node synchronisation, online status and subnet routers, please test this release and report back if the issue still persist.
adam commented 2025-12-29 02:20:53 +01:00
Author
Owner
Copy Link

@Nickiel12 commented on GitHub (Dec 20, 2023):

The host running headscale is able to connect its tailscale client to the server now.

@Nickiel12 commented on GitHub (Dec 20, 2023): The host running headscale is able to connect its tailscale client to the server now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#588
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?