# No home relay server

Last validated Aug 1, 2025

This topic explains a message that may appear in the Tailscale client and the actions you can take to address it. For a list of currently documented messages in the Tailscale admin console and client, refer to the main [Messages][kb-messages] topic.

## Message displayed in the client

No home relay server
Tailscale could not connect to any relay server.

## Reference ID

`no-derp-home`

## Why you're seeing this message

This message indicates that the Tailscale client is unable to connect to any DERP (Designated Encrypted Routing Protocol) relay server, which Tailscale uses as a fallback method for routing traffic when direct peer-to-peer connections are not possible.

Here are some reasons why this message might display:

* Issue with network or internet connectivity.
* Issue with firewall configuration.
* Issues with the Tailscale clients installation or upgrade.
* DERP server availability issues.

## What to do

Here are some things you can try to resolve this issue:

* Restart your Tailscale client using the client UI, or run the CLI commands `tailscale down` followed by `tailscale up`.
* Check your internet connection.
* If you are using a firewall, verify that the ports and domains used for connecting to Tailscale are not blocked.

## Additional information

* For information about the ports and domain names used to communicate with Tailscale, refer to [What firewall ports should I open to use Tailscale?][kb-firewall-ports].
* For information about the Designated Encrypted Routing Protocol, refer to [DERP servers][kb-derp-server].

[kb-derp-server]: /docs/reference/derp-servers

[kb-firewall-ports]: /docs/reference/faq/firewall-ports

[kb-messages]: /docs/reference/messages