shenxn
socat Connection reset by peer
I am seeing a lot of the following errors when using this with ios18 mail and a windows desktop application (eM client). I have to restart the container to get mail clients to work again.
2025/04/06 20:50:04 socat[107] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 20:50:04 socat[108] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 20:50:04 socat[109] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:02:58 socat[138] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:04:56 socat[139] E write(6, 0x55eb67d85000, 24): Broken pipe
2025/04/06 21:05:50 socat[152] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:05:50 socat[151] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:15:05 socat[153] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:15:05 socat[154] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:30:54 socat[157] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
2025/04/06 21:51:13 socat[160] E read(6, 0x55eb67d85000, 8192): Connection reset by peer
Unhelpfully, this looks similar to https://github.com/shenxn/protonmail-bridge-docker/issues/32
I get this when trying to use the container with Nextcloud
2025/05/03 02:40:06 socat[132] E read(6, 0x563ebfd15000, 8192): Connection reset by peer
On the Nextcloud side it says this: AxiosError: Request failed with status code 400 and if I try to send a welcome email (to get an actual log entry to share):
TransportException Unable to connect with STARTTLS: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages: error:0A000086:SSL routines::certificate verify failed
Sending mail to "Array ( [my-proton-mail-address] => Matthew Rease ) " with subject "Your [Nextcloud Branding] account was created" failed
My GitLab instance seems to mostly handle PM Bridge fine - some metadata warnings/errors, but emails get sent.
The above issue from @Magicrafter13 is also present in Authentik. Vaultwarden also has this issue, however, it has an option to accept invalid certificates, which resolves the issue.
