tonnamespace/rldp-http-proxy repository overview

⁠TON RLDP-HTTP-Proxy (Docker)

Dockerized TON RLDP-HTTP-Proxy⁠ — an HTTP proxy that resolves .ton domains over the TON network using the RLDP protocol. This image lets you browse TON Sites (e.g. http://tonnel.ton) from any regular browser or HTTP client by routing requests through a local proxy.

Docker Hub: tonnamespace/rldp-http-proxy⁠

⁠How It Works

The container runs the official rldp-http-proxy binary from ton-blockchain/ton⁠. It connects to the TON network via liteservers (configured through global.config.json), resolves .ton domain names via TON DNS, and fetches site content over the RLDP protocol. Locally it exposes an HTTP proxy on port 8080 that you can point your browser or curl at.

⁠Quick Start (Step by Step)

⁠Step 1: Clone the Repository

git clone https://github.com/TON-Namespace/docker-ton-rldp-http-proxy.git
cd docker-ton-rldp-http-proxy

⁠Step 2: Download global.config.json

Download the TON network global config into the project directory:

curl -o global.config.json https://ton-blockchain.github.io/global.config.json

⁠Step 3: Run prepare.sh

The prepare.sh script automates the initial setup of your proxy node. It does the following:

1. Generates an ADNL keypair — Every node on the TON network needs a unique ADNL (Abstract Datagram Network Layer) identity. The script creates a keyring/ directory and runs the generate-random-id tool inside a temporary Docker container to produce a new ADNL private key and its corresponding base64 address.
2. Prompts you to paste the ADNL address — After key generation, the script asks you to copy the base64 ADNL address from the output and paste it back. This address is used to identify your proxy node on the network.
3. Auto-detects your public IP — The script calls ipinfo.io/ip to determine your server's public IP address.
4. Creates main.env — All collected values (SERVER_PUBLIC_IP, SERVER_ADNL_ADDRESS, PORT, ADNL_PORT, etc.) are written into a main.env file that docker-compose.yml reads at startup.

Run it:

chmod +x prepare.sh
./prepare.sh

After the script finishes, review main.env to make sure SERVER_PUBLIC_IP is correct (especially if you are behind NAT or a cloud provider).

⁠Step 4: Start the Proxy

docker compose up -d

This pulls the image (if not built locally), creates the container, mounts global.config.json and the keyring/ directory, loads main.env, and starts the RLDP-HTTP-Proxy.

⁠Step 5: Check Logs

To follow the container logs in real time, use either:

# If you are in the project directory:
docker compose logs -f

# Or by container name from anywhere:
docker logs -f ton-proxy-gateway

You should see output like the proxy connecting to liteservers and starting to listen on port 8080.

⁠Step 6: Verify It Works

Test the proxy with curl by requesting a .ton website through it. For example, to open tonnel.ton:

curl -x localhost:8080 http://tonnel.ton

If you get back HTML content, the proxy is working correctly.

⁠Step 7 (Optional): Browse .ton Sites in Your Browser (Windows)

Instead of using curl, you can configure Windows to route all HTTP traffic through the proxy so you can open .ton websites directly in Chrome, Edge, or any other browser.

1. Open the Start menu and search for "Proxy settings":

   

2. In the Proxy settings page, scroll down to Manual proxy setup and configure it:

   • Toggle "Use a proxy server" to On
   • Address: Enter your server's IP address (use 127.0.0.1 if the proxy runs on the same machine, or the server's public IP if it runs remotely)
   • Port: 8080
   • Check "Don't use the proxy server for local (intranet) addresses"
   • Click Save

   

3. Open your browser and navigate to any .ton website, for example http://tonnel.ton. You should see the site load normally:

   

⁠Ports

Make sure port 3333/udp is open on your firewall/security group so the proxy can communicate with the TON network.

⁠Environment Variables

These are set automatically by prepare.sh in main.env, but you can edit them manually:

⁠File Structure

docker-ton-rldp-http-proxy/
├── Dockerfile            # Multi-stage build: downloads TON binaries and creates runtime image
├── docker-compose.yml    # Compose config with volume mounts and env file
├── entrypoint.sh         # Container entrypoint: handles key generation mode and proxy startup
├── prepare.sh            # Host-side setup script: generates ADNL keys and creates main.env
├── global.config.json    # TON network config (you provide this)
├── keyring/              # Generated ADNL private keys (created by prepare.sh)
└── main.env              # Environment variables (created by prepare.sh)

⁠Related: Host a Website on the TON Network

If you want to run your own website behind the TON network (make your site accessible as a .ton domain), check out the companion project:

• Docker Hub: tonnamespace/reverse-proxy⁠
• GitHub: TON-Namespace/docker-ton-reverse-proxy⁠

That image runs rldp-http-proxy in reverse proxy mode, allowing you to serve a regular HTTP backend (e.g. Nginx, Node.js) over the TON network so users can access it via a .ton domain.

⁠Building the Image Locally

If you prefer to build from source instead of pulling from Docker Hub:

docker build -t ton-proxy-client .

Then update docker-compose.yml to use image: ton-proxy-client (which is already the default).

⁠License

This project packages the official TON binaries from ton-blockchain/ton⁠. Refer to the TON repository for licensing details.