• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Forwarded to devs Migration causes Permanent SEO-safe 301 redirect from HTTP to HTTPS to be enabled

tkalfaoglu

Silver Pleskian
Username: tkalfaoglu

TITLE

Migration causes Permanent SEO-safe 301 redirect from HTTP to HTTPS to be enabled

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Centos 8 Obsidian

PROBLEM DESCRIPTION

After a migration, I found that the hosted site would not open and give security errors.
It turns out the "Permanent SEO-safe 301 redirect from HTTP to HTTPS" option was somehow enabled at the destination server whereas the source server has that option disabled.
I guess the migrator sets that option regardless.

STEPS TO REPRODUCE

Migrate a domain where the said option is off.

ACTUAL RESULT

The domain is recreated at destination server with that option on

EXPECTED RESULT

The value of that flag be respected

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Developers migrated a domain from Onyx to latest Obsidian with HTTP redirect disabled, and after migration, it was also disabled. So they could not reproduce this issue.

The only bug reported related to this is PMT-4611, but it was already fixed.
They recommend the following:
  • Check if Obsidian is the latest Change Log for Plesk Obsidian and also if all updates for Extensions > PLesk Migrator were installed.
  • If everything is up to date, they recommend opening a ticket with Plesk Support because migrations to Obsidian are working properly so far.
 
Back
Top