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

Client expired and I need to enable it back

Chuck Verc

New Pleskian
Hi,
I have a client that expired today and his site went down auto by Plesk (which is good).
Now I got a call saying he wants it back up and working since he just paid. I went to his client resource usage to change the expiry date and saved. Now the site answers with errors on the databases. It's as if Plesk did not re-enable the databases upon setting the expiry date.

How do I go about getting his site back up and running ?

Thanks
Charles
 
What sort of database error there? Could you please provide more detailed information about this problem?
 
Hello,
I don't remember the exact message but basically it said something along the lines of "The user does not have sufficient permissions to select the table content". What's strange is that the domain has a subdomain with a second database and that one was working after I changed the expiry date (although I have no idea if it did work while the client was expired).

I've solved the issue by manually changing the user mappings of the database user. The mappings had db_denydatareader and db_denydatawriter checked and had db_owner unchecked.
 
Back
Top