Seems like SSL is successfullly installed. Still getting Connection Not Secured

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: do not have access

It produced this output: none

My web server is (include version): not sure

The operating system my web server runs on is (include version): linux

My hosting provider, if applicable, is: rackspace

I can login to a root shell on my machine (yes or no, or I don't know): no

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): plesk

I'm trying to renew my SSL certificate on (as the auto-renewal does not seem to be working)

Althought Plesk is telling me I've successfully installed the new certificate, visiting the website tells me my connection is not secure.

I've also tested my site with and it seems I have no mixed content, but I do get this error:


X Your webserver is not forcing the use of SSL.
You may want to add a redirect to ensure a secure connection is used. More Info

(under more info)
Forcing the use of HTTPS:// on your site will ensure that visitors to your site are always using and aren't able to access an insecure URL. This is recommended since if a visitor does access your site as everything will be marked as "Not Secure".

Below code is for forcing HTTPs on an Apache webserver. If you are using another webserver such as lighttpd, nginx, etc you will need to contact your web hosting provider for assistance.

Add the following code to the .htaccess file in your webhosting account:

RewriteCond %{HTTP_HOST} [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$$1 [R,L]

Once this change is made your site will no longer be accessible on the insecure "" URLs and all visitors will be redirected to "" instead.

If I add an .htaccess file to my server with a redirect, I get this error under mixed content:

The Mixed content tests failed. Please be sure that you can connect to your site over SSL and try again.
Error Returned: net::ERR_TOO_MANY_REDIRECTS at

Hi @gregorino

now you have a loop: -> ... endless.

So you have too many redirects. First step: Remove these three rows:

Then create a new certificate via plesk with two names: and

So https works with both domain names.

@JuergenAuer, as in the other thread, this redirect only applies if the user accessed the resource via HTTP, so I don't think it should create a loop by itself!

1 Like


But then must be other definitions, which creates a loop. Testing (accepting the wrong certificate) creates a redirect to and there again a loop.

Yes, I guess that must be caused by a redirection defined in another file.

I’ve found a setting in Plesk that lets me apply a certificate to both and at once. This did not seem to fix the issue though. Now instead of saying my connection is not secure my browser says:

This page isn’t working redirected you too many times.
Try clearing your cookies.

I’ve removed the .htaccess redirect that @JuergenAuer mentioned. I’ve also tried clearing my cache and deleting cookies. Did not seem to fix the issue. Any other ideas?

Now you have fixed your redirect. is now redirected to

There the certificate is wrong.

But you have created already two correct certificates (created today).;include_subdomains:false;

So perhaps there is an option so plesk can use one of them

PS: Where was the redirect loop defined?

I had placed an .htaccess file in the wrong folder which was causing an infinite loop, glad that problem was fixed easily.

Unfortunately, as for the two certificates. There is a place I can see all the certificates set up on a website, I can only see 1 though. I have deleted and re-created many certificates today. Is it possible the google report is outdated and shows a certificate I had deleted an hour ago?

Thanks. Good to know.

Google shows the result of the Certificate Transparency Log (CT). Every certificate which is signed from a public Certificate Authority is there logged. The Log is read only. So revoking or deleting a certificate doesn't change this log.

PS: There is a limit - 5 certificates with the same names in 7 days. So you shouldn't create too much certificates. There is a test system. But I don't know if plesk allows to use that.

Thank you, I will stop creating new certificates. As far as I know plesk does not allow for testing.

Any other insights on what to do? I am at a loss. I have opened a ticket with my hosting provider but they often take up to a week to get back to me…

There is again something wrong. I accepted the wrong certificate - and there was a loop again.

Now -> ->

I don't know how plesk handles that inside. But perhaps there are some configuration files you are able to edit.

Hmm. Ok thank you for the insight. I will do some more research while waiting to hear back from my hosting provider

So it seems I’ve successfully removed the loop :smiley: just by messing around in the settings in Plesk. I had it set to force users to use instead of This seems to have fixed the issue.

Now for my other issue. Plesk is telling me my certificate is set up correctly. If I check on it also says my certificate is set up correctly. But I still am getting the “connection not private” error if I try to go to my page. I can now click through to the website, and access the website (although I see the not secure icon in the address bar)

You're using the wrong certificate, which is only for and not for both and

Of the seven certificates you've issued, two (which you're not using) cover both names, while five (one of which you're using) cover only one name:;include_subdomains:false;

Thanks! I was able to fix the issue with this information. Thanks both of you!!

1 Like

Now your certificate is correct:

And there is no loop. Your CommonName is, but there are two alternate names:


Now it's ok.

First I saw a warning. But that was because I had added an exception.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.