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

Follow

Comments

6 comments

  • Avatar
    Miomir Besarabic

    Hi,

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

    0
    Comment actions Permalink
  • 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 https://support.plesk.com/hc/en-us/articles/213946825 or contact regular Plesk support.

    0
    Comment actions Permalink
  • Avatar
    Miomir Besarabic

    @Denis

    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 example.com as example.com:8443 to redirect to Plesk hostname.com:8443 with Custom Plesk Host extension. In Hosting Setting for domain example.com in Plesk is set "Permanent SEO-safe 301 redirect from HTTP to HTTPS".

    In browser I type example.com:8443 and it show because "Permanent SEO-safe 301 redirect from HTTP to HTTPS". https://example.com:8443. Safe browsing expects SSL certificate for example.com but because is already redirected to the Plesk (hostname.com:8443) 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 example.com and just redirected to the Plesk.

    You can easily reproduce this.

     

    0
    Comment actions Permalink
  • 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.

    0
    Comment actions Permalink
  • Avatar
    Fabian Marsiglione

    Hello

    This works perfect but as @Miomir Besarabic says...

    ONLY works if you type in browser : domain.com:8443, www.domain.com:8443 or http://domain.com:8443 (WITHOUT https) 

    If you type : https://www.domain.com:8443 or https://domain.com:8443 NOT redirects to https://hotsname.com:8443 and you get SSL cert error.

    You fixed this?

    Also.. is not any way to set all domains login to plesk using the domain with :8443 as cpanel does?

    Regards
    Fabian

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Fabian,

    PPPM-7923 is yet to be resolved. The ETA is to be available later.

    All the changes about it will be added to this article.

    > Also.. is not any way to set all domains login to plesk using the domain with :8443 as cpanel does?

    Plesk may be accessed using any of the hosted domain with the link https://<domain>:8443 by default.

    However, the SSL certificate for selected domain will be used for securing the access: https://support.plesk.com/hc/en-us/articles/213954265-How-to-secure-Plesk-login-page-with-SSL-certificate-

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request