SSL installed but no lock, invalid intermediate


#1

I ran this command:
Followed this tutorial: https://support.tilaa.com/hc/en-us/articles/228652367?input_string=ssl+certificate

It produced this output:
https://www.whynopadlock.com/
https://www.ssllabs.com/

My web server is (include version):
Directadmin 1.53

The operating system my web server runs on is (include version):
CentOS7 and apache 2.4.29

My hosting provider, if applicable, is:
Tilaa unmanaged VPS

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

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

Followed the tutorial but somehow it does not show the padlock… and have this weird error message… Also ipv6 is not properly linked i’m afraid… Another thing is if i login to my server at: server.futurastudio.nl:2222 it shows me a super unsafe ssl certificate :frowning: not sure what i did wrong… would be awesome if you guys could help!


#2

As shown by SSLLABS:
https://www.ssllabs.com/ssltest/analyze.html?d=smoothieservice.nl
The problem is with the IPv6 address (not the IPv4 address) which is using a self-signed “localhost” cert.
If you are not using IPv6 you should remove that DNS entry.

the cert used at server.futurastudio.nl:2222 is also self-signed - for “Futura studio”.


#3

I followed the tutorial again, in case i missed something, however now my directadmin is quite fucked up :frowning: need to accept the certificate for every small thing i do and only a small amount of the images load in…

Next to that i unlinked the IPv6, it can take up to 24 hours though :confused:

I have no idea how to make the cert at server.futurastudio.nl:2222 not self signed and made by letsencrypt… i guess i’m kinda obligated to hire an programmer for this… expected someone here to know how to solve the issues


#4

After messing around with it way more and following the tutorial another time i found the issue and resolved it!

In this tutorial sometimes it said: “your.hostnamehere.com” and i assumed it should be: server.myhostname.nl but it should have just been hostname.nl…
So i finally got the green lock!


#5

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