Closed hakramzade closed 6 months ago
i think it only support http proxy not socks5
i think it only support http proxy not socks5
It do supports http but they updated the library and now It also supports socks5 Check this out: https://github.com/eternnoir/pyTelegramBotAPI?tab=readme-ov-file#proxy
P.S.: I used a tool called pproxy to convert my local socks proxy to local http proxy. I don't know if it is useful to anyone but the problem is solved for now as I'm using http instead socks
pip3 install pproxy
pproxy -l http://0.0.0.0:<unused_port> -r socks5://<userproxy:password@proxy_address:port>
now you can use http proxy as TELEGRAM_PROXY
It do supports http but they updated the library and now It also supports socks5 Check this out: https://github.com/eternnoir/pyTelegramBotAPI?tab=readme-ov-file#proxy
marzban is using 4.9.0 version and latest version is 4.15.2 if you are interest you can sync marzban with last version and make a pull request
It do supports http but they updated the library and now It also supports socks5 Check this out: https://github.com/eternnoir/pyTelegramBotAPI?tab=readme-ov-file#proxy
marzban is using 4.9.0 version and latest version is 4.15.2 if you are interest you can sync marzban with last version and make a pull request
I'm a newbie in github, cannot do that. it would be great if you guys make it for next marzban update. Thanks for you great work and effort! ⭐️
In the .env file there is a variable called "TELEGRAM_PROXY" which is being used as proxy server to connect to TelegramAPI servers using python telebot library using socks5 as proxy in python telebot is possible and supported IF "pysocks" and "requests[socks]" is available in python libraries.
To Reproduce the issue:
simply use any socks5 proxy address as TELEGRAM_PROXY in .env file. (I always alternatively check the proxy response with this command, you can do it too:
curl -x <socks5Proxy> ip.sb
socks5Proxy format: socks5://userproxy:password@proxy_address:port this must return the proxy public ipv4)restart the marzban and you constantly get this error which can be solved if you install "pysocks" and "requests[socks]" on the docker container. LOG:
Additional context: If you have trouble finding a socks5 proxy, you can use ssh connection to one of your servers as a socks proxy server. Here is how you can do:
screen -S proxy
ssh -N -D <custom_port> user@server
curl -x localhost:<custom_port> ip.sb