search

shenxn / protonmail-bridge-docker

ProtonMail IMAP/SMTP Bridge Docker container
GNU General Public License v3.0
406 stars 82 forks source link

Getting "connection refused" for any type of connection #93

Open danionita opened 11 months ago

danionita commented 11 months ago

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.

maxime-bern commented 9 months ago

Same here 👋 image

corentincam commented 9 months ago

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 commented 9 months ago

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.

Szwendacz99 commented 9 months ago

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.

panoskpv commented 9 months ago

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.

j4care-christianhahn commented 8 months ago

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 ?