headscale/config-example.yaml

181 lines
5 KiB
YAML
Raw Normal View History

2021-10-19 22:17:08 +00: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 17:27:11 +00:00
# The url clients will connect to.
# Typically this will be a domain like:
#
# https://myheadscale.example.com:443
#
2021-10-19 22:17:08 +00:00
server_url: http://127.0.0.1:8080
2021-10-22 17:27:11 +00:00
# Address to listen to / bind to on the server
#
2021-10-19 22:17:08 +00:00
listen_addr: 0.0.0.0:8080
2021-10-22 17:27:11 +00:00
2022-02-12 19:08:59 +00: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
# Private key used encrypt the traffic between headscale
# and Tailscale clients.
# The private key file which will be
2021-12-01 13:34:08 +00:00
# autogenerated if it's missing
private_key_path: /var/lib/headscale/private.key
2021-12-01 13:34:08 +00: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
# 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 20:30:51 +00: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
#
# This option is mostly interesting for people hosting
# their own DERP servers:
# https://tailscale.com/kb/1118/custom-derp-servers/
#
# paths:
# - /etc/headscale/derp-example.yaml
paths: []
2021-10-24 20:30:51 +00: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
# How often should we check for DERP updates?
2021-10-24 20:30:51 +00:00
update_frequency: 24h
2021-10-22 17:27:11 +00:00
# Disables the automatic check for headscale updates on startup
disable_check_updates: false
# Time before an inactive ephemeral node is deleted?
2021-10-19 22:17:08 +00:00
ephemeral_node_inactivity_timeout: 30m
2021-10-22 17:27:11 +00:00
# SQLite config
db_type: sqlite3
db_path: /var/lib/headscale/db.sqlite
2021-10-19 22:17:08 +00:00
# # Postgres config
# db_type: postgres
# db_host: localhost
# db_port: 5432
# db_name: headscale
# db_user: foo
# db_pass: bar
### 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-19 22:17:08 +00:00
acme_url: https://acme-v02.api.letsencrypt.org/directory
# Email to register with ACME provider
acme_email: ""
2021-10-22 17:27:11 +00:00
# Domain name to request a TLS certificate for:
tls_letsencrypt_hostname: ""
# Path to store certificates and metadata needed by
# letsencrypt
tls_letsencrypt_cache_dir: /var/lib/headscale/cache
# 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-19 22:17:08 +00:00
tls_letsencrypt_challenge_type: HTTP-01
# 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 17:27:11 +00:00
## Use already defined certificates:
tls_cert_path: ""
tls_key_path: ""
2021-10-22 17:27:11 +00:00
log_level: info
2021-10-22 17:27:11 +00:00
# Path to a file containg ACL policies.
# Recommended path: /etc/headscale/acl.hujson
acl_policy_path: ""
2021-10-22 17:27:11 +00: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-19 22:17:08 +00:00
dns_config:
# List of DNS servers to expose to clients.
2021-10-19 22:17:08 +00:00
nameservers:
- 1.1.1.1
# 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-19 22:17:08 +00:00
domains: []
2021-10-22 17:27:11 +00:00
# Whether to use [MagicDNS](https://tailscale.com/kb/1081/magicdns/).
# Only works if there is at least a nameserver defined.
2021-10-19 22:17:08 +00:00
magic_dns: true
# 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-19 22:17:08 +00:00
base_domain: example.com
# 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
unix_socket_permission: "0770"
#
2021-10-31 09:40:43 +00:00
# headscale supports experimental OpenID connect support,
# it is still being tested and might have some bugs, please
# help us test it.
# OpenID Connect
2021-10-30 15:33:01 +00:00
# oidc:
# issuer: "https://your-oidc.issuer.com/path"
# client_id: "your-oidc-client-id"
# client_secret: "your-oidc-client-secret"
#
2021-10-31 09:40:43 +00:00
# # Domain map is used to map incomming users (by their email) to
# # a namespace. The key can be a string, or regex.
2021-10-30 15:33:01 +00:00
# domain_map:
# ".*": default-namespace