Docker Mailserver
Replies: 1 comment 3 replies
-
If you can't connect at all, check if your IP is blocked by fail2ban. |
Beta Was this translation helpful? Give feedback.
-
|
I've confirmed that its not fail2ban. My ip isn't listed when checking its status. DMS just isn't reachable from anywhere externally for whatever reason. |
Beta Was this translation helpful? Give feedback.
-
|
If the only change that you did was on the host, it's most likely not a DMS issue. Things you could try to identify the cause:
Make sure to restart DMS correctly (destroying the container), after you did a change: Generally, I strongly advice against using watchtower and instead, do updates manually, after reading the changelog. fyi: DMS v15 just got just released. Maybe that fixes the issue for you. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW Watchtower is also unmaintained. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I've been running DMS for about 7 months with no issues, and yesterday, I logged in to do a regular system update of my remote server running my email and I have no clue how, but I somehow broke external connectivity to my web server, and I cannot connect from my email clients anymore. I've been trying to diagnose this error but I'm not sure what is causing the issue.
sudo docker compose down,sudo apt-get update,sudo apt-get upgrade,sudo reboot, and then ssh back in and runsudo docker compose up -d. This has worked fine for the past couple of months.sudo apt-get purge fail2banafter runningsudo systemctl disable fail2banandsudo systemctl stop fail2ban. After rebooting the remote machine and running compose up one more time, I haven't been able to fix the issue.Again, this configuration had been working fine for months until yesterday, and I have no clue what could've caused this shutdown. I will attach some relevant logs/config files for anyone to see. I would really appreciate some help in diagnosing this issue. Please let me know if further information is needed.
(Fail2Ban is enabled)
compose.yaml:DMS Log File at last working connection (Potentially sensitive info is removed)
There appears to be someone trying to scrape an email address and login, but lets ignore that for now. Here are the next lines in the log file shortly after.
There appears to be a restart and there were 0 connections/logs after these lines (until I logged into the server and attempted to diagnose the issue). I have no clue as to why this would randomly happen in the middle of the night.
To confirm that the issue is one with the network, I ran telnet internally and I got a valid response, but attempting to connect in an external manner doesn't work.
Just to reiterate, my configuration has worked flawlessly for months, and all DNS records and firewalls have had the correct ports open. I don't understand why installing and uninstalling fail2ban, or updating some ubuntu packages, would cause my service to go go down.
(Here is my OCI VCN configuration, in case it is needed):
I appreciate any time anyone puts in to help me resolve this issue. If I am somehow making a dumb error and I didn't properly read the docs, I apologize. I've reread the setup guide as well as the fail2ban guide.
Thank You :)
Beta Was this translation helpful? Give feedback.
All reactions