WEB Proxy connects but stops working after a few seconds

Tested the official tproxy-server deployment on Ubuntu 24.04.
The proxy connects successfully and works for a few seconds, then chats stop loading, while Telegram still shows the proxy as Connected.
Server remains healthy during the issue: /readyz returns 200, sessions remain active, and backend_dial_failures_total stays at 0.
Interestingly, with a VPN enabled on the client, WEB Proxy works normally and remains stable.
Also encountered the MTProxy permissions / 203/EXEC issue during installation.

WEB Proxy currently feels unnecessarily complicated and accessible mostly to technical users.
It could work more like Amnezia: the user rents a VPS, enters the server IP, SSH login/password (or key) directly in Telegram, and Telegram automatically installs and configures everything.
After deployment, the proxy could also be managed directly from Telegram — add/revoke users, generate individual access keys, check server status, update the proxy, etc.
This would turn WEB Proxy from a feature for a relatively small group of advanced users into something ordinary Telegram users could actually deploy themselves.
The complicated part could remain under the hood. For the user it could simply be: VPS credentials → Install → WEB Proxy ready.

The payload names the official tproxy-server deployment, /readyz, active sessions, backend_dial_failures_total, and Ubuntu 24.04; start by reproducing the WEB Proxy failure without a VPN and compare it with the stable VPN case. Done should be a confirmed cause and a narrowly defined fix for the disconnect, with the MTProxy 203/EXEC issue and Telegram-managed deployment proposal treated as separate scope.