• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Change outgoing mail address IP then broken server

RomanLed

Basic Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian v18.0.58
Hello,
Change the IP address for outgoing emails in Plesk panel server then broke the mail and all websites on the dedicated server.
Maybe someone will answer why everything stops working all service?
 
Hi

Can you provide any log ?

Cant say nothing without information, maybe some missconfigured IP
Maybe you delete old one ?

Too much posible options.
 
This applies to incoming and outgoing mail:
postfix/smtp [5939] 36ED79812C2: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10026, delay=764, delays=764/0.02/0/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting)
amavis [5131] (!)DENIED ACCESS from IP 138.201.68.194, policy bank 'SUBMISSION'
postfix/smtp [5937] 5F016981175: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=33816, delays=33816/0.01/0/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting)
This is the additional IP 138.201.68.194

Web pages stopped working - the default PLESK page only show,
SSL stopped working
Most domain logs stopped being saved when the IP switched.
Only this remains, In the PLESK logs :
panel [23511:65c21e840a4c9] Could not find domain connect URL prefix for lensgdansk.pl.
panel [23511:65c21e840a4c9] Could not find domain connect URL prefix for unifarma.pl.
panel [17432:65c24f2682ba4] Not found.
panel [25774:65c24f4c3d30d] Not found.
and etc.
 
Where did you change the IP address? There is no such option in Mail Server Settings. When you changed the IP address of the server itself, you need to at least re-read the IP addresses in Tools & Settings > IP Addresses, and likely a full reconfiguration of the web server configuration files is also required.
 
O.k., got you. Did you use the drop down or the command line?
Did the server become inaccessible only for your own Internet Access Point or for everyone on the Internet?
Did you check if the Postfix, Dovecot, Apache and Nginx services are up or if they have logged error messages and crashed?
 
Use the drop down in panel.
The websites became inaccessible to everyone from the Internet - default PLESK appeared
As you can see in the logs, the mail was not working - everything was left in queues

There are no errors apart from those listed here.
 
It's an interesting issue, because a modification of the mail service configuration does in no way change other services. There must be an additional issue on the system. Are the other services up? What error messages are logged for example in Apache, Nginx?
 
Could you please also check that 127.0.0.1 is excluded from Fail2Ban IP bans? And that your public IP addresses are excluded from bans, too?
 
IP Fail2Ban - not used
Juggernaut Security and Firewall - used, 127.0.0.1 its ok

Restoring the outgoing mail server to its original setting restored proper operation of everything.
But there were also problems - after restoring, a message appeared about incorrect DNS settings in all domains.
I saved the template (which was not changed) three times and it helped with the error messages.
The mail server worked immediately, rest started working after a few hours.

I gave up changing the IP of the mail server, I changed the IP of the entire server and not without problems - all cron jobs fell apart :(
 
Back
Top