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

Errors while renaming subscription name

XAMeLeOH

New Pleskian
Dear support team,

We got an error when customers try to change subscription name. When this happens users couldn't connect to FTP. Plesk changes the homedir but doesn't recreate the webspace. As the result user doesn't see DOCROOT directories like httpdocs, site1, site2, etc. Can you suggest any workaround?
 
My understanding of that feature is that, plesk just renames the folder /var/www/vhosts/old-subscription.com to the /var/www/vhosts/new-subscription.com leaving the rest of the files intact ..

I have just tested it here, and indeed that is exactly what happened!
 
So can you suggest any workaround to avoid this situation? Now any our customer can shoot himself in the foot. They lost access to their files after renaming the subscription. Maybe there is a way to restrict this ability?
 
If you have given the user an ability to create a domain name, then of-course they will also have the ability to rename it ...Same thing, disabling the ability to create domains also automatically disables the ability to edit them!!
 
Please give me answer to the questions:
1) How do you think this renaming behavior is correct?
2) Is there any hope this renaming feature will work correctly in the foreseeable future?
 
If you can provide the plesk team and (us too) instructions of how we can re-produce that problem it would greatly help in the resolution of such a bug if does exist.

How it works, is how it's currently ...(The options are very limited so the procedure is straight forward)
 
I found out that this error is the result of this bug: http://forum.parallels.com/showthread.php?283284-Subscribers-unable-to-remove-domains-completely
So I will enable 'Hosting settings management' feature for my customers but if anybody wants to repeat error described here you should:
1) Create new subscription with the domain example.com.
2) Add a new domain example.net.
3) Delete the domain example.net.
4) Rename the main domain from example.com to example.net.
Because the domain example.net wasn't deleted completly, the directory /var/www/vhosts/example.net still exists and the Panel will show you an error message while trying to rename the subscription.
 
Back
Top