Highly-opinionated (ex-bullshit-free) MTPROTO proxy for Telegram. If you use v1.0 or upgrade broke you proxy, please read the chapter Version 2
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
9seconds 7a99a4ec32 Correct list of supported platforms on cross compilation před 7 roky
client Fix lint errors před 7 roky
config Fix lint errors před 7 roky
mtproto Fix lint errors před 7 roky
obfuscated2 Remove frame pool for obfuscated2 frames před 7 roky
proxy Fix small lint problem před 7 roky
scripts Add Makefile před 8 roky
stats Fix lint errors před 7 roky
telegram Fix lint errors před 7 roky
utils Fix lint errors před 7 roky
wrappers Put timeouts for 2 minutes stale connections před 7 roky
.gitignore Correct list of supported platforms on cross compilation před 7 roky
.gometalinter.json Fix lint issues před 8 roky
.travis.yml Add travis yaml před 8 roky
Dockerfile Use upx for image build před 7 roky
Gopkg.lock Fix lint errors před 7 roky
Gopkg.toml Add base stats před 7 roky
LICENSE Initial commit před 8 roky
Makefile Correct list of supported platforms on cross compilation před 7 roky
README.md Jira-style links :( před 7 roky
main.go Fix lint errors před 7 roky
run-mtg.sh Update README před 7 roky

README.md

mtg

Bullshit-free MTPROTO proxy for Telegram

Build Status Docker Build Status

Rationale

There are several available proxies for Telegram MTPROTO available. Here are the most notable:

Almost all of them follow the way how official proxy was build. This includes support of multiple secrets, support of promoted channels etc.

mtg is an implementation in golang which is intended to be:

  • Lightweight It has to consume as less resources as possible but not by losing maintainability.
  • Easily deployable I strongly believe that Telegram proxies should follow the way of ShadowSocks: promoted channels is a strange way of doing business I suppose. I think the only viable way is to have a proxy with minimum configuration which should work everywhere.
  • Single secret I think that multiple secrets solves no problems and just complexify software. I also believe that in case of throwout proxies, this feature is useless luxury.
  • Minimum docker image size Official image is less than 2 megabytes. Literally.
  • No management WebUI This is an implementation of simple lightweight proxy. I won’t do that.

This proxy supports 2 modes of work: direct connection to Telegram and promoted channel mode. If you do not need promoted channels, I would recommend you to go with direct mode: this is way more robust.

To run proxy in direct mode, all you need to do is just provide a secret. If you do not provide ADTag as a second parameter, promoted channels mode won’t be activated.

To get promoted channel, please contact @MTProxybot and provide generated adtag as a second parameter.

How to build

$ make

If you want to build for another platform:

$ make crosscompile

If you want to build Docker image (called mtg):

$ make docker

Docker image

$ docker pull nineseconds/mtg

Configuration

Basically, to run this tool you need to configure as less as possible.

First, you need to generate a secret:

$ openssl rand -hex 16

or

$ head -c 512 /dev/urandom | md5sum | cut -f 1 -d ' '

Now run the tool:

$ mtg <secret>

This tool will listen on port 3128 by default with the given secret.

One-line runner

$ docker run --name mtg --restart=unless-stopped -p 3128:3128 -p 3129:3129 -d nineseconds/mtg $(openssl rand -hex 16)

You will have this tool up and running on port 3128. Now curl localhost:3129 to get tg:// links or do docker logs mtg. Also, port 3129 will show you some statistics if you are interested in.

Also, you can use run-mtg.sh script