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

Issue after shift from inetpub - PleskFatalException - xxxx is out of webspace

Andre235

New Pleskian
Hello, after I moved C:\inetpub\vhosts to D: with the Plesk Reconfigurator I get 500 PleskFatalException with "Path-to-a-domain-on-d:" is out of webspace when calling the domains in the Plesk configuration. What can be the problem for this?
 
Looks like the domain document root directory in the database differs from the actual one.
Check that www_root and home paths are set correctly in Plesk database, for example:

Code:
select id,home from sys_users where home like "%example.com%";
+----+--------------------------------+
| id | home                           |
+----+--------------------------------+
| 15 | C:\inetpub\vhosts\example.com  |
+----+--------------------------------+

select www_root from hosting where sys_user_id=15;
+----------------------------------------+
| www_root                               |
+----------------------------------------+
| C:\inetpub\vhosts\example.com\httpdocs |
+----------------------------------------+
 
Thank you... updating the home did it. The Plesk Reconfiguration Tool showed no error (except something with ftp), so i thought i should updated it...
but i had to change the path in the IIS on hand, So there may have been errors that just weren't displayed
 
Back
Top