Describe the bug
If I choose AmnesiaWG as a protocol, then every day or two the data just suddenly stops going. No error reports or disconnects on the client. If I disconnect on the client, I can not reconnect again. The only way to fix is to restart the docker container OR choose another protocol.
On the docker side, the logs say:
root@vm2475156:~# docker logs d96
Error response from daemon: configured logging driver does not support reading
The logs error may be my fault, I am not that good at docker. But my own containers that run alongside do produce logs.
If any other protocol is used (I tried Wireguard and Shadowsocks) or another app is used (Shadowsocks, SSH tunnel), then they have no issues at the same time.
To Reproduce
Steps to reproduce the behavior:
Connect using the AmnesiaWG protocol.
Wait a day or two.
Start an important ranking match in an online game.
Connection fails.
Desktop (please complete the following information):
OS: Win11
Version 4.5.3.0.
Server (please complete the following information):
OS: Debian 12
Additional context
I will help you to collect logs on the failure if you tell me how to obtain them.
Describe the bug If I choose AmnesiaWG as a protocol, then every day or two the data just suddenly stops going. No error reports or disconnects on the client. If I disconnect on the client, I can not reconnect again. The only way to fix is to restart the docker container OR choose another protocol. On the docker side, the logs say:
The logs error may be my fault, I am not that good at docker. But my own containers that run alongside do produce logs.
If any other protocol is used (I tried Wireguard and Shadowsocks) or another app is used (Shadowsocks, SSH tunnel), then they have no issues at the same time.
To Reproduce Steps to reproduce the behavior:
Desktop (please complete the following information):
Server (please complete the following information):
Additional context I will help you to collect logs on the failure if you tell me how to obtain them.