• 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.

503 Errors after Moving Inetpub

Matt Sonnentag

Basic Pleskian
I installed Plesk 11 on our IIS server and had moved the default inetpub from C: to D: on the server prior to installing plesk. After the Plesk 11 install I was getting a 503 error when navigating to the control panel.

Turns out something in the install must reference C:\inetpub and the proper permissions did not get put on d:\inetpub and when the panel was accessed the application pool for the panel would die with an insufficient permissions error.

Initiallly, the fix was to go through the inetpub directory on both drives and make sure that the new permissions matched those of the directory on the c drive. Basically the psaadm account needs to be able to list folder contents in the temp\app pool directory.

This worked yesterday, but for some reason this morning the error has returned and I can't seem to get it working again despite multiple reinstalls. Anyone have any ideas?
 
Last edited:
Back
Top