Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
docs(gateways): explain why Cloud cannot use direct listen
bernie-g25e6ebd299ca
diff --git a/docs/cli/commands/gateway.mdx b/docs/cli/commands/gateway.mdxindex 59142992f8..ac5e51e29a 100644--- a/docs/cli/commands/gateway.mdx+++ b/docs/cli/commands/gateway.mdx@@ -173,7 +173,7 @@ In direct listen mode it also:Can also be set with the `INFISICAL_GATEWAY_LISTEN_ADDRESS` environment variable.<Note>- Direct listen is available on self-hosted Infisical. On Infisical Cloud, use `--relay` or omit both flags.+ Direct listen is available on self-hosted Infisical. Infisical Cloud runs outside your network and has no route into it, so there's no address it could dial. On Cloud, use `--relay` or omit both flags.</Note></Accordion>diff --git a/docs/documentation/platform/gateways/gateway-deployment.mdx b/docs/documentation/platform/gateways/gateway-deployment.mdxindex 4c70e96ac5..600406df11 100644--- a/docs/documentation/platform/gateways/gateway-deployment.mdx+++ b/docs/documentation/platform/gateways/gateway-deployment.mdx@@ -27,6 +27,8 @@ Before you deploy, decide which side opens the connection between Infisical and**Use relay mode** when the Gateway sits behind NAT or a firewall you can't open, when you're on Infisical Cloud, or when PAM CLI users connect from outside the Gateway's network.+Direct listen isn't a paid feature you can turn on for Cloud. Cloud runs outside your network and has no route into it, so there's no address it could dial. Relay mode exists precisely so the Gateway can open that connection from the inside.+You can also run both at once, which gives you direct connections for platform operations and a relay for PAM CLI users outside the network. Pass `--relay` and `--listen-address` together, and Infisical uses the direct address first and falls back to the relay when it stops answering.For the ports, certificates, and traffic flow behind each mode, see [Network architecture](/documentation/platform/gateways/network-architecture).@@ -364,7 +366,7 @@ Switching away from a mode drops it. To keep both, pass `--relay` and `--listen-<Accordion title="Why does my direct listen gateway fail to register?">The listen address has to be `host:port`, with a port in the range 1 to 65535. An address with no port is rejected, and so is one that includes a scheme or a path, so use `gateway.internal:8443` rather than `https://gateway.internal` or `gateway.internal`.-Direct listen is also unavailable on Infisical Cloud. On Cloud, use relay mode.+Direct listen is also unavailable on Infisical Cloud, which runs outside your network and has no route into it. On Cloud, use relay mode.</Accordion>diff --git a/docs/documentation/platform/gateways/network-architecture.mdx b/docs/documentation/platform/gateways/network-architecture.mdxindex d0aa25cc6b..6cc97a39cc 100644--- a/docs/documentation/platform/gateways/network-architecture.mdx+++ b/docs/documentation/platform/gateways/network-architecture.mdx@@ -14,7 +14,9 @@ There are two ways the Gateway and Infisical reach each other, and they differ iBoth modes carry the same mutually authenticated TLS between Infisical and the Gateway, with certificates issued by your organization's own certificate authorities. In relay mode the relay routes bytes without holding the keys to read them.<Info>- Direct listen is available on self-hosted Infisical. On Infisical Cloud, gateways use relay mode.+ Direct listen is available on self-hosted Infisical. It can't work on Infisical Cloud, because+ Cloud runs outside your network and has no route into it, so there's no address it could dial.+ Cloud gateways use relay mode, where the Gateway opens the connection instead.</Info>## Relay modediff --git a/docs/documentation/platform/gateways/relay-deployment/overview.mdx b/docs/documentation/platform/gateways/relay-deployment/overview.mdxindex 30873a08c1..d4bf96ccfa 100644--- a/docs/documentation/platform/gateways/relay-deployment/overview.mdx+++ b/docs/documentation/platform/gateways/relay-deployment/overview.mdx@@ -16,7 +16,7 @@ If you self-host Infisical and it can reach your gateway host at a stable addresA relay is what you need when:- The gateway sits behind NAT or a firewall you can't open for inbound connections-- You're on Infisical Cloud, where gateways use relay mode+- You're on Infisical Cloud, which runs outside your network and has no route into it, so a gateway there can't be dialed and has to open the connection itself- PAM CLI users connect from outside the gateway's network, since the CLI dials the gateway from their own machineA gateway can also run both, giving you direct connections for platform operations and a relay for CLI users outside the network.diff --git a/docs/self-hosting/helm-charts/gateway.mdx b/docs/self-hosting/helm-charts/gateway.mdxindex 2a00d6e706..8da93c2879 100644--- a/docs/self-hosting/helm-charts/gateway.mdx+++ b/docs/self-hosting/helm-charts/gateway.mdx@@ -153,7 +153,7 @@ The Service is created only in direct listen mode. In relay mode the gateway accThe address has to be one Infisical can resolve and reach. An in-cluster Service DNS name works when you self-host Infisical in the same cluster. From outside the cluster, expose the gateway through an Ingress or a `LoadBalancer` Service and register that address instead.-Direct listen is available on self-hosted Infisical. On Infisical Cloud, leave `gateway.listenAddress` empty and use a relay.+Direct listen is available on self-hosted Infisical. Infisical Cloud runs outside your cluster and has no route into it, so there's no address it could dial. On Cloud, leave `gateway.listenAddress` empty and use a relay.## Default Helm values