Alexander Bersenev

Hello, Are you able to reach https://core.telegram.org/getProxyConfig address using browser from the host which runs the proxy?

Please, try to disable your antivirus and firewall. They can block the network communication.

does it make some syscalls? strace -p

also you can send a sigusr1 to the proccess, it will show the pdb debugging console, and write "bt" in it

Hi, are you launching inside Docker or not? If not, then you should have the root rights to listen on ports that less than 1024

The port number shouldn't depend on RAM. There is a PermissionError in the traceback. If it be RAM the error world be MemoryError

You can either to change your port on, say 4430, either to run the program as administrator

This is just is warning about not recommended settings. Your mask host is refusing connections, which can make the proxy more detectable.

hi, the proxy tries to use ipv6 by default if it is available. I added one more check if ipv6 is in good condition to use it: https://github.com/alexbers/mtprotoproxy/commit/6e8e8b63b26507310bbe550d5fbd6851f598f6e1 , hope...

it is probably the network problems please retry from the master branch, it is based on debian now instead of alpine