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:- Plesk Onyx 17.5.3 23 March 2017 (Linux)
- Plesk Onyx Update 14 30 January 2017 (Windows)
- Plesk Onyx 17.5 Release 20 April 2017
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
Bug #PPPM-5434 have been fixed in Plesk Onyx 17.5.3, Plesk Onyx Update 14
Please sign in to leave a comment.