2021-10-20 00:17:08 +02:00
|
|
|
---
|
2022-01-02 20:42:35 +01:00
|
|
|
# headscale will look for a configuration file named `config.yaml` (or `config.json`) in the following order:
|
|
|
|
#
|
|
|
|
# - `/etc/headscale`
|
|
|
|
# - `~/.headscale`
|
|
|
|
# - current working directory
|
|
|
|
|
2021-10-22 19:27:11 +02:00
|
|
|
# The url clients will connect to.
|
2022-01-02 20:38:04 +01:00
|
|
|
# Typically this will be a domain like:
|
|
|
|
#
|
|
|
|
# https://myheadscale.example.com:443
|
|
|
|
#
|
2021-10-20 00:17:08 +02:00
|
|
|
server_url: http://127.0.0.1:8080
|
2021-10-22 19:27:11 +02:00
|
|
|
|
|
|
|
# Address to listen to / bind to on the server
|
2022-01-02 20:38:04 +01:00
|
|
|
#
|
2021-10-20 00:17:08 +02:00
|
|
|
listen_addr: 0.0.0.0:8080
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-02-12 20:08:59 +01:00
|
|
|
# Address to listen for gRPC.
|
|
|
|
# gRPC is used for controlling a headscale server
|
|
|
|
# remotely with the CLI
|
|
|
|
# Note: Remote access _only_ works if you have
|
|
|
|
# valid certificates.
|
|
|
|
grpc_listen_addr: 0.0.0.0:50443
|
|
|
|
|
2022-02-13 10:08:46 +01:00
|
|
|
# Allow the gRPC admin interface to run in INSECURE
|
|
|
|
# mode. This is not recommended as the traffic will
|
|
|
|
# be unencrypted. Only enable if you know what you
|
|
|
|
# are doing.
|
|
|
|
grpc_allow_insecure: false
|
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# Private key used encrypt the traffic between headscale
|
|
|
|
# and Tailscale clients.
|
|
|
|
# The private key file which will be
|
2021-12-01 14:34:08 +01:00
|
|
|
# autogenerated if it's missing
|
2022-01-02 19:11:36 +01:00
|
|
|
private_key_path: /var/lib/headscale/private.key
|
2021-12-01 14:34:08 +01:00
|
|
|
|
2022-01-28 22:13:45 +01:00
|
|
|
# List of IP prefixes to allocate tailaddresses from.
|
|
|
|
# Each prefix consists of either an IPv4 or IPv6 address,
|
|
|
|
# and the associated prefix length, delimited by a slash.
|
|
|
|
ip_prefixes:
|
|
|
|
- fd7a:115c:a1e0::/48
|
|
|
|
- 100.64.0.0/10
|
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# DERP is a relay system that Tailscale uses when a direct
|
|
|
|
# connection cannot be established.
|
|
|
|
# https://tailscale.com/blog/how-tailscale-works/#encrypted-tcp-relays-derp
|
|
|
|
#
|
|
|
|
# headscale needs a list of DERP servers that can be presented
|
|
|
|
# to the clients.
|
2021-10-24 22:30:51 +02:00
|
|
|
derp:
|
|
|
|
# List of externally available DERP maps encoded in JSON
|
|
|
|
urls:
|
|
|
|
- https://controlplane.tailscale.com/derpmap/default
|
|
|
|
|
|
|
|
# Locally available DERP map files encoded in YAML
|
2022-01-02 20:38:04 +01:00
|
|
|
#
|
|
|
|
# This option is mostly interesting for people hosting
|
|
|
|
# their own DERP servers:
|
|
|
|
# https://tailscale.com/kb/1118/custom-derp-servers/
|
|
|
|
#
|
2022-01-02 19:11:36 +01:00
|
|
|
# paths:
|
|
|
|
# - /etc/headscale/derp-example.yaml
|
2022-01-03 00:17:42 +01:00
|
|
|
paths: []
|
2021-10-24 22:30:51 +02:00
|
|
|
|
|
|
|
# If enabled, a worker will be set up to periodically
|
|
|
|
# refresh the given sources and update the derpmap
|
|
|
|
# will be set up.
|
|
|
|
auto_update_enabled: true
|
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# How often should we check for DERP updates?
|
2021-10-24 22:30:51 +02:00
|
|
|
update_frequency: 24h
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# Disables the automatic check for headscale updates on startup
|
2021-10-23 11:40:15 +02:00
|
|
|
disable_check_updates: false
|
2022-01-02 20:38:04 +01:00
|
|
|
|
|
|
|
# Time before an inactive ephemeral node is deleted?
|
2021-10-20 00:17:08 +02:00
|
|
|
ephemeral_node_inactivity_timeout: 30m
|
|
|
|
|
2021-10-22 19:27:11 +02:00
|
|
|
# SQLite config
|
2021-10-20 23:27:59 +02:00
|
|
|
db_type: sqlite3
|
2022-01-02 19:11:36 +01:00
|
|
|
db_path: /var/lib/headscale/db.sqlite
|
2021-10-20 00:17:08 +02:00
|
|
|
|
2021-10-22 19:14:29 +02:00
|
|
|
# # Postgres config
|
|
|
|
# db_type: postgres
|
|
|
|
# db_host: localhost
|
|
|
|
# db_port: 5432
|
|
|
|
# db_name: headscale
|
|
|
|
# db_user: foo
|
|
|
|
# db_pass: bar
|
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
### TLS configuration
|
|
|
|
#
|
|
|
|
## Let's encrypt / ACME
|
|
|
|
#
|
|
|
|
# headscale supports automatically requesting and setting up
|
|
|
|
# TLS for a domain with Let's Encrypt.
|
|
|
|
#
|
|
|
|
# URL to ACME directory
|
2021-10-20 00:17:08 +02:00
|
|
|
acme_url: https://acme-v02.api.letsencrypt.org/directory
|
2022-01-02 20:38:04 +01:00
|
|
|
|
|
|
|
# Email to register with ACME provider
|
2021-10-22 19:14:29 +02:00
|
|
|
acme_email: ""
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# Domain name to request a TLS certificate for:
|
2021-10-22 19:14:29 +02:00
|
|
|
tls_letsencrypt_hostname: ""
|
2022-01-02 20:38:04 +01:00
|
|
|
|
2022-01-30 13:26:28 +01:00
|
|
|
# Client (Tailscale/Browser) authentication mode (mTLS)
|
|
|
|
# Acceptable values:
|
|
|
|
# - disabled: client authentication disabled
|
|
|
|
# - relaxed: client certificate is required but not verified
|
|
|
|
# - enforced: client certificate is required and verified
|
2022-02-20 15:06:14 +01:00
|
|
|
tls_client_auth_mode: relaxed
|
2022-01-30 13:26:28 +01:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# Path to store certificates and metadata needed by
|
|
|
|
# letsencrypt
|
2022-01-02 19:11:36 +01:00
|
|
|
tls_letsencrypt_cache_dir: /var/lib/headscale/cache
|
2022-01-02 20:38:04 +01:00
|
|
|
|
|
|
|
# Type of ACME challenge to use, currently supported types:
|
|
|
|
# HTTP-01 or TLS_ALPN-01
|
|
|
|
# See [docs/tls.md](docs/tls.md) for more information
|
2021-10-20 00:17:08 +02:00
|
|
|
tls_letsencrypt_challenge_type: HTTP-01
|
2022-01-02 20:38:04 +01:00
|
|
|
# When HTTP-01 challenge is chosen, letsencrypt must set up a
|
|
|
|
# verification endpoint, and it will be listning on:
|
|
|
|
# :http = port 80
|
|
|
|
tls_letsencrypt_listen: ":http"
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
## Use already defined certificates:
|
2021-10-22 19:14:29 +02:00
|
|
|
tls_cert_path: ""
|
|
|
|
tls_key_path: ""
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2021-12-01 20:02:00 +01:00
|
|
|
log_level: info
|
|
|
|
|
2021-10-22 19:27:11 +02:00
|
|
|
# Path to a file containg ACL policies.
|
2022-01-02 20:38:04 +01:00
|
|
|
# Recommended path: /etc/headscale/acl.hujson
|
2021-10-22 19:14:29 +02:00
|
|
|
acl_policy_path: ""
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
## DNS
|
|
|
|
#
|
|
|
|
# headscale supports Tailscale's DNS configuration and MagicDNS.
|
|
|
|
# Please have a look to their KB to better understand the concepts:
|
|
|
|
#
|
|
|
|
# - https://tailscale.com/kb/1054/dns/
|
|
|
|
# - https://tailscale.com/kb/1081/magicdns/
|
|
|
|
# - https://tailscale.com/blog/2021-09-private-dns-with-magicdns/
|
|
|
|
#
|
2021-10-20 00:17:08 +02:00
|
|
|
dns_config:
|
2022-01-02 20:38:04 +01:00
|
|
|
# List of DNS servers to expose to clients.
|
2021-10-20 00:17:08 +02:00
|
|
|
nameservers:
|
2021-10-22 19:14:29 +02:00
|
|
|
- 1.1.1.1
|
2022-01-02 20:38:04 +01:00
|
|
|
|
|
|
|
# Split DNS (see https://tailscale.com/kb/1054/dns/),
|
|
|
|
# list of search domains and the DNS to query for each one.
|
|
|
|
#
|
|
|
|
# restricted_nameservers:
|
|
|
|
# foo.bar.com:
|
|
|
|
# - 1.1.1.1
|
|
|
|
# darp.headscale.net:
|
|
|
|
# - 1.1.1.1
|
|
|
|
# - 8.8.8.8
|
|
|
|
|
|
|
|
# Search domains to inject.
|
2021-10-20 00:17:08 +02:00
|
|
|
domains: []
|
2021-10-22 19:27:11 +02:00
|
|
|
|
2022-01-02 20:38:04 +01:00
|
|
|
# Whether to use [MagicDNS](https://tailscale.com/kb/1081/magicdns/).
|
|
|
|
# Only works if there is at least a nameserver defined.
|
2021-10-20 00:17:08 +02:00
|
|
|
magic_dns: true
|
2022-01-02 20:38:04 +01:00
|
|
|
|
|
|
|
# Defines the base domain to create the hostnames for MagicDNS.
|
|
|
|
# `base_domain` must be a FQDNs, without the trailing dot.
|
|
|
|
# The FQDN of the hosts will be
|
|
|
|
# `hostname.namespace.base_domain` (e.g., _myhost.mynamespace.example.com_).
|
2021-10-20 00:17:08 +02:00
|
|
|
base_domain: example.com
|
2021-10-30 16:08:16 +02:00
|
|
|
|
|
|
|
# Unix socket used for the CLI to connect without authentication
|
|
|
|
# Note: for local development, you probably want to change this to:
|
|
|
|
# unix_socket: ./headscale.sock
|
|
|
|
unix_socket: /var/run/headscale.sock
|
2022-01-28 19:58:22 +01:00
|
|
|
unix_socket_permission: "0770"
|
2022-01-02 20:38:04 +01:00
|
|
|
#
|
2021-10-31 10:40:43 +01:00
|
|
|
# headscale supports experimental OpenID connect support,
|
2021-10-30 17:35:58 +02:00
|
|
|
# it is still being tested and might have some bugs, please
|
|
|
|
# help us test it.
|
|
|
|
# OpenID Connect
|
2021-10-30 17:33:01 +02:00
|
|
|
# oidc:
|
|
|
|
# issuer: "https://your-oidc.issuer.com/path"
|
|
|
|
# client_id: "your-oidc-client-id"
|
|
|
|
# client_secret: "your-oidc-client-secret"
|
2021-10-30 17:35:58 +02:00
|
|
|
#
|
2021-10-31 10:40:43 +01:00
|
|
|
# # Domain map is used to map incomming users (by their email) to
|
2021-10-30 17:35:58 +02:00
|
|
|
# # a namespace. The key can be a string, or regex.
|
2021-10-30 17:33:01 +02:00
|
|
|
# domain_map:
|
|
|
|
# ".*": default-namespace
|