Articles in this section

See more

Client cannot enable Permanent SEO-safe 301 redirect from HTTP to HTTPS

Avatar
Denis Bykov
Updated
Follow

Applicable to:

  • Plesk for Linux

Note: This article has the reference to the issue with the fix available:

  • #PPPM-5434 "On CentOS 7.3 x64 servers, a customer could not set up a permanent 301 redirect from HTTP to HTTPS for their subscription."
    Fixed in:
Please consider updating your server:

Symptoms

It is not possible to enable Permanent SEO-safe 301 redirect from HTTP to HTTPS in Domains > example.com > Hosting Settings from a client's account - the checkbox becomes unchecked again after applying the changes.

Cause

Such behavior is caused by a Plesk bug with id #PPPM-5434 which is fixed in microupdates.

Resolution

Install Plesk microupdates.

Comments

1 comment

Sort by Date Votes
  • Avatar
    Integrator

    Bug #PPPM-5434 have been fixed in Plesk Onyx 17.5.3, Plesk Onyx Update 14

    0
    Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles