SSL Isn't working

[tomd]

I am having problems with SSL, I keep getting random problems. Up until today my website has been secured by the SSL provider DirectAdmin advice using. Today the padlock disappeared from the left hand of the address bar and it is now saying that the website is insecure. I have had blank pages appearing when trying to access :2222 even though this is hostname secured per DirectAdmins install guide to do this. Then when I clear the cookies out and try and log back in via :2222 it says this is an insecure connection. On top of this as said before the padlock has vanished and my website is now insecure. What's going on with SSL today, it has been working fine until today?

 

[ikkeben]

For support DA needed i think

Browser used and version

DA versions used also OS and custombuild versions

When the cert is or should been udpated by letsencrypt.

Do you still see for that domain(s) at ssl the lestancrypt cert?

Or is it only for the DA panel at port 2222 ?

Other domains ok?

I can't help but these info's could be important!

Also look in docs where to find versions or the letsencrypt renwed yes or no in ssh for the hostname.


Do you use hostname as "vps.exampledomain.com " ?
What is example.com as domain doing ?

IPV4 or IPV6 at your place connection where you use the browser to login?

Server itself yes or no in ipv4 ipv6 or both?

Do you use forced ssl, and or also redirect www or non www settings in DA panel or somewhere else.?

You can have that force also set for DA ADMIN PANEL a check checkbox somewhere i don't know by head , is that set or not set?

Test with online testers the ipv6 on https and http!

and your browser own connection to.

try other browser other computer other internet connection.

Test check your dns and nameserver also online for ipv6 and ipv4!!!!

FYI i have problems some times to as testing on https://en.internet.nl/ then sometimes seems random on ipv6 no https , wen testing same time however with a ipv6 online tester on https no problem.

No errors in log on server however at that DA BOX centos 8 alma latest DA and custombuild.

OYEA sometimes if new cert or config a browser need a kind of reset cookies and co , mostly this is only with ftp programs but sometimes check browser on caching things.

If it is browser that is going wel after there reset and clear al cookie, sessions, cache or even if it is going wel on other computer and connection, then nogood and maybey kind of BUG DA

 

[tomd]

For support DA needed i think

Browser used and version

DA versions used also OS and custombuild versions

When the cert is or should been udpated by letsencrypt.

Do you still see for that domain(s) at ssl the lestancrypt cert?

Or is it only for the DA panel at port 2222 ?

Other domains ok?

I can't help but these info's could be important!

Also look in docs where to find versions or the letsencrypt renwed yes or no in ssh for the hostname.


Do you use hostname as "vps.exampledomain.com " ?
What is example.com as domain doing ?

IPV4 or IPV6 at your place connection where you use the browser to login?

Server itself yes or no in ipv4 ipv6 or both?

Do you use forced ssl, and or also redirect www or non www settings in DA panel or somewhere else.?

You can have that force also set for DA ADMIN PANEL a check checkbox somewhere i don't know by head , is that set or not set?

Test with online testers the ipv6 on https and http!

and your browser own connection to.

try other browser other computer other internet connection.

Test check your dns and nameserver also online for ipv6 and ipv4!!!!

FYI i have problems some times to as testing on https://en.internet.nl/ then sometimes seems random on ipv6 no https , wen testing same time however with a ipv6 online tester on https no problem.

No errors in log on server however at that DA BOX centos 8 alma latest DA and custombuild.

OYEA sometimes if new cert or config a browser need a kind of reset cookies and co , mostly this is only with ftp programs but sometimes check browser on caching things.

If it is browser that is going wel after there reset and clear al cookie, sessions, cache, then nogood and mayby kind of BUG DA

Thanks for your reply, all my websites went insecure. I have deleted the certificate and reinstalled it using this https://docs.directadmin.com/webser...ypt-tool-to-secure-port-2222-via-the-hostname

The domain names are now showing the padlock again but :2222 is still insecure, I don't know how to fix that because running the commands here should have fixed it but it hasn't
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single `hostname` 4096

I don't know what went wrong as I haven't been working on anything to cause this to happen. The secure connections just vanished and it went insecure.

As of now the websites are now secure again but :2222 DirectAdmin login isn't.

The IPs are IP4 the server is working fine, I have used the following browsers Firefox, Google Chrome and windows and I have the same error with all of them.

 

[tomd]

The website were running fine and have been for ages with letscrpyt securing them then the secure connection just dropped for no reason.

There are no updates for custom build showing in the control panel, license is up to date, nameservers have not changed.

 

[ikkeben]

check if somewhere a ipv6 is set on server in a config, search forum , wiki, help, docs for that

While some noticed problems is ipv6 set on 1 somewhere and not having ipv6 att all

Or if a ipv6 is set in a dns somewhere then to problems if you didn't have it well on server!


UH wen a cert server hostname r is renewed look for that to i don't know where you can in ssh find those files to check!

When nothing changed that is often not true, if done a update sometime somewher , such changes for certs and ssl are often seen later after renewing certs and not before! Even LETSENCRYPT themselves did have changes in things these day's is on their website....

Take care of the other questions above from my first reaction

if Hostname is also used as domain then could be problem , or if vps.exampledomain.com ( that is hostname not domain) and exampledomain.com has no cert itself separate from hostname..