• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Apache 2 Default Page Displaying

Q

quixrick

Guest
I Have Set Up A Domain In Plesk And When I Try And Access It Via The Web Browser, I Either See The Default Apache 2 Welcome Page (If Going To The Domain) And 404 Not Found (If Going To A File Inside The Domain.)

In The /var/log/httpd/error_log, I Can See That What The Problem Is:

[Sat Aug 04 16:09:17 2012] [error] [client xxx.xxx.xxx.xxx] File does not exist: /var/www/html/sandbox

It Is Trying To Load The Page From "/var/www/html" And Not "/var/www/vhosts/domain.com/httpdocs"

I Have Tried Modifying The "vhost.conf" File And Using "httpdmng" To Apply The Changes. I Think I Was Barking Up The Wrong Tree With That One As The Problem Seems To Be Happening BEFORE It Reaches The "vhost" Files.

I Saw Another Post Of A User Having A Similar Problem, But FastCGI Was Causing It To Not Read The "vhost.conf" Files, So In Plesk, I Switched The Domain From FastCGI To Apache. No Dice.

I Also Tried Running:
"/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair"

Got The "Congratulations! All stages of the upgrade were successful. psa is now running on your system." Message

...Restarted Apache And The Server.

That Didn't Fix It Either.

"httpd.conf Says" That The Default Website Is "/var/www/html" And That The "VirtualHost" Section Is Entirely Commented Out. I Thought That Was Probably The Solution Right There, However, On The Other Two Servers Where The Domains Are Working Well, The httpd.conf Files Have The Same Configuration.

I Just Am Not Sure Where The Missing Link Is In Telling Apache To Point To The Plesk Directories Instead Of The Default.

Thanks For Any Assistance You Can Provide.

-Rick
 
Try /usr/local/psa/admin/bin/httpdmng --reconfigure-all and also with --reconfigure-server
 
I Had Already Tried httpdmng Multiple Times With The --reconfigure-all Flag, But Never Tried The --reconfigure-server.

I Tried Them Both This Morning And Restarted Apache, But Am Still Getting "File does not exist: /var/www/html/sandbox" In The Error Log.

Thanks For Responding, Though, I Do Appreciate The Attempt.

-Rick
 
From What I Can Tell, (And Please Correct Me If I'm Mistaken) Plesk Does Not Use httpd.conf To Tell The Web Server Where To Look For Files. If That's True, Where Does It Set The Path For Files? Maybe I Can Work My Way Back Up From There.
 
Solved!

Solved... Short Answer Is It Was A Firewall Issue.


Long Answer In Case Anyone Else Has This Problem...

When Using Plesk With An External Firewall, You Have To Create A Map File And Map The Outside IP Address To The Inside IP Address In Order For Plesk To Recognize It.


I Followed The Steps In This Article:
http://support.godaddy.com/help/art...x-501-or-asa-5505-hardware-firewall?locale=en


And I Get This Response:
Generating DB update script...
ok
Updating database...
ok
Reconfiguring DNS:
domain nwcommon.com...
ok
Restarting DNS service...
ok
Reconfiguring Apache...
ok
IP addresses are successfully changed.

That Fixed It. Now I Can Get To The Websites.

Thank You lvalics For Trying To Help Me. I Am Really Grateful. And So Happy To Have It Working.

-Rick
 
Back
Top