{"slug":"tailscale-serve-command","title":"tailscale serve command","tags":["tailscale"],"agent_summary":"Last validated: Jan 26, 2026","trigger_phrases":[],"runnable":false,"markdown":"\r\n# tailscale serve command\r\n\r\nLast validated: Jan 26, 2026\r\n\r\nThe CLI commands for both Tailscale Funnel and Tailscale Serve have changed in the 1.52 version of the Tailscale client. If you've used Funnel or Serve in previous versions, we recommend reviewing the CLI documentation.\r\n\r\n`tailscale serve` lets you share a local service securely within your Tailscale network (known as a tailnet).\r\n\r\n```shell\r\ntailscale serve [flags] \r\n```\r\n\r\nYou can also choose to use [Tailscale Funnel](https://tailscale.com/docs/features/tailscale-funnel) with the [`tailscale funnel`](https://tailscale.com/docs/reference/tailscale-cli/funnel) command to expose your service publicly, open to the entire internet.\r\n\r\nSubcommands:\r\n\r\n- [`status`](https://tailscale.com/docs/reference/tailscale-cli/serve#get-the-status) Gets the status\r\n- [`reset`](https://tailscale.com/docs/reference/tailscale-cli/serve#reset-tailscale-serve) Resets the configuration\r\n- [`drain`](https://tailscale.com/docs/reference/tailscale-cli/serve#drain) Drain a [Service](https://tailscale.com/docs/features/tailscale-services)\r\n- [`advertise`](https://tailscale.com/docs/reference/tailscale-cli/serve#advertise) Advertise a [Service](https://tailscale.com/docs/features/tailscale-services)\r\n- [`get-config`](https://tailscale.com/docs/reference/tailscale-cli/serve#get-service-config) Get [Service](https://tailscale.com/docs/features/tailscale-services) configuration\r\n- [`set-config`](https://tailscale.com/docs/reference/tailscale-cli/serve#set-service-config) Set [Service](https://tailscale.com/docs/features/tailscale-services) configuration\r\n\r\nFor various use cases and examples, refer to [Tailscale Serve examples](https://tailscale.com/docs/reference/examples/serve).\r\n\r\n## [Serve command flags](https://tailscale.com/docs/reference/tailscale-cli/serve\\#serve-command-flags)\r\n\r\nAvailable flags:\r\n\r\n- `--accept-app-caps=` [App capabilities](https://tailscale.com/docs/features/access-control/grants/grants-app-capabilities) to forward to the server (specify multiple capabilities with a comma-separated list).\r\n- `--bg` Determines whether the command should run as a background process.\r\n- `--http=` Expose an HTTP server at the specified port.\r\n- `--https=` Expose an HTTPS server at the specified port (default).\r\n- `--proxy-protocol=` PROXY protocol version (1 or 2) for TCP forwarding.\r\n- `--service=` Serve for a [Tailscale Service](https://tailscale.com/docs/features/tailscale-services) with a distinct virtual IP instead of the device's IP address.\r\n- `--set-path=` Appends the specified path to the base URL for accessing the underlying service.\r\n- `--tcp=` Expose a TCP forwarder to forward TCP packets at the specified port.\r\n- `--tls-terminated-tcp=` Expose a TCP forwarder to forward TLS-terminated TCP packets at the specified port.\r\n- `--tun` Configure a [Layer 3 Service](https://tailscale.com/docs/features/tailscale-services#layer-3-endpoints-network-layer) to forward all traffic to the local machine (default false); only supported for Services.\r\n- `--yes` Update without interactive prompts.\r\n\r\nThe `tailscale serve` command accepts a target that can be a file, directory, text, or most commonly, the location to a service running on the local device. You can write the location to the local service as a port number (for example, `3000`), a partial URL (for example, `localhost:3000`), or a full URL including a path (for example, `tcp://localhost:3000/foo`, `https+insecure://localhost:3000/foo`).\r\n\r\n## [Use HTTPS and HTTP servers](https://tailscale.com/docs/reference/tailscale-cli/serve\\#use-https-and-http-servers)\r\n\r\n```shell\r\ntailscale serve --https= [off]\r\ntailscale serve --http= [off]\r\n```\r\n\r\nThe `serve` offers an HTTPS and HTTP server that has a few modes: a reverse proxy, a file server, and a static text server. HTTPS traffic uses an automatically provisioned TLS certificate. By default, the device's Tailscale daemon terminates the HTTPS connection.\r\n\r\n- `--https=` or `http=` Specifies the port to listen on\r\n\r\n- `--set-path` Is a slash-separated URL path. The root-level mount point would be `/` and would be matched by making a request to `https://my-node.example.ts.net/`, for example. For more information on how these path patterns are matched, refer to the Go [ServeMux](https://pkg.go.dev/net/http#ServeMux) documentation. Our mount points behave similarly.\r\n\r\n- `` Serve provides 4 options for serving content: an HTTP reverse proxy, a file, a directory, and static text. A reverse proxy lets you forward requests to a local HTTP web server. Providing a local file path provides the ability to serve files or directories of files. Serving static text is available mostly for debugging purposes and serves a static response.\r\n - **Reverse proxy**\r\n\r\n To serve as a reverse proxy to a local backend, provide the location of the `` argument. You can write the location to the local service as a port number (for example, `3000`), a partial URL (for example, `localhost:3000`), or a full URL including a path (for example, `tcp://localhost:3000/foo`, `https+insecure://localhost:3000/foo`). Note that only `http://127.0.0.1` is supported for proxies.\r\n\r\n Example: `tailscale serve localhost:3000`\r\n\r\n Or, to serve over HTTP:\r\n\r\n Example: `tailscale serve --http=80 localhost:3000`\r\n\r\n HTTP servers are accessible using short MagicDNS names like `http://my-node`\r\n\r\n - **File server**\r\n\r\n Provide a full, absolute path to the file or directory of files you wish to serve. If you specify a directory, this renders a directory listing with links to files and subdirectories.\r\n\r\n Example: `tailscale serve /home/alice/blog/index.html`\r\n\r\n Due to macOS app sandbox limitations, this option only works when using Tailscale's [open source variant](https://tailscale.com/docs/concepts/macos-variants). If you've installed Tailscale on macOS through the Mac App Store or as a Standalone variant system extension, you can use Serve to share ports but not files or directories.\r\n\r\n - **Static text server**\r\n\r\n Specifying `text:` as a `` configures a static plain-text server.\r\n\r\n Example: `tailscale serve text:\"Hello, world!\"`\r\n\r\n## [Use the PROXY protocol](https://tailscale.com/docs/reference/tailscale-cli/serve\\#use-the-proxy-protocol)\r\n\r\n```shell\r\ntailscale serve --proxy-protocol= \r\n```\r\n\r\nFor most situations, users will likely use version `2`.\r\n\r\nThe [PROXY protocol](https://www.haproxy.com/blog/use-the-proxy-protocol-to-preserve-a-clients-ip-address) is a minimal network protocol that preserves information about a proxied connection (typically, the source IP address) through a proxy or load balancer and to the backend target. This lets the service that you're exposing with Serve determine the original IP address and port for connecting clients.\r\n\r\nFor example:\r\n\r\n```shell\r\ntailscale serve --proxy-protocol=2 --tls-terminated-tcp=443 tcp://127.0.0.1:9899\r\n```\r\n\r\nThis command will return information similar to the following:\r\n\r\n```shell\r\nAvailable within your tailnet:\r\n\r\n|-- tcp://serve-test.example.ts.net:443 (TLS terminated, PROXY protocol v2)\r\n|-- tcp://100.101.102.103:443\r\n|-- tcp://[fd7a:115c:a1e0::1111:2222]:443\r\n|--> tcp://127.0.0.1:9899\r\n\r\nPress Ctrl+C to exit.\r\n```\r\n\r\nThe backend (running on `localhost:9899`) then gets the original source IP and port through the PROXY protocol.\r\n\r\n## [Use a TCP forwarder](https://tailscale.com/docs/reference/tailscale-cli/serve\\#use-a-tcp-forwarder)\r\n\r\n```shell\r\ntailscale serve --tcp= tcp://localhost: [off]\r\ntailscale serve --tls-terminated-tcp= tcp://localhost: [off]\r\n```\r\n\r\nThe `serve` command offers a TCP forwarder that you can use to forward both raw TCP packets and TLS-terminated TCP packets to a local TCP server like Caddy or other TCP-based protocols such as SSH or RDP. By default, the TCP forwarder forwards raw packets.\r\n\r\n- `--tcp=` Sets up a raw TCP forwarder listening on the specified port. You can use any valid port number.\r\n\r\n- `--tls-terminated-tcp=` Sets up a TLS-terminated TCP forwarder listening on the specified port. You can use any valid port number.\r\n\r\n- `tcp://localhost:` Specifies the local port to forward packets to.\r\n\r\n\r\n## [Use a valid certificate](https://tailscale.com/docs/reference/tailscale-cli/serve\\#use-a-valid-certificate)\r\n\r\n```shell\r\ntailscale serve \r\n```\r\n\r\nIf you have a valid certificate, use `https` in the `` argument.\r\n\r\nExample: `tailscale serve https://localhost:8443`\r\n\r\n## [Ignore invalid and self-signed certificate checks](https://tailscale.com/docs/reference/tailscale-cli/serve\\#ignore-invalid-and-self-signed-certificate-checks)\r\n\r\n```shell\r\ntailscale serve \r\n```\r\n\r\nIf you run a local web server using HTTPS with a self-signed or otherwise invalid certificate, you can specify `https+insecure` as a special pseudo-protocol for your `tailscale serve` commands.\r\n\r\nExample: `tailscale serve https+insecure://localhost:8443`\r\n\r\n## [Get the status](https://tailscale.com/docs/reference/tailscale-cli/serve\\#get-the-status)\r\n\r\n```shell\r\ntailscale serve status [--json]\r\n```\r\n\r\nTo get the status of your servers, you can use the `status` subcommand. This lists all the servers that are currently running on your device.\r\n\r\n- `--json` If you want to get the status in JSON format, you can provide the `--json` argument.\r\n\r\nExample: `tailscale serve status --json`\r\n\r\n\r\nCurrently, `tailscale serve status` and `tailscale serve status --json` return different information. If you are seeking a list of Services, you can use the following command:\r\n\r\n```shell\r\ntailscale serve get-config --all\r\n```\r\n\r\nFor more information, refer to our [GitHub issue](https://github.com/tailscale/tailscale/issues/18289).\r\n\r\n## [Reset Tailscale Serve](https://tailscale.com/docs/reference/tailscale-cli/serve\\#reset-tailscale-serve)\r\n\r\n```shell\r\ntailscale serve reset\r\n```\r\n\r\nTo clear out the current `tailscale serve` configuration, use the `reset` subcommand.\r\n\r\n## [Disable Tailscale Serve](https://tailscale.com/docs/reference/tailscale-cli/serve\\#disable-tailscale-serve)\r\n\r\n- `[off]` To turn off a `tailscale serve` command, you can add `off` to the end of the command you used to turn it on. This will remove the server from the list of active servers. In `off` commands, the `` argument is optional, but all original flags are required.\r\n\r\nIf this command turned on a server:\r\n\r\n```shell\r\ntailscale serve --https=443 /home/alice/blog/index.html\r\n```\r\n\r\nYou can turn it off by running:\r\n\r\n```shell\r\ntailscale serve --https=443 /home/alice/blog/index.html off\r\n```\r\n\r\nYou can omit the `` argument, so these 2 commands are equivalent:\r\n\r\n```shell\r\ntailscale serve --https=443 --set-path=/foo /home/alice/blog/index.html off\r\ntailscale serve --https=443 --set-path=/foo off\r\n```\r\n\r\n## [Get service config](https://tailscale.com/docs/reference/tailscale-cli/serve\\#get-service-config)\r\n\r\n```shell\r\ntailscale serve get-config [flags]\r\n```\r\n\r\nGet the configuration for [Services](https://tailscale.com/docs/features/tailscale-services) that this node is currently hosting in a format that can later be provided to `set-config`. This can be used to declare the configuration for a service host.\r\n\r\nAvailable flags:\r\n\r\n- `--all` Read configuration from all services.\r\n- `--service=` Read configuration from a specific service.\r\n\r\n## [Set service config](https://tailscale.com/docs/reference/tailscale-cli/serve\\#set-service-config)\r\n\r\n```shell\r\ntailscale serve set-config [flags]\r\n```\r\n\r\nRead the provided [configuration file](https://tailscale.com/docs/reference/tailscale-services-configuration-file) and use it to declare the configuration for either a single [Service](https://tailscale.com/docs/features/tailscale-services) or for all Services that this node is hosting.\r\n\r\n- `--all` Apply configuration to all services.\r\n- `--service=` Apply configuration to a specific service.\r\n\r\n## [Drain](https://tailscale.com/docs/reference/tailscale-cli/serve\\#drain)\r\n\r\n```shell\r\ntailscale serve drain \r\n```\r\n\r\nDrain a [Service](https://tailscale.com/docs/features/tailscale-services) from the current node.\r\n\r\nUse this command to gracefully remove a Service from the current node without disrupting existing connections. No new connections will be accepted, but existing connections will continue to work until they are closed.\r\n\r\n`` should be a Service name. For example: `svc:my-service`.\r\n\r\n## [Advertise](https://tailscale.com/docs/reference/tailscale-cli/serve\\#advertise)\r\n\r\n```shell\r\ntailscale serve advertise \r\n```\r\n\r\nAdvertise this node as a [Service](https://tailscale.com/docs/features/tailscale-services) host for the tailnet.\r\n\r\nThis command can be useful to bring a Service host back online after it has been [drained](https://tailscale.com/docs/reference/tailscale-cli/serve#drain). This is not needed if you are using `tailscale serve` to initialize a Service.\r\n\r\n`` should be a Service name. For example: `svc:my-service`.\r\n\r\nAvailable flags:\r\n\r\n- `--service=` Apply config to a particular service.\r\n\r\n## [Effects of rebooting and restarting](https://tailscale.com/docs/reference/tailscale-cli/serve\\#effects-of-rebooting-and-restarting)\r\n\r\nIf you use the `tailscale serve` command with the [`-bg`](https://tailscale.com/docs/reference/tailscale-cli/serve#serve-command-flags) flag, it runs persistently in the background until you [disable](https://tailscale.com/docs/reference/tailscale-cli/serve#disable-tailscale-serve) it. When you reboot the device or restart Tailscale from the command line using [`tailscale down`](https://tailscale.com/docs/reference/tailscale-cli#down) and [`tailscale up`](https://tailscale.com/docs/reference/tailscale-cli#up), Serve automatically resumes sharing.\r\n\r\nIf you use the `tailscale serve` command without the `-bg` flag, then reboot the device or restart Tailscale from the command line, you must restart Serve manually to resume sharing.\r\n\r\nWhen you use the `tailscale serve` command with [Tailscale Services](https://tailscale.com/docs/features/tailscale-services), it runs in the background by default.\r\n\r\n![Project Logo](https://cdn.brandfetch.io/tailscale.com/fallback/lettermark/theme/dark/h/256/w/256/icon?c=1bfwsmEH20zzEfSNTed)\r\n\r\nAsk AI\r\n\r\nreCAPTCHA\r\n\r\nRecaptcha requires verification.\r\n\r\nprotected by **reCAPTCHA**\r\n","html":"

tailscale serve command

\n

Last validated: Jan 26, 2026

\n

The CLI commands for both Tailscale Funnel and Tailscale Serve have changed in the 1.52 version of the Tailscale client. If you've used Funnel or Serve in previous versions, we recommend reviewing the CLI documentation.

\n

tailscale serve lets you share a local service securely within your Tailscale network (known as a tailnet).

\n
tailscale serve [flags] <target>\n
\n

You can also choose to use Tailscale Funnel with the tailscale funnel command to expose your service publicly, open to the entire internet.

\n

Subcommands:

\n\n

For various use cases and examples, refer to Tailscale Serve examples.

\n

Serve command flags

\n

Available flags:

\n
    \n
  • --accept-app-caps=<capability-1,capability-2,...> App capabilities to forward to the server (specify multiple capabilities with a comma-separated list).
    • \n
  • --bg Determines whether the command should run as a background process.
    • \n
  • --http=<port> Expose an HTTP server at the specified port.
    • \n
  • --https=<port> Expose an HTTPS server at the specified port (default).
    • \n
  • --proxy-protocol=<version> PROXY protocol version (1 or 2) for TCP forwarding.
    • \n
  • --service=<virtual-ip> Serve for a Tailscale Service with a distinct virtual IP instead of the device's IP address.
    • \n
  • --set-path=<path> Appends the specified path to the base URL for accessing the underlying service.
    • \n
  • --tcp=<port> Expose a TCP forwarder to forward TCP packets at the specified port.
    • \n
  • --tls-terminated-tcp=<port> Expose a TCP forwarder to forward TLS-terminated TCP packets at the specified port.
    • \n
  • --tun Configure a Layer 3 Service to forward all traffic to the local machine (default false); only supported for Services.
    • \n
  • --yes Update without interactive prompts.
    • \n
\n

The tailscale serve command accepts a target that can be a file, directory, text, or most commonly, the location to a service running on the local device. You can write the location to the local service as a port number (for example, 3000), a partial URL (for example, localhost:3000), or a full URL including a path (for example, tcp://localhost:3000/foo, https+insecure://localhost:3000/foo).

\n

Use HTTPS and HTTP servers

\n
tailscale serve --https=<port> <target> [off]\r\ntailscale serve --http=<port> <target> [off]\n
\n

The serve offers an HTTPS and HTTP server that has a few modes: a reverse proxy, a file server, and a static text server. HTTPS traffic uses an automatically provisioned TLS certificate. By default, the device's Tailscale daemon terminates the HTTPS connection.

\n
    \n
  • \n

    --https=<port> or http=<port> Specifies the port to listen on

    \n
    • \n
  • \n

    --set-path Is a slash-separated URL path. The root-level mount point would be / and would be matched by making a request to https://my-node.example.ts.net/, for example. For more information on how these path patterns are matched, refer to the Go ServeMux documentation. Our mount points behave similarly.

    \n
    • \n
  • \n

    <target> Serve provides 4 options for serving content: an HTTP reverse proxy, a file, a directory, and static text. A reverse proxy lets you forward requests to a local HTTP web server. Providing a local file path provides the ability to serve files or directories of files. Serving static text is available mostly for debugging purposes and serves a static response.

    \n
      \n
    • \n

      Reverse proxy

      \n

      To serve as a reverse proxy to a local backend, provide the location of the <target> argument. You can write the location to the local service as a port number (for example, 3000), a partial URL (for example, localhost:3000), or a full URL including a path (for example, tcp://localhost:3000/foo, https+insecure://localhost:3000/foo). Note that only http://127.0.0.1 is supported for proxies.

      \n

      Example: tailscale serve localhost:3000

      \n

      Or, to serve over HTTP:

      \n

      Example: tailscale serve --http=80 localhost:3000

      \n

      HTTP servers are accessible using short MagicDNS names like http://my-node

      \n
      • \n
    • \n

      File server

      \n

      Provide a full, absolute path to the file or directory of files you wish to serve. If you specify a directory, this renders a directory listing with links to files and subdirectories.

      \n

      Example: tailscale serve /home/alice/blog/index.html

      \n

      Due to macOS app sandbox limitations, this option only works when using Tailscale's open source variant. If you've installed Tailscale on macOS through the Mac App Store or as a Standalone variant system extension, you can use Serve to share ports but not files or directories.

      \n
      • \n
    • \n

      Static text server

      \n

      Specifying text:<value> as a <target> configures a static plain-text server.

      \n

      Example: tailscale serve text:\"Hello, world!\"

      \n
      • \n
    \n
    • \n
\n

Use the PROXY protocol

\n
tailscale serve --proxy-protocol=<version> <target>\n
\n

For most situations, users will likely use version 2.

\n

The PROXY protocol is a minimal network protocol that preserves information about a proxied connection (typically, the source IP address) through a proxy or load balancer and to the backend target. This lets the service that you're exposing with Serve determine the original IP address and port for connecting clients.

\n

For example:

\n
tailscale serve --proxy-protocol=2 --tls-terminated-tcp=443 tcp://127.0.0.1:9899\n
\n

This command will return information similar to the following:

\n
Available within your tailnet:\r\n\r\n|-- tcp://serve-test.example.ts.net:443 (TLS terminated, PROXY protocol v2)\r\n|-- tcp://100.101.102.103:443\r\n|-- tcp://[fd7a:115c:a1e0::1111:2222]:443\r\n|--> tcp://127.0.0.1:9899\r\n\r\nPress Ctrl+C to exit.\n
\n

The backend (running on localhost:9899) then gets the original source IP and port through the PROXY protocol.

\n

Use a TCP forwarder

\n
tailscale serve --tcp=<port> tcp://localhost:<local-port> [off]\r\ntailscale serve --tls-terminated-tcp=<port> tcp://localhost:<local-port> [off]\n
\n

The serve command offers a TCP forwarder that you can use to forward both raw TCP packets and TLS-terminated TCP packets to a local TCP server like Caddy or other TCP-based protocols such as SSH or RDP. By default, the TCP forwarder forwards raw packets.

\n
    \n
  • \n

    --tcp=<port> Sets up a raw TCP forwarder listening on the specified port. You can use any valid port number.

    \n
    • \n
  • \n

    --tls-terminated-tcp=<port> Sets up a TLS-terminated TCP forwarder listening on the specified port. You can use any valid port number.

    \n
    • \n
  • \n

    tcp://localhost:<local-port> Specifies the local port to forward packets to.

    \n
    • \n
\n

Use a valid certificate

\n
tailscale serve <https:target>\n
\n

If you have a valid certificate, use https in the <target> argument.

\n

Example: tailscale serve https://localhost:8443

\n

Ignore invalid and self-signed certificate checks

\n
tailscale serve <https+insecure:target>\n
\n

If you run a local web server using HTTPS with a self-signed or otherwise invalid certificate, you can specify https+insecure as a special pseudo-protocol for your tailscale serve commands.

\n

Example: tailscale serve https+insecure://localhost:8443

\n

Get the status

\n
tailscale serve status [--json]\n
\n

To get the status of your servers, you can use the status subcommand. This lists all the servers that are currently running on your device.

\n
    \n
  • --json If you want to get the status in JSON format, you can provide the --json argument.
    • \n
\n

Example: tailscale serve status --json

\n

Currently, tailscale serve status and tailscale serve status --json return different information. If you are seeking a list of Services, you can use the following command:

\n
tailscale serve get-config --all\n
\n

For more information, refer to our GitHub issue.

\n

Reset Tailscale Serve

\n
tailscale serve reset\n
\n

To clear out the current tailscale serve configuration, use the reset subcommand.

\n

Disable Tailscale Serve

\n
    \n
  • [off] To turn off a tailscale serve command, you can add off to the end of the command you used to turn it on. This will remove the server from the list of active servers. In off commands, the <target> argument is optional, but all original flags are required.
    • \n
\n

If this command turned on a server:

\n
tailscale serve --https=443 /home/alice/blog/index.html\n
\n

You can turn it off by running:

\n
tailscale serve --https=443 /home/alice/blog/index.html off\n
\n

You can omit the <target> argument, so these 2 commands are equivalent:

\n
tailscale serve --https=443 --set-path=/foo /home/alice/blog/index.html off\r\ntailscale serve --https=443 --set-path=/foo off\n
\n

Get service config

\n
tailscale serve get-config <file> [flags]\n
\n

Get the configuration for Services that this node is currently hosting in a format that can later be provided to set-config. This can be used to declare the configuration for a service host.

\n

Available flags:

\n
    \n
  • --all Read configuration from all services.
    • \n
  • --service=<name> Read configuration from a specific service.
    • \n
\n

Set service config

\n
tailscale serve set-config <file> [flags]\n
\n

Read the provided configuration file and use it to declare the configuration for either a single Service or for all Services that this node is hosting.

\n
    \n
  • --all Apply configuration to all services.
    • \n
  • --service=<name> Apply configuration to a specific service.
    • \n
\n

Drain

\n
tailscale serve drain <service>\n
\n

Drain a Service from the current node.

\n

Use this command to gracefully remove a Service from the current node without disrupting existing connections. No new connections will be accepted, but existing connections will continue to work until they are closed.

\n

<service> should be a Service name. For example: svc:my-service.

\n

Advertise

\n
tailscale serve advertise <service>\n
\n

Advertise this node as a Service host for the tailnet.

\n

This command can be useful to bring a Service host back online after it has been drained. This is not needed if you are using tailscale serve to initialize a Service.

\n

<service> should be a Service name. For example: svc:my-service.

\n

Available flags:

\n
    \n
  • --service=<name> Apply config to a particular service.
    • \n
\n

Effects of rebooting and restarting

\n

If you use the tailscale serve command with the -bg flag, it runs persistently in the background until you disable it. When you reboot the device or restart Tailscale from the command line using tailscale down and tailscale up, Serve automatically resumes sharing.

\n

If you use the tailscale serve command without the -bg flag, then reboot the device or restart Tailscale from the command line, you must restart Serve manually to resume sharing.

\n

When you use the tailscale serve command with Tailscale Services, it runs in the background by default.

\n

\"Project

\n

Ask AI

\n

reCAPTCHA

\n

Recaptcha requires verification.

\n

protected by reCAPTCHA

\n"}