protonmail-bridge-docker icon indicating copy to clipboard operation
protonmail-bridge-docker copied to clipboard

Getting "connection refused" for any type of connection

Open danionita opened this issue 1 year ago • 6 comments

I am running Protonmail bridge docker on an UnRAID server. I have a few small websites that run on the same machine as the Bridge which use it to send e-mails. I also have a PC that uses MailBird as an e-mail client to connect to the Bridge via my LAN. No firewalls or VPN are involved. This setup has been running for over a year. Occasionally, the bridge would stop working but after restarting the Docker, it would work again. Very annoying because I would not realize it is down, but somewhat fixed by turning auto-updates on so that it restarts itself every so often. However, since Dec 10, none of my services or e-mail clients are able to connect to the Bridge to retrieve or send mail. It just throws the following error whenever anything tries to connect: " socat[21019] E connect(5, AF=2 127.0.0.1:1143, 16): Connection refused".. Nothing in the configuration or network has changed.

danionita avatar Dec 29 '23 12:12 danionita

Same here 👋 image

maxime-bern avatar Feb 02 '24 15:02 maxime-bern

Same problem since a couple days, no change in the config or anything... Tried rolling back to previous version (3.8.2-1) with no luck. I had the problem with both 1143 and 1025 ports

corentincam avatar Feb 24 '24 08:02 corentincam

I figured out my account was no longer synced, so I reinitialized the bridge (using the readme procedure) and reentered my credential and it fixed the problem. I don't know why my account disappeared.

corentincam avatar Feb 25 '24 15:02 corentincam

For me the reinitialization also worked out. The new account is syncing data to differend directory (dir have uuid-like name) so it is good to remove the old one.

Szwendacz99 avatar Feb 25 '24 17:02 Szwendacz99

I have the same issue, but it is not solved by re-initialization. I even removed the docker container and its files and started over. The issue appears back after few hours. Rebooting the container also fixes temporarily the issue.

panoskpv avatar Feb 29 '24 11:02 panoskpv

I also have a similar issue that I cannot send mails anymore - reinitalized docker container also didn't fix the issue. is there some sort of debug that we can turn on to understand the issue better ?

j4care-christianhahn avatar Mar 12 '24 07:03 j4care-christianhahn