fredliang44
derp: 21.221.23.122:53654: client nodekey:09a***13d rejected: tailscaled version is too old (out of sync with derper binary)
dear: Linux 5.16.17-sun50iw6 aarch64 GNU/Linux system, after upgrading the derper self built node installed in Docker to the latest version, cannot connect successfully. Using the "tailscale status" command displays: # Health check:
- not connected to home DERP region 901 Use the 'tailscale netcheck' command to check if the display is normal: Report:
UDP: true IPv4: yes, 112.20.75.201:53735 IPv6: no, but OS has support MappingVariesByDestIP: PortMapping: UPnP Nearest DERP: tong DERP latency: dtae: 1.3ms (tong) The Derper log consistently shows that the tailscale version used is too old and rejected. Upgrading tailscale to the latest version 1.168.2 still remains the same: 2024/07/14 03:44:36 derp: 37.110.125.20:21391: client nodekey:88522 rejected: tailscaled version is too old (out of sync with derper binary) 2024/07/14 03:44:37 derp: 37.110.125.20:21394: client nodekey:b5b827 rejected: tailscaled version is too old (out of sync with derper binary) 2024/07/14 03:44:38 derp: 37.110.125.20:21396: client nodekey:fa9a65b rejected: tailscaled version is too old (out of sync with derper binary) 2024/07/14 03:44:38 derp: 21.221.23.122:53654: client nodekey: rejected: tailscaled version is too old (out of sync with derper binary) May I ask what the reason is and how to solve it. thank you.
orangepi3-lts 5.16.17-sun50iw6 https://github.com/tailscale/tailscale/issues/3.0.8 SMP Tue Sep 6 18:22:49 CST 2022 aarch64 aarch64 aarch64 GNU/Linux，Client: Docker Engine - Community Version: 26.1.3 Context: default Debug Mode: false Remove the upgrade and use the old version of Derper and Tailscale 1.68.1 to ensure normal operation.
Hi @chdeast,
This error typically occurs when there's a version mismatch between your derper server and the Tailscale client. Here are a few things to check:
1. Update the Docker image Make sure you're using the latest version of the derper-docker image:
docker pull fredliang44/derper:latest
2. Check your derper version You can verify which Tailscale version your derper container is running by checking the logs or running:
docker exec <container_name> /app/derper -version
3. Client-side troubleshooting
- Ensure your Tailscale client is actually updated:
tailscale version - Try restarting the Tailscale service:
sudo tailscale down && sudo tailscale up - Clear any cached connections:
sudo tailscale logout && sudo tailscale login
4. Server-side restart Sometimes a simple container restart helps sync versions:
docker restart <derper_container_name>
The derper server needs to be running a compatible version with your Tailscale clients. Since you mentioned you're on 1.68.2, make sure the Docker image has been updated to include this version.
Can you share the output of docker logs <derper_container> and tailscale version from your client? This will help identify the exact version mismatch.
