Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.
© 2026 The ThingsBoard Authors
180 Try for free Menu

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

North America Data stored in North America Europe Data stored in the European Union

Rather run it yourself? Install on your own servers

Connect Edge behind a proxy — Docker

Running ThingsBoard Edge behind a proxy server means that its gRPC connection to the ThingsBoard server (port 7070 by default, set by CLOUD_RPC_PORT) is routed through the proxy instead of going directly to the internet. Edge opens this connection through the proxy with an HTTP CONNECT tunnel. Only this connection uses the proxy: devices, the Edge UI, and the local database are not affected, so there is no bypass list to configure.

This setup is common in restricted network environments where direct internet access is deliberately blocked. Proxies also add a security layer by filtering and monitoring outbound traffic, and can cache resources to reduce bandwidth usage.

Prerequisites

Section titled “Prerequisites”
  • An HTTP proxy server that allows CONNECT to the ThingsBoard server’s gRPC port, with its host, port, and credentials if required.
  • ThingsBoard Edge must be installed and running via Docker Compose.
  • Docker and Docker Compose must be installed.

Step 1. Stop the container

Section titled “Step 1. Stop the container”
Terminal window
docker compose stop

Step 2. Update docker-compose.yml

Section titled “Step 2. Update docker-compose.yml”

Open the file:

Terminal window
sudo nano docker-compose.yml

Add the following lines to the environment block of the mytbedge service:

      CLOUD_RPC_PROXY_ENABLED: "true"
      CLOUD_RPC_PROXY_HOST: "proxy_host"
      CLOUD_RPC_PROXY_PORT: "proxy_port"
      CLOUD_RPC_PROXY_USERNAME: "proxy_user"
      CLOUD_RPC_PROXY_PASSWORD: "proxy_password"

Replace proxy_host and proxy_port with your proxy’s hostname and port. If your proxy does not require authentication, omit the CLOUD_RPC_PROXY_USERNAME and CLOUD_RPC_PROXY_PASSWORD lines.

Step 3. Restart the containers

Section titled “Step 3. Restart the containers”
Terminal window
docker compose up -d && docker compose logs -f mytbedge

mytbedge is the default Edge service name in docker-compose.yml. If you renamed the service, replace it in the command.

Once started, open the Edge UI at http://localhost:8080 and log in with your tenant credentials. Go to Edge → Status and confirm the Status field shows Connected — this confirms Edge is reaching the server through the proxy.

Troubleshooting

Section titled “Troubleshooting”

Check that the proxy variables reached the Edge container:

Terminal window
docker compose exec mytbedge printenv | grep CLOUD_RPC_PROXY

Test connectivity to ThingsBoard Cloud through the proxy:

Terminal window
curl -x http://proxy_host:proxy_port https://your_tb_cloud_url

Check container logs for proxy-related errors:

Terminal window
docker compose logs mytbedge | grep -iE "proxy|UNAVAILABLE"