MTProxy

Simple MT-Proto proxy

Install dependencies, you would need common set of tools for building from source, and development packages for openssl and zlib.

On Debian/Ubuntu:

apt install git curl build-essential libssl-dev zlib1g-dev

On CentOS/RHEL:

yum install openssl-devel zlib-devel
yum groupinstall "Development Tools"

Clone the repo:

git clone https://github.com/TelegramMessenger/MTProxy
cd MTProxy

To build, simply run make, the binary will be in objs/bin/mtproto-proxy:

make && cd objs/bin

If the build has failed, you should run make clean before building it again.

1. Obtain a secret, used to connect to telegram servers.

curl -s https://core.telegram.org/getProxySecret -o proxy-secret

2. Obtain current telegram configuration. It can change (occasionally), so we encourage you to update it once per day.

curl -s https://core.telegram.org/getProxyConfig -o proxy-multi.conf

3. Generate a secret to be used by users to connect to your proxy.

head -c 16 /dev/urandom | xxd -ps

4. Run mtproto-proxy:

./mtproto-proxy -u nobody -p 8888 -H 443 -S <secret> --aes-pwd proxy-secret proxy-multi.conf -M 1

... where:

• nobody is the username. mtproto-proxy calls setuid() to drop privileges.
• 443 is the port, used by clients to connect to the proxy.
• 8888 is the local port. You can use it to get statistics from mtproto-proxy. Like wget localhost:8888/stats. You can only get this stat via loopback.
• <secret> is the secret generated at step 3. Also you can set multiple secrets: -S <secret1> -S <secret2>.
• proxy-secret and proxy-multi.conf are obtained at steps 1 and 2.
• 1 is the number of workers. You can increase the number of workers, if you have a powerful server.

Also feel free to check out other options using mtproto-proxy --help.

5. Generate the link with following schema: tg://proxy?server=SERVER_NAME&port=PORT&secret=SECRET (or let the official bot generate it for you).
6. Register your proxy with @MTProxybot on Telegram.
7. Set received tag with arguments: -P <proxy tag>
8. Enjoy.

Due to some ISPs detecting MTProxy by packet sizes, random padding is added to packets if such mode is enabled.

It's only enabled for clients which request it.

Add dd prefix to secret (cafe...babe => ddcafe...babe) to enable this mode on client side.

1. Create systemd service file (it's standard path for the most Linux distros, but you should check it before):

nano /etc/systemd/system/MTProxy.service

2. Edit this basic service (especially paths and params):

[Unit]
Description=MTProxy
After=network.target

[Service]
Type=simple
WorkingDirectory=/opt/MTProxy
ExecStart=/opt/MTProxy/mtproto-proxy -u nobody -p 8888 -H 443 -S <secret> -P <proxy tag> <other params>
Restart=on-failure

[Install]
WantedBy=multi-user.target

3. Reload daemons:

systemctl daemon-reload

4. Test fresh MTProxy service:

systemctl restart MTProxy.service
# Check status, it should be active
systemctl status MTProxy.service

5. Enable it, to autostart service after reboot:

systemctl enable MTProxy.service

ghcr.io/dzalunin/mtproxy:latest

Install docker https://docs.docker.com/engine/install/

Create a docker-compose.yml file.

services:
  mtproxy:
    image: ghcr.io/dzalunin/mtproxy:latest
    container_name: mtproxy
    ports:
      - "443:443"
    environment:
      - MT_FAKETLS_DOMAIN=www.google.com
    volumes:
      - ./config:/etc/mtproxy
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8888/stats"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

Run:

docker compose up -d

After startup, run docker compose logs, copy connection links:

======== Connection Links ========
https://t.me/proxy?server=1.2.3.4&port=443&secret=ee1...
https://t.me/proxy?server=1.2.3.4&port=443&secret=ee2...

Supported formats:

• Single secret:

  32 hex characters
  

• Multiple secrets:

  secret1,secret2,secret3
  

If not provided, they are generated automatically. Secret can be generated by head -c 16 /dev/urandom | od -An -tx1 | tr -d ' \n'

Enable via:

environment:
  - MT_FAKETLS_DOMAIN=www.google.com

Requirements:

• domain must resolve correctly
• use popular domains (Cloudflare, Google, etc.)

The container uses:

/etc/mtproxy

It stores:

• proxy-secret — Telegram server key
• proxy-multi.conf — Telegram config
• secret — user secrets