V2ray MTProto through Shadowsocks
Why use it
MTProto is easy to block;
shadowsocks is hard to identify but cannot work without a client.
You can deylop this docker image to run a relay inside the firewall (China/Russia etc.), it provide a MTProto and all the packets will be sent through shadowsocks protocol.
How to run
v2ray.conf, change the
secret, and the other 4 settings in
servers for shadowsocks configure.
Then put these 2 files in a folder and run
docker-compose up -d.
It is based on V2ray. Also, I wrote some similar programs: inner-shadowsocks, shadowsocks-with-socks-auth to provide a Socks5 through shadowsocks. But for telegram, they are not recommended, because the Socks5 credential is transported in plain.
UPDATE: I add a pre-connection pool to the original v2ray in a ugly way, but it works. It can reduce a lot of "Connecting" time.
Known problem: The v2ray does not have a connection pool or some mechanisms like pre-connect, which will cause the "Connecting" status lasts for very long time.