Use mtproto-proxy -nat-info command line switch to configure the proxy server.Resilio sync telegram. The container tries to detect the external IP address automatically, but this may fail if you have extracted the binary out of the container. The MTProto Proxy must know about its globally routable external IP address if it's behind NAT.You should be running a time synchronization daemon to keep these issues to a minimum. Your proxy server's system time should be within five seconds of UTC.Firewalls and/or DPI checkpoints between your proxy server and the core Telegram servers may not allow traffic to pass.If clients hang in an "updating" state, be sure to check the following: "Connecting" problems are usually caused by a misconfigured firewall, a Docker port forwarding problem, a state censorship issue, or a combination of the above. There are two major problem categories: the client might not be able to connect to your proxy server (client applications will hang in "connecting" state), or your proxy server is unable to connect to the core Telegram servers (application hangs in "updating" state). MTProto Proxy may fail to operate properly in certain conditions. Is equal to 60000 multiplied by worker count. total_max_special_connections: the upper limit on inbound connections.total_special_connections: number of inbound client connections.active_targets: number of Telegram core servers the proxy is actually connected to.ready_targets: number of Telegram core servers the proxy will try to connect to.Please note that this endpoint is available only from localhost: depending on your configuration, you may need to collect the statistics with docker exec mtproto-proxy curl The MTProto proxy server exports internal statistics as tab-separated values over the endpoint. ARGS: Additional custom args to be passed to mtproto-proxy binary.If not provided, will be automatically detected, INTERNAL_IP: Server internal IP for NAT.If not provided, will be automatically detected PROXY_CONFIG_FILE: Telegram core IP addresses obtained from telegram during init.PROXY_SECRET_FILE: Optained from telegram servers for communication during init.SECRET_FILE: Where to store generated secret.Defaults to /data/secret.DEBUG: Set to true to enable init script debugging.e WORKERS=16 mtproxy/mtproxy Other Environment Variables □Example: Setting number of workers to 16: docker run. If you have many clients, be sure to adjust the WORKERS variable. For best performance we artificially limit the proxy to 60000 connections per core and run one workers by default. WORKERSĪ single worker process is expected to handle tens of thousands of clients on a modern CPU. You'll have to provide it as an environment variable every time you run an MTProto proxy container. Please note that the tag is not persistent. e SECRET_COUNT=4 mtproxy/mtproxy TAGĪ custom advertisement tag may be provided using the TAG environment variable: e SECRET=secret1,secret2 mtproxy/mtproxy □Example: Manualy specify different secrets: docker run. You may specify them explicitly as comma-separated hex strings in the SECRET environment variable, or you may let the container generate the secrets automatically using the SECRET_COUNT variable to limit the number of generated secrets. The proxy may be configured to accept up to 16 different secrets. e SECRET=00baadf00d15abad1deaa51sbaadcafe mtproxy/mtproxy If you need to specify a custom secret (say, if you are deploying multiple proxies with DNS load-balancing), you may pass the SECRET environment variable as 16 bytes in lower-case hexidecimals: docker run. Several options are configurable using environment variables. Once your MTProxy server is up and running go to and register your proxy with Telegram to gain access to usage statistics and monetization. We try to keep the changes to a minimum, but you should restart the container about once a day, just in case. Please note that the proxy gets the Telegram core IP addresses at the start of the container. You may forward any other port to the container's 443 by changing left side port.īe sure to fix the automatic configuration links if you do so. If not provided, it will be generated automatically at container start. It is a mandatory configuration parameter. The secret will persist across container upgrades in a volume. ![]() Then obtain links for Telegram app by reading container's logs with docker logs -f mtproxy. Docker run -d -p443:443 -name=mtproxy -restart=always -v mtproxy:/data mtproxy/mtproxy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |