-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7944 from madhavajay/madhava/fixes_headscale
Upgrading Headscale / Tailscale
- Loading branch information
Showing
8 changed files
with
203 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,23 +10,28 @@ | |
# | ||
# https://myheadscale.example.com:443 | ||
# | ||
server_url: http://127.0.0.1:8080 | ||
server_url: http://0.0.0.0:8080 | ||
|
||
# Address to listen to / bind to on the server | ||
# | ||
# For production: | ||
# listen_addr: 0.0.0.0:8080 | ||
listen_addr: 0.0.0.0:8080 | ||
|
||
# Address to listen to /metrics, you may want | ||
# to keep this endpoint private to your internal | ||
# network | ||
# | ||
metrics_listen_addr: 127.0.0.1:9090 | ||
metrics_listen_addr: 0.0.0.0:9090 | ||
|
||
# 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. | ||
# | ||
# For production: | ||
# grpc_listen_addr: 0.0.0.0:50443 | ||
grpc_listen_addr: 0.0.0.0:50443 | ||
|
||
# Allow the gRPC admin interface to run in INSECURE | ||
|
@@ -35,15 +40,30 @@ grpc_listen_addr: 0.0.0.0:50443 | |
# are doing. | ||
grpc_allow_insecure: false | ||
|
||
# Private key used encrypt the traffic between headscale | ||
# Private key used to encrypt the traffic between headscale | ||
# and Tailscale clients. | ||
# The private key file which will be | ||
# autogenerated if it's missing | ||
private_key_path: /headscale/data/private_v2.key | ||
# The private key file will be autogenerated if it's missing. | ||
# | ||
private_key_path: /headscale/data/private.key | ||
|
||
# The Noise section includes specific configuration for the | ||
# TS2021 Noise protocol | ||
noise: | ||
# The Noise private key is used to encrypt the | ||
# traffic between headscale and Tailscale clients when | ||
# using the new Noise-based protocol. It must be different | ||
# from the legacy private key. | ||
private_key_path: /headscale/data/noise_private.key | ||
|
||
# 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. | ||
# It must be within IP ranges supported by the Tailscale | ||
# client - i.e., subnets of 100.64.0.0/10 and fd7a:115c:a1e0::/48. | ||
# See below: | ||
# IPv6: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#LL81C52-L81C71 | ||
# IPv4: https://github.com/tailscale/tailscale/blob/22ebb25e833264f58d7c3f534a8b166894a89536/net/tsaddr/tsaddr.go#L33 | ||
# Any other range is NOT supported, and it will cause unexpected issues. | ||
ip_prefixes: | ||
# - fd7a:115c:a1e0::/48 | ||
- 100.64.0.0/10 | ||
|
@@ -58,7 +78,7 @@ derp: | |
server: | ||
# If enabled, runs the embedded DERP server and merges it into the rest of the DERP config | ||
# The Headscale server_url defined above MUST be using https, DERP requires TLS to be in place | ||
enabled: true | ||
enabled: false | ||
|
||
# Region ID to use for the embedded DERP server. | ||
# The local DERP prevails if the region ID collides with other region ID coming from | ||
|
@@ -69,7 +89,7 @@ derp: | |
region_code: "headscale" | ||
region_name: "Headscale Embedded DERP" | ||
|
||
# Listens in UDP at the configured address for STUN connections to help on NAT traversal. | ||
# Listens over UDP at the configured address for STUN connections - to help with NAT traversal. | ||
# When the embedded DERP server is enabled stun_listen_addr MUST be defined. | ||
# | ||
# For more details on how this works, check this great article: https://tailscale.com/blog/how-tailscale-works/ | ||
|
@@ -103,18 +123,31 @@ disable_check_updates: false | |
# Time before an inactive ephemeral node is deleted? | ||
ephemeral_node_inactivity_timeout: 30m | ||
|
||
# Period to check for node updates within the tailnet. A value too low will severely affect | ||
# CPU consumption of Headscale. A value too high (over 60s) will cause problems | ||
# for the nodes, as they won't get updates or keep alive messages frequently enough. | ||
# In case of doubts, do not touch the default 10s. | ||
node_update_check_interval: 10s | ||
|
||
# SQLite config | ||
db_type: sqlite3 | ||
|
||
# For production: | ||
db_path: /headscale/data/db.sqlite | ||
|
||
# # Postgres config | ||
# If using a Unix socket to connect to Postgres, set the socket path in the 'host' field and leave 'port' blank. | ||
# db_type: postgres | ||
# db_host: localhost | ||
# db_port: 5432 | ||
# db_name: headscale | ||
# db_user: foo | ||
# db_pass: bar | ||
|
||
# If other 'sslmode' is required instead of 'require(true)' and 'disabled(false)', set the 'sslmode' you need | ||
# in the 'db_ssl' field. Refers to https://www.postgresql.org/docs/current/libpq-ssl.html Table 34.1. | ||
# db_ssl: false | ||
|
||
### TLS configuration | ||
# | ||
## Let's encrypt / ACME | ||
|
@@ -123,39 +156,36 @@ db_path: /headscale/data/db.sqlite | |
# TLS for a domain with Let's Encrypt. | ||
# | ||
# URL to ACME directory | ||
acme_url: https://acme-v02.api.letsencrypt.org/directory | ||
|
||
# Email to register with ACME provider | ||
acme_email: "" | ||
|
||
# Domain name to request a TLS certificate for: | ||
tls_letsencrypt_hostname: "" | ||
|
||
# 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 | ||
tls_client_auth_mode: relaxed | ||
|
||
# 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 | ||
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" | ||
|
||
## Use already defined certificates: | ||
# acme_url: https://acme-v02.api.letsencrypt.org/directory | ||
|
||
# # Email to register with ACME provider | ||
# acme_email: "" | ||
|
||
# # Domain name to request a TLS certificate for: | ||
# tls_letsencrypt_hostname: "" | ||
|
||
# # Path to store certificates and metadata needed by | ||
# # letsencrypt | ||
# # For production: | ||
# 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 | ||
# tls_letsencrypt_challenge_type: HTTP-01 | ||
# # When HTTP-01 challenge is chosen, letsencrypt must set up a | ||
# # verification endpoint, and it will be listening on: | ||
# # :http = port 80 | ||
# tls_letsencrypt_listen: ":http" | ||
|
||
# ## Use already defined certificates: | ||
tls_cert_path: "" | ||
tls_key_path: "" | ||
|
||
log_level: info | ||
log: | ||
# Output formatting for logs: text or json | ||
format: text | ||
level: info | ||
|
||
# Path to a file containg ACL policies. | ||
# ACLs can be defined as YAML or HUJSON. | ||
|
@@ -172,10 +202,26 @@ acl_policy_path: "" | |
# - https://tailscale.com/blog/2021-09-private-dns-with-magicdns/ | ||
# | ||
dns_config: | ||
# Whether to prefer using Headscale provided DNS or use local. | ||
# override_local_dns: true | ||
override_local_dns: false | ||
|
||
# List of DNS servers to expose to clients. | ||
nameservers: | ||
- 1.1.1.1 | ||
|
||
# NextDNS (see https://tailscale.com/kb/1218/nextdns/). | ||
# "abc123" is example NextDNS ID, replace with yours. | ||
# | ||
# With metadata sharing: | ||
# nameservers: | ||
# - https://dns.nextdns.io/abc123 | ||
# | ||
# Without metadata sharing: | ||
# nameservers: | ||
# - 2a07:a8c0::ab:c123 | ||
# - 2a07:a8c1::ab:c123 | ||
|
||
# Split DNS (see https://tailscale.com/kb/1054/dns/), | ||
# list of search domains and the DNS to query for each one. | ||
# | ||
|
@@ -189,34 +235,94 @@ dns_config: | |
# Search domains to inject. | ||
domains: [] | ||
|
||
# Extra DNS records | ||
# so far only A-records are supported (on the tailscale side) | ||
# See https://github.com/juanfont/headscale/blob/main/docs/dns-records.md#Limitations | ||
# extra_records: | ||
# - name: "grafana.myvpn.example.com" | ||
# type: "A" | ||
# value: "100.64.0.3" | ||
# | ||
# # you can also put it in one line | ||
# - { name: "prometheus.myvpn.example.com", type: "A", value: "100.64.0.3" } | ||
|
||
# Whether to use [MagicDNS](https://tailscale.com/kb/1081/magicdns/). | ||
# Only works if there is at least a nameserver defined. | ||
magic_dns: true | ||
magic_dns: false | ||
# 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_). | ||
base_domain: openmined.org | ||
# `hostname.user.base_domain` (e.g., _myhost.myuser.example.com_). | ||
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 | ||
# Note: for production you will want to set this to something like: | ||
unix_socket: /var/run/headscale/headscale.sock | ||
unix_socket_permission: "0770" | ||
# | ||
# headscale supports experimental OpenID connect support, | ||
# it is still being tested and might have some bugs, please | ||
# help us test it. | ||
# OpenID Connect | ||
# oidc: | ||
# only_start_if_oidc_is_available: true | ||
# issuer: "https://your-oidc.issuer.com/path" | ||
# client_id: "your-oidc-client-id" | ||
# client_secret: "your-oidc-client-secret" | ||
# # Alternatively, set `client_secret_path` to read the secret from the file. | ||
# # It resolves environment variables, making integration to systemd's | ||
# # `LoadCredential` straightforward: | ||
# client_secret_path: "${CREDENTIALS_DIRECTORY}/oidc_client_secret" | ||
# # client_secret and client_secret_path are mutually exclusive. | ||
# | ||
# # The amount of time from a node is authenticated with OpenID until it | ||
# # expires and needs to reauthenticate. | ||
# # Setting the value to "0" will mean no expiry. | ||
# expiry: 180d | ||
# | ||
# If `strip_email_domain` is set to `true`, the domain part of the username email address will be removed. | ||
# This will transform `[email protected]` to the namespace `first-name.last-name` | ||
# If `strip_email_domain` is set to `false` the domain part will NOT be removed resulting to the following | ||
# namespace: `first-name.last-name.example.com` | ||
# # Use the expiry from the token received from OpenID when the user logged | ||
# # in, this will typically lead to frequent need to reauthenticate and should | ||
# # only been enabled if you know what you are doing. | ||
# # Note: enabling this will cause `oidc.expiry` to be ignored. | ||
# use_expiry_from_token: false | ||
# | ||
# # Customize the scopes used in the OIDC flow, defaults to "openid", "profile" and "email" and add custom query | ||
# # parameters to the Authorize Endpoint request. Scopes default to "openid", "profile" and "email". | ||
# | ||
# scope: ["openid", "profile", "email", "custom"] | ||
# extra_params: | ||
# domain_hint: example.com | ||
# | ||
# # List allowed principal domains and/or users. If an authenticated user's domain is not in this list, the | ||
# # authentication request will be rejected. | ||
# | ||
# allowed_domains: | ||
# - example.com | ||
# # Note: Groups from keycloak have a leading '/' | ||
# allowed_groups: | ||
# - /headscale | ||
# allowed_users: | ||
# - [email protected] | ||
# | ||
# # If `strip_email_domain` is set to `true`, the domain part of the username email address will be removed. | ||
# # This will transform `[email protected]` to the user `first-name.last-name` | ||
# # If `strip_email_domain` is set to `false` the domain part will NOT be removed resulting to the following | ||
# user: `first-name.last-name.example.com` | ||
# | ||
# strip_email_domain: true | ||
|
||
# Logtail configuration | ||
# Logtail is Tailscales logging and auditing infrastructure, it allows the control panel | ||
# to instruct tailscale nodes to log their activity to a remote server. | ||
logtail: | ||
# Enable logtail for this headscales clients. | ||
# As there is currently no support for overriding the log server in headscale, this is | ||
# disabled by default. Enabling this will make your clients send logs to Tailscale Inc. | ||
enabled: false | ||
|
||
# Enabling this option makes devices prefer a random port for WireGuard traffic over the | ||
# default static port 41641. This option is intended as a workaround for some buggy | ||
# firewall devices. See https://tailscale.com/kb/1181/firewalls/ for more information. | ||
randomize_client_port: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.