Skip to content

Update config docs #300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nscuro merged 1 commit into from
Oct 8, 2026
Merged

Update config docs #300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/reference/configuration/properties.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1422,7 +1422,7 @@ Specifies if the username entered during login needs to be formatted prior to a

<span id="dtoutboundallowed-destinations">**`dt.outbound.allowed-destinations`** [¶](#dtoutboundallowed-destinations){ .headerlink }</span>

Defines which destinations outbound connections may reach. <br/><br/> Every address a host resolves to must be allowed. Connections to the database, S3 file storage, LDAP, and OIDC identity providers are always allowed. <br/><br/> Supported entries: <ul> <li><code>external</code>: publicly routable addresses</li> <li><code>private</code>: <code>10.0.0.0/8</code>, <code>172.16.0.0/12</code>, <code>192.168.0.0/16</code>, <code>100.64.0.0/10</code>, <code>fc00::/7</code></li> <li><code>loopback</code>: <code>127.0.0.0/8</code>, <code>::1</code></li> <li>IP addresses and CIDR ranges, e.g. <code>10.1.0.0/16</code></li> <li>hostnames, e.g. <code>internal.example.com</code></li> <li><code>*</code>: all destinations; must be the only entry</li> </ul> Link-local, unspecified, and cloud metadata addresses (e.g. `169.254.169.254`) are always denied, unless an IP address or CIDR range entry at least as specific allows them. Hostname entries never do. <br/><br/> Requests through the configured HTTP proxy are only checked when the destination is an IP address.
Defines which destinations outbound connections may reach. <br/><br/> Every address a host resolves to must be allowed. Connections to the database, S3 file storage, LDAP, and OIDC identity providers are always allowed. <br/><br/> Supported entries: <ul> <li><code>external</code>: publicly routable addresses</li> <li><code>private</code>: <code>10.0.0.0/8</code>, <code>172.16.0.0/12</code>, <code>192.168.0.0/16</code>, <code>100.64.0.0/10</code>, <code>fc00::/7</code></li> <li><code>loopback</code>: <code>127.0.0.0/8</code>, <code>::1</code></li> <li>IP addresses and CIDR ranges, e.g. <code>10.1.0.0/16</code></li> <li>hostnames, matched exactly, e.g. <code>internal.example.com</code></li> <li><code>*</code>: all destinations; must be the only entry</li> </ul> Allow only the destinations your integrations need. Prefer hostnames and narrow CIDR ranges over <code>private</code> and <code>loopback</code>. Link-local, unspecified, and cloud metadata addresses (e.g. `169.254.169.254`) are always denied, unless an IP address or CIDR range entry at least as specific allows them. Hostname entries never do. <br/><br/> Requests through the configured HTTP proxy are only checked when the destination is an IP address.

<table>
<tr><th>Type</th><td style="border-width: 0"><code>string</code></td></tr>
Expand Down
Loading