Configure advanced Pangolin settings using the privateConfig.yml file for enterprise features
The privateConfig.yml file provides advanced configuration options for enterprise deployments. This file is mounted at config/privateConfig.yml in your Docker container.
The private configuration file is only used on enterprise deployments. If you're using Pangolin Community, refer to the main configuration file documentation instead. The private config file is not required.
Regional and base domain configuration for multi-region deployments.
Show propertiesHide properties
identity_provider_modestringdefault: global
Set the identity provider (IdP) mode for authentication. By default both global and org pages will show until set. See the Identity Providers documentation for more details on how this affects authentication and user management.
Possible values:
global: (default) Both global and organization-level IdP login pages are available. Users can authenticate using either global or organization-specific identity providers.
org: Only organization-level IdP login pages are available. Users must authenticate using identity providers defined at the organization
app: identity_provider_mode: "org"
regionstringdefault: default
The region identifier for this Pangolin instance. Used for multi-region deployments.
Path to the RSA private key used for encrypting sensitive data. Must be at least 8 characters long. THIS IS ONLY USED WITH pangolin_dns FEATURE FLAG ENABLED AND REQUIRES EXTERNAL COMPONENTS.
Configuration for Pangolin's built-in authoritative DNS nameserver. This lets Pangolin answer DNS queries directly for domains delegated to it (via CNAME or NS delegation), issue ACME DNS-01 challenge responses, and resolve site tunnel subnet addresses.
Show propertiesHide properties
enabledbooleandefault: false
Enables the authoritative DNS server. When false or omitted, no DNS listener is started.
dns: enabled: true
listen_portnumberdefault: 53
UDP port the authoritative DNS server listens on.
dns: listen_port: 53
nameserver_namestringrequired
The FQDN Pangolin advertises as itself when acting as a nameserver. Used as the mname in SOA responses and included in the NS record set returned for zones it is authoritative for. This is the hostname you point your domain's nameservers at when using NS-based domain delegation (e.g. ns1.pangolin-ns.net).
dns: nameserver_name: "ns1.pangolin-ns.net"
cname_extensionstringrequired
The domain suffix used for single-domain CNAME delegation. When an org adds a domain using the CNAME delegation type, Pangolin generates {domainId}.{cname_extension} and _acme-challenge.{domainId}.{cname_extension} targets to point your records at.
dns: cname_extension: "cname.pangolin.net"
site_extensionstring
Suffix used to resolve a site's WireGuard tunnel subnet address by DNS. A query for {newtId}.{site_extension} resolves to the tunnel subnet IP of the site running the Newt agent with that ID. This is used for site-to-cloud networking.
dns: site_extension: "site.pangolin.net"
cname_alternate_extensionsarraydefault: []
Additional CNAME suffixes (besides cname_extension) that are treated the same way. Useful when Pangolin should respond to more than one CNAME delegation domain, such as for white-label/multi-brand deployments.
Additional nameserver hostnames appended after nameserver_name in the NS record set Pangolin returns for a zone, and in the NS records shown when using NS-based domain delegation (e.g. ns2.pangolin-ns.net, ns3.pangolin-ns.net).
The time window, in milliseconds, over which query counts are measured.
max_requestsnumberdefault: 1200
Maximum total DNS queries allowed per source IP within window_ms.
max_requests_per_query_typenumberdefault: 600
Maximum queries allowed per source IP, per DNS record type (A, TXT, NS, etc.), within window_ms.
static_recordsarraydefault: []
Hardcoded DNS answers served by the authoritative DNS server, checked before database-backed lookups. Useful for fixed entries such as domain verification TXT records.
URL where the local Gerbil exit node can be reached by Pangolin. Useful when clustering multiple pangolin nodes. Overrides the value stored in the database. Useful when using Docker and address the local gerbil container using the host's address.
Configuration for Pangolin's self-hosted ACME client, which issues and renews TLS certificates directly using DNS-01 challenges served by Pangolin's own authoritative DNS server, as an alternative to relying on Traefik's built-in ACME resolver.
Show propertiesHide properties
cert_modestringdefault: traefik
Controls who is responsible for obtaining and renewing TLS certificates.
pangolin: Pangolin issues and manages certificates itself via its self-hosted ACME client, using DNS-01 challenges. Requires dns.enabled and acme.enable_acme_client to both be true. ENSURE ONLY ONE NODE IN A CLUSTER HAS THE acme.enable_acme_client FLAG ENABLED, OTHERWISE MULTIPLE NODES WILL TRY TO ISSUE CERTIFICATES SIMULTANEOUSLY.
acme: cert_mode: "pangolin"
enable_acme_clientbooleandefault: false
Enable the self-hosted ACME client and its certificate issuance/renewal jobs. Must be true, along with cert_mode: "pangolin", for the certificate manager to start.
acme: enable_acme_client: true
contact_emailstringrequired
Email address registered with the ACME account, used by the CA for expiry and policy notices.
How long, in milliseconds, a DNS-01 challenge TXT record is considered valid and served by the authoritative DNS server before expiring.
acme: challenge_ttl_ms: 300000
renewal_check_interval_msnumberdefault: 3600000
How often, in milliseconds, Pangolin checks for certificates approaching expiry and renews them.
acme: renewal_check_interval_ms: 3600000
new_cert_check_interval_msnumberdefault: 5000
How often, in milliseconds, Pangolin checks for newly-needed certificates and issues them. Set much lower than renewal_check_interval_ms since new certificates are user-facing and blocking.
acme: new_cert_check_interval_ms: 5000
acme_requests_per_secondnumberdefault: 15
Shared rate limit on outbound calls Pangolin's client makes directly to the ACME server (create order, get authorizations, verify challenge, finalize, get certificate). Kept under Let's Encrypt's ~20 req/s limit.
acme: acme_requests_per_second: 15
dns_check_interval_msnumberdefault: 60000
How often, in milliseconds, Pangolin checks pending (not-yet-verified) domains' DNS records against live DNS to flip them to verified once the records are in place.
How often, in milliseconds, Pangolin runs a periodic pass re-checking already-verified domains, to catch removing or changing their DNS records after the fact.
Minimum age, in milliseconds, a verified domain's last check must have before it becomes eligible for reverification. A given domain is reverified at most roughly this often, not on every reverification pass.
acme: domain_reverification_window_ms: 259200000
domain_reverification_batch_sizenumberdefault: 20
Maximum number of verified domains reverified per reverification pass, to bound database and DNS load per tick.
Upstream public DNS resolvers used to perform live lookups against real DNS (not Pangolin's own authoritative server) when validating or reverifying domain records. Resolvers are rotated across on each attempt so a single resolver's cache or propagation lag doesn't wrongly fail a check.
Some configuration values can be set using environment variables for enhanced security:
Name
Variable
Config
Supports _FILE
Redis Password
REDIS_PASSWORD
redis.password
YES
Any variable marked "Supports _FILE" can also be set as <VARIABLE>_FILE, pointing to a file on disk whose (trimmed) contents are used as the value instead — see Reading secrets from a file in the main configuration file docs for details and a Docker Compose example.