[Bug] key is delivered to tailscale node for a long time (6-7 minutes) after re-authentication, traffic doesn't pass in this time

[spymobilfon]

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

1. User re-authenticated in Tailscale (in the client side)
2. I detected the registration in the Headscale log

2025-07-08T07:46:52.934674+00:00 headscale-xxx headscale[648615]: 2025-07-08T07:46:52Z INF github.com/juanfont/headscale/hscontrol/db/node.go:454 > Registering node machine_key=[bWpJu] node=xxxxx-50HP node_key=[Unuw8] vpn=true user=xxxxx@example.org

3. Traffic didn't pass via Tailscale node which responsible for routing traffic
4. I checked the Tailscale (router) log

Jul 08 07:46:55 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:46:56 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:02 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:08 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:14 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:19 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:24 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:29 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:34 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:39 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:53:05 tailscale-xxx tailscaled[445054]: wgengine: idle peer [Unuw8] now active, reconfiguring WireGuard
Jul 08 07:53:05 tailscale-xxx tailscaled[445054]: magicsock: disco: node [Unuw8] d:7ea3b2e69a300b60 now using 1.2.3.4:38913 mtu=1360 tx=d8eb29444f6e

6-7 minutes to accept new key and pass traffic are excessively long.

Expected Behavior

Maximum 1 minute to accept new key and pass traffic.

Steps To Reproduce

1. Re-authenticate in Tailscale (in the client side)
2. Open resource which route via the Tailscale router node
3. Check the Headscale log
4. Check the Tailscale log

Environment

Headscale:
- OS: Ubuntu 24.04
- Headscale version: 0.26.1
Tailscale router:
- OS: Ubuntu 22.04
- Tailscale version: 1.82.5
Tailscale client:
- OS: macOS Sequoia 15.5
- Tailscale version: 1.84.1

Runtime environment

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

Debug information

Headscale log

2025-07-08T07:46:52.934674+00:00 headscale-xxx headscale[648615]: 2025-07-08T07:46:52Z INF github.com/juanfont/headscale/hscontrol/db/node.go:454 > Registering node machine_key=[bWpJu] node=xxxxx-50HP node_key=[Unuw8] vpn=true user=xxxxx@example.org

Tailscale log

Jul 08 07:46:55 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:46:56 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:02 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:08 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:14 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:19 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:24 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:29 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:34 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:47:39 tailscale-xxx tailscaled[445054]: magicsock: disco: ignoring CallMeMaybe from d:77e58033721ad55b; [Unuw8] is unknown
Jul 08 07:53:05 tailscale-xxx tailscaled[445054]: wgengine: idle peer [Unuw8] now active, reconfiguring WireGuard
Jul 08 07:53:05 tailscale-xxx tailscaled[445054]: magicsock: disco: node [Unuw8] d:7ea3b2e69a300b60 now using 1.2.3.4:38913 mtu=1360 tx=d8eb29444f6e

[spymobilfon]

I detected one more case. Some our clients passed re-authentication process but their keys didn't delivery to the Tailscale nodes which responsible for routing traffic. Helps just reboot of the Tailscale node((

[qwerty1q2w]

the same case