New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegram专用代理MTProxy脚本 #12

Open
shellhub opened this Issue Jul 18, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@shellhub
Owner

shellhub commented Jul 18, 2018

写一个专门用于搭建Telegram代理MTProxy的脚本

https://github.com/shellhub/shellhub/blob/master/proxy/mt_proxy.sh

支持版本

  • Centos
  • Debian/Ubuntu

如何使用

复制到服务器中自动编译安装

wget -N --no-check-certificate https://raw.githubusercontent.com/shellhub/shellhub/master/proxy/mt_proxy.sh && chmod +x mt_proxy.sh && ./mt_proxy.sh

输入用于客服端连接的端口号,可以直接自动生成

Input server port (defalut: Auto Generated):

输入一个32位16进制的密码用于客服端用来验证服务器,回车自动生成

Input secret (defalut: Auto Generated):

完成安装

***************************************************
* Server : 140.82.22.61
* Port   : 1094
* Secret : 3c6c1efb0244e0285a4c3a28ebc6ce9c
***************************************************

Here is a link to your proxy server:
https://t.me/proxy?server=140.82.22.61&port=1094&secret=3c6c1efb0244e0285a4c3a28ebc6ce9c

And here is a direct link for those who have the Telegram app installed:
tg://proxy?server=140.82.22.61&port=1094&secret=3c6c1efb0244e0285a4c3a28ebc6ce9c
***************************************************

客服端链接到代理服务器

  • 可以手动输入ip地址,端口号,密钥进行链接
  • 可以复制https开头的链接到浏览器打开,浏览器自动打开Telegram配置
  • 可以在app里面直接打开tg:开头的链接

视频教程

IMAGE ALT TEXT HERE

@shellhub shellhub changed the title from Telegram专用代理脚本 to Telegram专用代理MTProxy脚本 Jul 18, 2018

@yangbows

This comment has been minimized.

yangbows commented Nov 4, 2018

怎么卸载?

@shellhub

This comment has been minimized.

Owner

shellhub commented Nov 5, 2018

怎么卸载?

这个没有安装到硬盘(从源码可知),只是暂时性运行在内存上,如果想停止可以重启服务器,如果不想重启就杀死对应的进程,
方式如下

ps -aux | grep mtproto-proxy

找到对应的pid
然后执行kill pid执行杀死对应进程

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment