Configure an external proxy

Set up a proxy for outgoing connections, supporting both HTTP and HTTPS

CARTO Self-hosted supports operating behind an HTTP or HTTPS proxy. The proxy acts as a gateway, enabling CARTO Self-hosted components to establish connections with essential external services like CARTO licensing system, or You can find detailed information about these components and services in the network requirements section.

CARTO Self-hosted does not provide or install any proxy component; It's built to connect to an existing proxy software deployed on your side.

A comprehensive list of domains that must be whitelisted by the proxy for the proper operation of CARTO Self-hosted can be found here. Such list includes domains for the core services of CARTO Self-hosted, as well as some optional domains that should be enabled to access specific features.


In order to configure an external HTTP proxy on your CARTO Self-hosted installation, you'll have to:

Please be aware that proxy support is not available for our Single VM Deployment at this time.


To configure an HTTPS proxy on CARTO Self-hosted, you'll have to change the following configuration:

Please be aware that proxy support is not available for our Single VM Deployment at this time.

Support for data warehouses

While certain data warehouses can be configured to work with a proxy, there are some providers that will inherently bypass it. This means that the connection to these data warehouses won't be created through the proxy, so CARTO Self-hosted services will try to directly perform requests to the providers.

  • BigQuery: It supports both HTTP and HTTPs proxy.

  • PostgreSQL and Redshift: They use a TCP connection instead of HTTP(S), so the proxy is bypassed.

  • Databricks: Proxy is not supported, so the HTTPS connection will be bypassed.

  • Snowflake: It supports HTTP proxy, but HTTPS is not supported and will have to be bypassed. In order to bypass it, you'll have to add to the list of excluded domains.

When the proxy is bypassed, and you have a restrictive network policy in place, you will need to explicitly allow this egress of non-proxied traffic.


Password authentication is not supported for the proxy connection.

Importing data using an HTTPS Proxy configured with a certificate signed by a Custom CA is not supported.

Last updated