-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting "connection refused" for any type of connection #93
Comments
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 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. |
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. |
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. |
I also have a similar issue that I cannot send mails anymore - reinitalized docker container also didn't fix the issue. |
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.
The text was updated successfully, but these errors were encountered: