GuidesSecurity

tailscale up requires mentioning all non-default flags: the fix

tailscale up refuses one new flag on a server already up. When to copy the line it prints, what --reset drops, and tailscale set, which changes one setting.

November 14, 2026The Everpod team
The short answer

tailscale up treats the flags you give it as the whole of the machine’s settings. Run it again with one new flag on a server that already has others, and it refuses rather than switch those others back to their defaults. To change one setting, use tailscale set instead: sudo tailscale set --ssh, sudo tailscale set --advertise-exit-node or sudo tailscale set --exit-node=<name> leave everything else as it is. The command the error prints is safe to copy when you want every current setting kept. Adding --reset is the one to be careful with: every setting you did not retype goes back to its default, tags included.

What the message means

The full message, as the CLI prints it:

Error: changing settings via 'tailscale up' requires mentioning all
non-default flags. To proceed, either re-run your command with --reset or
use the command below to explicitly mention the current value of
all non-default settings:

	tailscale up --ssh --accept-routes --advertise-exit-node
Copied

The last line is built from your machine, so yours will differ: it starts with the flags you just typed, then adds every setting currently away from its default, in alphabetical order. Here the server already advertised itself as an exit node and accepted other devices’ routes, and the new command asked only for --ssh.

The reason is in how tailscale up reads its flags. Tailscale’s reference says plainly that flags are not persisted between runs, and the command’s own help says that if flags are given, they “must be the complete set of desired settings.” A flag you leave out means its default. Rather than quietly stop advertising the exit node because the new command did not mention it, the CLI stops and shows you what a complete command would be. Running tailscale up with no flags at all never prints this: it brings the connection up and changes nothing.

Change one setting with tailscale set

tailscale set exists for exactly this. In the words of Tailscale’s CLI reference, “Unlike tailscale up, this command does not require the complete set of desired settings.” It changes what you name and nothing else, and it has no defaults to fall back to. The common cases on a Linux server:

sudo tailscale set --ssh                          # turn on Tailscale SSH
sudo tailscale set --advertise-exit-node          # offer this machine as an exit node
sudo tailscale set --exit-node=<ip-or-name>       # send this machine's traffic through one
sudo tailscale set --exit-node=                   # stop using an exit node
sudo tailscale set --exit-node-allow-lan-access=true
sudo tailscale set --accept-routes                # accept other devices' subnet routes
sudo tailscale set --advertise-routes=10.0.0.0/24 # advertise a subnet
Copied

Turning a setting off is the same flag with a false or empty value, such as --ssh=false or --exit-node=. An advertised exit node still needs approving in the admin console before anything routes through it, and a server sending its traffic through one needs the policy to allow it; setting up an exit node for a cloud server covers both ends.

Two things differ from up. If your SSH session to the server arrives over Tailscale, switching --ssh on or off moves port 22 on that address between the server’s own sshd and Tailscale SSH, so the CLI warns that your session will disconnect and asks before going on; --accept-risk=lose-ssh skips the question, which a script needs. Run it from a session on the server’s public address or the provider’s console if you want to stay connected. And tailscale set does not print the IP forwarding and UDP GRO warnings that tailscale up prints when a machine advertises routes or an exit node, so a forwarding problem on an exit node set up this way stays silent until traffic fails.

Tags are the exception

tailscale set has no --advertise-tags flag. To tag a server that is already on the tailnet, the simplest route is the admin console: Machines, the menu at the end of the server’s row, Edit tags. Tailscale’s tags documentation notes that the tag has to exist in the tailnet policy file first. From the command line, take the line the error printed, add --advertise-tags=tag:<name> to it, and run that with sudo. Order matters for a server you reach only over Tailscale SSH: a tagged machine falls outside Tailscale’s default SSH rule, so the policy needs an SSH rule for the tag before the tag goes on, as locking down an AI agent’s server with tags and Tailscale SSH explains.

When to copy the command it prints

The printed line restates every current setting plus your change, so running it (with sudo, which the line leaves off) does what you meant and keeps everything else. It is the right choice when you are changing something tailscale set cannot, such as the tags above, or when you want a single command that records the machine’s full configuration, for a setup script or your notes.

Read it before running it. Every flag in it after the ones you typed is a setting the machine has now, and some may be ones you forgot, set by an earlier command or by someone else. If one of them should not be there, edit it out of the line and the setting returns to its default; that is a deliberate change, made with the setting in front of you. Flags that are not settings, such as --auth-key and --force-reauth, are never added to the line and never need repeating.

What --reset drops

--reset, in Tailscale’s description, will “reset unspecified settings to default values.” It makes the error go away by doing exactly what the error was protecting you from. sudo tailscale up --reset --ssh on the server above turns Tailscale SSH on and, without a word, stops advertising the exit node and stops accepting routes. Anything else you had set and did not retype goes the same way: a custom hostname, DNS settings, a subnet you were advertising. Tags are compared like any other setting, so a --reset line without --advertise-tags asks for the server’s tags to be removed, and on a server whose SSH access is granted to a tag, that is access you depend on.

--reset is the right tool when you do want a clean slate and are about to state the whole configuration in one line. To check what a server has before deciding, tailscale debug prefs prints its current settings, and the error itself is a readable list of everything that is not a default. For the server behind a private agent setup with no inbound ports, where Tailscale is the only way in, the difference between set and up --reset can be the difference between a changed setting and a trip to the provider’s web console.

Run Claude Code, Codex, OpenCode, Pi, Hermes or OpenClaw on an always-on developer pod.

A developer pod is a permanent cloud computer (VPS), set up and secured for you, with your pick of Claude Code, Codex, OpenCode, Pi, Hermes and OpenClaw installed. Run more agents at once than your laptop can hold, and keep them working when it’s closed. From $24 a month, built in about ten minutes.