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

Received error: control server is too old; no noise key #707

New Issue
Closed
opened 2025-12-29 02:22:41 +01:00 by adam · 3 comments
adam commented 2025-12-29 02:22:41 +01:00
Owner
Copy Link

Originally created by @sachinshakya507 on GitHub (May 9, 2024).

Originally assigned to: @ohdearaugustin on GitHub.

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 am Experiencing an issue while connecting to my headscale server.
When i try to connect my headscale it stuck with no any authticate message
This is my status log from tailscale

$sudo systemctl status tailscaled.service
: Received error: control server is too old; no noise key
: monitor: RTM_DELROUTE: src=, dst=fe80::/64, gw=, outif=197, table=254
: monitor: RTM_DELROUTE: src=, dst=ff00::/8, gw=, outif=197, table=255: 
[RATELIMIT] format("control: LoginInteractive -> regen=true") (2 dropped)
: control: LoginInteractive -> regen=true
: [RATELIMIT] format("control: doLogin(regen=%v, hasUrl=%v)") (2 dropped)
: control: doLogin(regen=true, hasUrl=false)
: Received error: control server is too old; no noise key

Expected Behavior

Should be able to generate below authentication message.

To authenticate, visit:
https://my_headscale_server:443/register/nodekey:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Steps To Reproduce

What I did on my tailscale server to connect headscale.

sudo tailscale up --login-server http://my_headscale_server --accept-routes

Environment

- Headscale version: v0.12.3
- Tailscale version: 1.64.0

Runtime environment

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

Anything else?

I think i should update my headscale version. But can i get any help regarding headscale update without changing my config file or having any issue as its my production server.

Originally created by @sachinshakya507 on GitHub (May 9, 2024). Originally assigned to: @ohdearaugustin on GitHub. ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior I am Experiencing an issue while connecting to my headscale server. When i try to connect my headscale it stuck with no any authticate message This is my status log from tailscale ``` $sudo systemctl status tailscaled.service : Received error: control server is too old; no noise key : monitor: RTM_DELROUTE: src=, dst=fe80::/64, gw=, outif=197, table=254 : monitor: RTM_DELROUTE: src=, dst=ff00::/8, gw=, outif=197, table=255: [RATELIMIT] format("control: LoginInteractive -> regen=true") (2 dropped) : control: LoginInteractive -> regen=true : [RATELIMIT] format("control: doLogin(regen=%v, hasUrl=%v)") (2 dropped) : control: doLogin(regen=true, hasUrl=false) : Received error: control server is too old; no noise key ``` ### Expected Behavior Should be able to generate below authentication message. ``` To authenticate, visit: https://my_headscale_server:443/register/nodekey:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ``` ### Steps To Reproduce What I did on my tailscale server to connect headscale. ``` sudo tailscale up --login-server http://my_headscale_server --accept-routes ``` ### Environment ```markdown - Headscale version: v0.12.3 - Tailscale version: 1.64.0 ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? I think i should update my headscale version. But can i get any help regarding headscale update without changing my config file or having any issue as its my production server.
adam added the stale label 2025-12-29 02:22:41 +01:00
adam closed this issue 2025-12-29 02:22:42 +01:00
adam commented 2025-12-29 02:22:42 +01:00
Author
Owner
Copy Link

@ohdearaugustin commented on GitHub (May 18, 2024):

I really hope you are not running 0.12.3 still. This version doesn't support the noise protocol. Only an update to 0.22.3 will help.

It just seems like you have no noise key defined on the server.

Received error: control server is too old; no noise key

See this config snipped for 0.22.3:

b01f1f1867/config-example.yaml (L49-L56)

This seem no to be a bug.

@ohdearaugustin commented on GitHub (May 18, 2024): I really hope you are not running 0.12.3 still. This version doesn't support the noise protocol. Only an update to 0.22.3 will help. It just seems like you have no noise key defined on the server. > Received error: control server is too old; no noise key See this config snipped for 0.22.3: https://github.com/juanfont/headscale/blob/b01f1f1867136d9b2d7b1392776eb363b482c525/config-example.yaml#L49-L56 This seem no to be a bug.
adam commented 2025-12-29 02:22:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 17, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Aug 17, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:22:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 24, 2024):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Aug 24, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 stale
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#707
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?