• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

EMERGENCY! Migration Failing due to HTTPD not listening to specific IP's

Tsi-Shawn

Basic Pleskian
I built the system on Centos 6.5 with plesk 12 with a range of ips. I then (after the fact) copied the IPs of the old server to the new and moved all the domains to their IP's. This way today we flipped the routes and all should work.

The problem is that the domains only work when putting :7080 behind them. It seems like the httpd is only listening on the old IP and not the new ones. Anyone know how to make plesk/httpd listen with the new IP's on port 80"

httpd.conf

#Listen 12.34.56.78:80
Listen 7080

I added all the other IP's and tried changing ports under Listen but that does not work either. So changing the listening port does not work.
 
Ports 7080/7081 are used, if nginx is installed as well, because nginx listens on Port 80 and 443. You might check that with:

netstat -ntpl | grep httpd
( on some other systems ) netstat -ntpl | grep apache2
netstat -ntpl | grep nginx

After configuring the domains over Plesk, assigning the correct IPs to them, you might want to reconfigure the domains with the following command, to make sure, that all httpd.conf's and vhost.conf's are built.
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
or
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain YOURDOMAIN.COM

You should restart httpd and nginx afterwards:
/etc/init.d/httpd restart
( on some other systems ) /etc/init.d/apache2 restart
/etc/init.d/nginx restart


If you still experience problems/issues, it might help to investigate some logs ( Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 ) )
 
Thanks! I will go through this and check back.

I have done all this. What should i see seeing with netstat -ntpl | grep nginx before I make the DNS switch back to the new server?
 
Last edited:
The netstat command above will show something like this:

For httpd / apache2:
Code:
tcp        0      0 0.0.0.0:7080            0.0.0.0:*               LISTEN      4029/httpd [I]( or apache2 )[/I]
tcp        0      0 0.0.0.0:7081            0.0.0.0:*               LISTEN      4029/httpd [I]( or apache2 )[/I]

For nginx:
Code:
tcp        0      0 XXX.XXX.XXX.XX1:80        0.0.0.0:*               LISTEN      13887/nginx
tcp        0      0 XXX.XXX.XXX.XX2:80        0.0.0.0:*               LISTEN      13887/nginx
tcp        0      0 XXX.XXX.XXX.XX3:80        0.0.0.0:*               LISTEN      13887/nginx
tcp        0      0 XXX.XXX.XXX.XX1:443       0.0.0.0:*               LISTEN      13887/nginx
tcp        0      0 XXX.XXX.XXX.XX2:443       0.0.0.0:*               LISTEN      13887/nginx
tcp        0      0 XXX.XXX.XXX.XX3:443       0.0.0.0:*               LISTEN      13887/nginx
... where each XXX.XXX.XXX.XX1 ( 2 / 3 ) will show, on which IPs nginx is listening to. It should show all available IPs on your server.
 
Fixed. I did the above after I ran /usr/local/psa/bin/repair -r

I am not sure which one fixed ti as the repair does a re-config after too. Can someone please edit this to be SOLVED?

UFH thanks for the help in getting this server up and running.
 
Back
Top