Redirect from domain to server hostname on port 8443 is blocked by Safe Browsing




  • Avatar
    Miomir Besarabic


    I'm on Plesk 17.8 and my domains have all set "Permanent SEO-safe 301 redirect from HTTP to HTTPS". If I try give me warning about unsecure connections. The same if I try This should be fixed because today mostly domains use "Permanent SEO-safe 301 redirect from HTTP to HTTPS". 

  • Avatar
    Denis Bykov

    @Miomir Besarabic

    According to reported symptoms, redirect to HTTPS works properly, but SSL certificate for the domain is either does not include the proper domain name or expired or self-signed.
    The issue seems to be irrelevant to the current article. Please refer to or contact regular Plesk support.

  • Avatar
    Miomir Besarabic


    The issue is relevant to Custom Plesk Host extension and have nothing to do with SSL certificate. SSL certificate for domain is valid. Let me explain exactly.

    I try domain as to redirect to Plesk with Custom Plesk Host extension. In Hosting Setting for domain in Plesk is set "Permanent SEO-safe 301 redirect from HTTP to HTTPS".

    In browser I type and it show because "Permanent SEO-safe 301 redirect from HTTP to HTTPS". Safe browsing expects SSL certificate for but because is already redirected to the Plesk ( and Plesk certificate is used warning is showed and access to the Plesk blocked.

    Earlier with only http:// worked fine because browser not expected any SSL certificate for and just redirected to the Plesk.

    You can easily reproduce this.


  • Avatar
    Artyom Baranov

    @Miomir Besarabic,

    Hello! As I can see, you have created a ticket for Plesk support in regards to the issue. I believe the support team will check it soon and provide you with a solution.

Please sign in to leave a comment.

Have more questions? Submit a request