Some users pointed out they where having problems with the proxy as soon as I upgraded it.
I was running a very old version (no idea which version, but it was from at least 2 years ago).
After upgrading, now I am running:
mtproxy-0.01 compiled at Sep 8 2020 08:41:59 by gcc 9.3.0 64-bit after commit dc0c7f3de40530053189c572936ae4fd1567269b
I am running the proxy with a systemd service, so I didn't notice at first it was crashing, because it was started again as soon as it crashed. I decided to run it in a tmux session to check what happened, and about 40 minutes later I found this:
Some users pointed out they where having problems with the proxy as soon as I upgraded it. I was running a very old version (no idea which version, but it was from at least 2 years ago). After upgrading, now I am running:
mtproxy-0.01 compiled at Sep 8 2020 08:41:59 by gcc 9.3.0 64-bit after commit dc0c7f3de40530053189c572936ae4fd1567269b
I am running the proxy with a systemd service, so I didn't notice at first it was crashing, because it was started again as soon as it crashed. I decided to run it in a tmux session to check what happened, and about 40 minutes later I found this:
./mtproto-proxy -u nobody -p 8085 -H 2233 -P ... -S ... --aes-pwd proxy-secret proxy-multi.conf -M 1 --http-stats
It references https://github.com/TelegramMessenger/MTProxy/blob/ce9933813dd1473e8158b45abf38fa45cbd3b84c/net/net-msg.c#L1303 , but I have no idea how to solve this.
Some (perhaps) usefull information:
Usage statistics (@MTProxybot):