PuppyIP Resource Center
Network And Account Troubleshooting 5 min Published 2026-11-20

Tailscale 1.104.x login timeout on a work network? Check the 1.104.7 TLS fix

If Tailscale login or device registration times out or the connection resets during TLS, check the running client version. The compatibility fix shipped in 1.104.7. Update through your organization's approved channel and repeat the same operation on the same device and network.

Tailscale TLS Network troubleshooting Control plane

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Tailscale 1.104.7 updated to Go 1.27.4 to fix control-plane TLS handshakes interrupted by some middleboxes. Version 1.104.6 did not include the fix.
  • Working DNS or a successful TCP 443 connection only checks earlier stages. Verify that the client itself can complete login or registration.
  • If the update doesn't resolve the problem, share the version, timestamp, and connection error with your network administrator to check clock accuracy, outbound HTTPS, and TLS inspection records.

Check the affected versions and symptoms

Tailscale released 1.104.7 on November 12, 2026. Its release notes say the update to Go 1.27.4 fixed a compatibility problem in which some middleboxes interrupted the control-plane connection when handling the initial TLS ClientHello. A maintainer had previously clarified that 1.104.6 did not include the fix. A project contributor closed the issue on November 17 after 1.104.7 shipped.

If login, device registration, or a control-plane reconnect times out, or if you see <code>connection reset by peer</code>, record the operating system, running Tailscale version, time, and network. On desktop, check the app's version information. For a container or a managed package, check the Tailscale version in the running instance. The package that delivers it may have a different version number.

Why the client can fail even when TCP 443 connects

DNS resolves a name to an address. TCP success confirms that a transport connection can open. TLS still has to complete its own handshake. The public issue includes a case where the client established TCP and then timed out during TLS. A browser loading an ordinary website provides a separate check of general internet access.

Record whether the failed action was login or registration, or communication between two devices that were already signed in. The first involves the client and control plane. The second can also involve device availability, access policy, or the relay path. If existing devices still communicate while a new device fails to register, record the registration failure explicitly.

Verify the update on the same device and network

Use your organization's approved update channel to install a supported stable version that includes the fix, starting with 1.104.7. Confirm the updated app or background process is actually running. Then repeat the failing operation on the same device, approved network, and account. Test the original login, registration, or reconnect without signing out other working devices.

Compare what the Tailscale client reports before and after the update. Record whether login finished, whether the device registered, and whether the timeout or reset returned. Holding the device and network steady makes the comparison easier to interpret. If the network changed too, record it separately.

What to give the administrator if the failure persists

Check the device clock and time zone and note the local time of the error. Share the client version, operating system, failed step, and relevant error lines with the network administrator. Keep the report focused and remove tokens, account details, or sign-in links from excerpts.

Ask the administrator to compare the relevant control-plane destinations with Tailscale's firewall documentation and your organization's policy, and to check DNS, outbound HTTPS, and TLS inspection records for that timestamp. A handshake timeout identifies the stage where the connection stopped. If the administrator finds an explicit policy denial, follow your organization's service approval and network change process.

Sources

Frequently Asked Questions

Does Tailscale 1.104.6 include this fix?

The maintainer confirmed that 1.104.6 shipped without it. The Tailscale 1.104.7 release notes list the fix.

If TCP 443 connects, is Tailscale working again?

Verify that the client completes the TLS handshake and the original login or registration step. TCP success is an intermediate result.

What should I do if tls-connection-failed still appears after updating?

Confirm the new version is running, check the device clock, and record the operation that failed. Your administrator can review outbound HTTPS and TLS inspection records for that time.