Media Temple was acquired by GoDaddy back in 2013. They were left alone with their own customers, products and team. They handled things well and were left as a separate arm of the GoDaddy conglomerate… For about a decade.
Slowly over time the GRID (shared hosting) and DV (servers) got… outdated. Anyone in the tech industry knows 10 year old hardware is OLD in robot standards. So it appears that the hardware update limits caused software update limits and the whole system needed an overhaul.
So now… with new emails coming out about the transition… it looks like THE GREAT MERGE is upon us! (That’s what I’m calling it).
They started moving over products to the GoDaddy backbone and consolidating product offerings. It is what it is… nothing stays the same forever. With that being said… here are some of the things clients have been asking about for Media Temple accounts.
Most of these are compatibility based or just configuring the new hosting how you’d prefer. Some of these are actions to take and some is just process concepts that give clarity to the big picture.
GRID to cPanel:
- If you had the standard GRID product, the vast majority of those got moved to cPanel (Max) shared hosting.
(However… if your database was out of the ordinary (records/ tables/ size); or your i-node/file count/quantity was over 250K; then you got moved to one of the higher shared hosting + tiers.) - The first major topic is PHP version of the site is being limited and not reflecting the correct global hosting PHP version.
- The second issue I see is the website is downloading PHP files instead of displaying site content.
- Next we go over why your website form just can’t get a message out of the cPanel shared hosting.
- Most people are just asking how do I find the primary FTP cred’s for cPanel so I can update my site?
DV to VPS:
- Your previous resources are the same as they were. The name of the product may not reflect the actual resources allocated to your migrated DV. They just moved everything over as a snapshot. Same price; same content, data, config; same resource allocation; same IP.
- The primary admin is now ‘root’ and you should probably reset your password. There is no more ‘admin’ or any other user path. You log in with IP (or assigned URL if you’ve assigned a primary over the IP); you use ‘root’; and you update your password on the settings page of the MYH hosting panel for the VPS product.
- You should probably reassess your product choice to align with the talent on your team… meaning when these VPS accounts hit GoDaddy first level support, the extra level of assistance with running SSH commands and toggling your Plesk settings may not happen as frequently. Know what product you have… is this Un-Managed; Self Managed; or Fully Managed? Because these are all different product tiers. Know what help you have, with your contacts and vendors and staff… and know where the weak points are.
- If you want to change the CentOS version or update the Plesk, you’re probably best off just backing everything up; doing a Plesk export of your stuff; selecting the ‘hosting reset’ option from the server actions menu… and just giving it a nice factory reset. Then you import your Plesk config and data back in and things should be all new and fresh. If you keep the same product just force the system to install the OS again, it’ll push the latest version and you can keep your price lock.