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

https:// instead of http:// after migration from Plesk 9.3 to 10.3

Jay Versluis

Regular Pleskian
Good evening,

I just got a brand new server running Plesk 10.3 (nice!) and I'd like to migrate some of my domains over from an older server running Plesk 9.3. Migration Manager works fine for a couple of test domains. So far so good.

However once a domain is transferred in and the DNS is pointed to the new server, it appears the website no longer loads CSS via a standard http connection. For example, my test domain is a WordPress site at http://artcoachapp.com which worked fine with the old server. Browsing this domain on the new server results in no formatting being loaded... unless I use https://artcoachapp.com.

I've not come across this phenomenon before on previous migrations - can you shed some light on this? Can I change my domains from https back to http? Even with a valid certificate installed, I don't want all my websites to be secured.

I very much appreciate your help or a pointer in the right direction.
 
Seems that for some reason, when migrating a Wordpress installation - the migration manager changes the MySQL database to point to https://your-wordpress-install.com

To fix, go into Webadmin for your database (phpMyadmin) and change "siteurl" and "home" to the correct address for your blog.
 
Mick, you're a GENIUS! I didn't even think to look in the database.

I've changed the values and it totally works, many thanks for sharing this ;-)
 
Back
Top