• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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