• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question How to configure customer subscription with multiple domains if they cancel the main domain?

Marc Pol

New Pleskian
Hi,

I am struggling with the following problem:

For our costumers we create subscriptions based on their domainname, so that when they buy multiple domains at our company the buyed domains can be set under their subscription. The problem with this construction is that, when customers cancel their main domain that is binded to their subscription we need to remove the main subscription. This is a big tasks because we have to create a new subscription and migrate the existing domains to this newly created subscription.

So i was thinking:

What if i create a subscription with the costumer relation number in our portal. But plesk only listens to real domains. So that is not a option. I do not want to create seperate subscription for every domain that is buyed under the same customer. That is going to be a administrative mess.

I am wondering how the rest of you is dealing with this problem.
 
Some providers simply create "fake" domain names like <customer id>.xx (34567.xx, 9875.xx). Some use long internal subdomains like <subdomain>.<id>.<hostname>.tld (copper.t78.hostname-at-provider.com etc.). You can also rename the main domain to such a name when the main domain is cancelled. And even if you let it sit just there as it is - if it is no longer registered or routed to the system, nothing will happen anyway.
 
Back
Top