• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Subscription is suspended although the service plan is changed to unlimited validity

Thomas Becker

Basic Pleskian
Hello,
I have a serious problem.

One customer had added a service plan that has a validity period (expiration) of one month. This is because of providing the customer a test account which expires after a month.

Two days ago I changed the service plan of that customers subscription to a service plan with a unlimited validity period. The System now is still locking his account every night.

I did the same with lots of customers before without such problems. So I expect that a Plesk update changed something. Please give me some advice how to proceed.

Where is Plesk storing the information of the subscriptions / customer accounts that are suspending? Can I manually edit that?

I already changed the service plan for the subscription and changed it back to overwrite some problems that may exist but that doesn't work.

Thanks for any help.
 
Last edited:
The expiration date is in MySQL table
psa --> Limits --> [ID of domain] --> expiration

I edited the limit manually to "2d31" (-1) but I still don't know why Plesk is not changing it when adding a service plan with unlimited expiration.

This is a Plesk issue so please someone from Parallels check that.
 
Last edited:
Back
Top