Issue Getting no site on address on secondary IP

[NickBucko]

I've recently added an IP address in Plesk but now when I set any site up using that IP I get the default web server (not the standard index.html page that Plesk adds on site creation) when I go to the site. Is there anything to check in the DB to make sure the site is setup on the correct IP? I've tried httpdmng --reconfigure-domain with no luck.

This is the text of the page I'm getting:

Web Server's Default Page
This page is generated by Plesk, the leading hosting automation software. You see this page because there is no Web site at this address.

You can do the following:

• Create domains and set up Web hosting using Plesk.

 

[IgorG]

Make sure that your site hostname is resolvable to this new IP address.

 

[NickBucko]

Thank you for the reply. I have pointed the site hostname using both my hosts file and an actual DNS record. Doesn't work.

 

[Bitpalast]

Follow this short guide to try to narrow the issue down:
- Ping the new domain. Does it respond with the correct (secondary) IP address?
- Check the file "/var/www/vhosts/system/<domainname>/conf/nginx.conf" for the "listen" directive. Is this directive using the secondary IP address?
- In the same file: Does the line "root ..." read "root "/var/www/vhosts/<domainname>/<document root directory as set in the domain>"?
- Check the file "/var/www/vhosts/system/<domainname>/conf/httpd.conf" for the "listen" directive. Is this directive using the secondary IP address?
- In the same file: Does the line "DocumentRoot ..." read "root "/var/www/vhosts/<domainname>/<document root directory as set in the domain>"?
- In the directory /etc/nginx/plesk.conf.d/vhosts: Do you find a symbolic link "<domainname>.conf" that is pointing to "/var/www/vhosts/system/<domainname>/conf/nginx.conf"?
- In the directory /etc/httpd/conf/plesk.conf.d/vhosts: Do you find a symbolic link "<domainname>.conf" that is pointing to "/var/www/vhosts/system/<domainname>/conf/httpd.conf"?

 

[NickBucko]

Follow this short guide to try to narrow the issue down:
- Ping the new domain. Does it respond with the correct (secondary) IP address?
- Check the file "/var/www/vhosts/system/<domainname>/conf/nginx.conf" for the "listen" directive. Is this directive using the secondary IP address?
- In the same file: Does the line "root ..." read "root "/var/www/vhosts/<domainname>/<document root directory as set in the domain>"?
- Check the file "/var/www/vhosts/system/<domainname>/conf/httpd.conf" for the "listen" directive. Is this directive using the secondary IP address?
- In the same file: Does the line "DocumentRoot ..." read "root "/var/www/vhosts/<domainname>/<document root directory as set in the domain>"?
- In the directory /etc/nginx/plesk.conf.d/vhosts: Do you find a symbolic link "<domainname>.conf" that is pointing to "/var/www/vhosts/system/<domainname>/conf/nginx.conf"?
- In the directory /etc/httpd/conf/plesk.conf.d/vhosts: Do you find a symbolic link "<domainname>.conf" that is pointing to "/var/www/vhosts/system/<domainname>/conf/httpd.conf"?

-I've switched the domain back to the primary IP for now so ping won't help. I can use my hosts file which I've done many times in the past on other servers without issue. I can see my requests hitting in /var/log/nginx/access.log when I get the default Plesk page so I'm hitting the server.
-/var/www/vhosts/system/<domainname>/conf/nginx.conf does show the secondary IP for listen
-Root directory is correct in nginx.conf
-/var/www/vhosts/system/<domainname>/conf/httpd.conf doesn't have listen but does have VirtualHost entries that have the correct IP.
-DocumentRoot is correct in httpd.conf
-/etc/nginx/plesk.conf.d/vhosts does have symbolic link
-Apache directory for me is /etc/apache2/plesk.conf.d/vhosts and does have symbolic link