Brandon Yap

Merging Plesk subscriptions

Update: 18/08/2020 Plesk Obsidian is now able to move domains between subscriptions thus negating the need for any external scripts. Please use this in built function instead. Keeping this article for posterity. This article could have been called “Merging domains from one subscription to another” or “Moving domains between subscriptions”. But its goal remains the same. If you’re arrived at this page then you probably already know what you’re looking for. With the business model change from Plesk 9 to Plesk 10, the upgrader splits each customer’s domains into it’s own subscription. Highly annoying if you want to keep track of […]

Merging Plesk subscriptions Read More »

Unable to remove customer/subscription

When trying to remove a customer or subscription, you may get this error message in Plesk: Unable to find service node for web service on domain with id=xxx This was supposed to be fixed in 10.4.4 MU #13 but isn’t in all cases. I hit this error and the cause turned out to be because the subscription had no IP address assigned to it. To fix this, go into the Hosting Settings of the subscription. Select an IP address, you’ll also have to reset the password. Once you do this, you should be able to remove the customer and subscription.

Unable to remove customer/subscription Read More »

Switching to from Internode to TPG

What? Are you crazy?? That’s what you’re thinking isn’t it. First off, why I am writing this post. I want to share my unbiased experience switching from Internode to TPG. Let me assure you that this is not a sponsored post! As you no doubt would have recently heard, iiNet have bought Internode. I’ve been a loyal customer of the Node for over 6 years, but living out of the city areas means i’m on a Telstra DSLAM on one of Internodes Easy Reach plans. Due to the “Telstra price squeeze” (in which their retail division undercuts their wholesale pricing

Switching to from Internode to TPG Read More »

Virtual machine must be running in order to be migrated

Lately i’ve run into a strange issue where an ESXi server gets into a state where VMs running on it are not able to be migrated to other ESXi servers. This is the error that comes up when you try to vMotion the problematic VMs. A general system error occured: Virtual machine must be running in order to be migrated. I’ve contacted VMware support and they tell me there’s no other way to fix this than to shutdown and powerup the VMs. Simply rebooting them does not work as the problem seems to be linked to their registration with ESXi

Virtual machine must be running in order to be migrated Read More »

Scroll to Top