• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Virtual hosting quit working

JustonG

Basic Pleskian
Hello,

Today I shut my server down in order to replace a defective and nonfunctional network router. Upon hooking everything backup and rebooting the server I am having an issue getting my website back up. Plesk is running, because I am able to login to the panel, but when I try to browse to my website all I get is the default apache page:

It works!

This is the default web page for this server.

The web server software is running but no content has been added, yet.

I tried adding a new domain and new site, but to no avail. It comes up the dafault apache page and not the default plesk page. It appears that somewhere between plesk and apache vhosting & virtual servers quit working after the server was powered back up.

Can you please give me a way to fix this so i can get my website back up and running?

Kind Regards,
Juston G
 
Try to run:
/usr/local/psa/admin/bin/httpdmng --check-configurations
and provide output.
Also, you can run:
/usr/local/psa/admin/bin/httpdmng --reconfigure-server
but it a bit more dangerous operation. Are you have a back up of you server?
 
Try to run:
/usr/local/psa/admin/bin/httpdmng --check-configurations
and provide output.
Also, you can run:
/usr/local/psa/admin/bin/httpdmng --reconfigure-server
but it a bit more dangerous operation. Are you have a back up of you server?

root@suprtech:~# /usr/local/psa/admin/bin/httpdmng --check-configurations
Unrecognized option: '--check-configurations'

no I do not have a backup of my server, how can I do this?
 
Ok, you should use:
/usr/local/psa/admin/bin/httpdmng --check-configurations ''
instead (there is two single quotes at the command end).

Some backup functions exists in 'Tools&Settings -> Backup Manager" page.
 
Last edited:
Ok, you should use:
/usr/local/psa/admin/bin/httpdmng --check-configurations ''
instead (there is two single quotes at the command end).

Some backup functions exists in 'Tools&Settings -> Backup Manager" page.

okay I made a backup, now what?
 
Try to run:
/usr/local/psa/admin/bin/httpdmng --check-configurations
and provide output.
Also, you can run:
/usr/local/psa/admin/bin/httpdmng --reconfigure-server
but it a bit more dangerous operation. Are you have a back up of you server?


I also tried running

/usr/local/psa/admin/bin/httpdmng --reconfigure-server

But nothing changed, still have the same issue
 
Is there any output of
/usr/local/psa/admin/bin/httpdmng --check-configurations ''
?
If any, please provide it.

Also, try to run:
/usr/local/psa/admin/bin/httpdmng --reconfigure-all
if there is any error please provide.

What of linux distribution do you use?

Are you sure, that server IP didn't change due to router replacement?
 
there was no output of /usr/local/psa/admin/bin/httpdmng --check-configurations ''

and the only ip that changed was instead of having the connection coming straight into the server, we are passing through a router now. the external ip is 68.14.202.251, which that was set in the server config files (hosts & interfaces) but since hooking the router ip, we assign a static of 192.168.1.7 to the server.

As I stated earlier we can get to the Plesk panel at 68.14.202.251:8080 but using the actual domain www.suprtech.com only returns the apache test page and not our website
 
Please, run:
apache2ctl -tD DUMP_VHOSTS
and provide output.

Output of apache2ctl -tD DUMP_VHOSTS:
root@suprtech:/etc# apache2ctl -tD DUMP_VHOSTS
VirtualHost configuration:
68.14.202.251:80 is a NameVirtualHost
default server default (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:68)
port 80 namevhost default (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:68)
port 80 namevhost lists (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:140)
port 80 namevhost horde.webmail (/opt/psa/admin/conf/generated/13377849810.79480500_horde.include:4)
port 80 namevhost suprtech.com (/var/www/vhosts/suprtech.com/conf/13377255980.68532000_httpd.include:139)
port 80 namevhost justongriggs.com (/var/www/vhosts/justongriggs.com/conf/13377253680.03038800_httpd.include:138)
68.14.202.251:443 is a NameVirtualHost
default server default-68_14_202_251 (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:102)
port 443 namevhost default-68_14_202_251 (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:102)
port 443 namevhost lists (/opt/psa/admin/conf/generated/13377849810.79480500_server.include:167)
port 443 namevhost horde.webmail (/opt/psa/admin/conf/generated/13377849810.79480500_horde.include:48)
port 443 namevhost suprtech.com (/var/www/vhosts/suprtech.com/conf/13377255980.68532000_httpd.include:10)
port 443 namevhost justongriggs.com (/var/www/vhosts/justongriggs.com/conf/13377253680.03038800_httpd.include:10)
wildcard NameVirtualHosts and _default_ servers:
*:80 is a NameVirtualHost
default server suprtech.com (/etc/apache2/sites-enabled/000-default:1)
port 80 namevhost suprtech.com (/etc/apache2/sites-enabled/000-default:1)
Syntax OK
 
I am having the same problem, have you found a fix for this?
 
Back
Top