I'm not arguing about what that file contains or not.
What I've said, and the test show, is that the system is NOT serving a trusted chain.
This is all of what I get directly from it:
we are using IIS 10.0 and have to support old Android devices, so it is important that our server provides both paths, including the "New Default Chain" with IdenTrust DST Root CA X3.
Sadly, the IIS removes the path including the expired IdentTrust Certificate.
The Workaround we found was putting the "ISGR Root X1" in the Untrusted Store of the Windows Certificate Manager as described here and reboot the server.
Is there a better way to do this? This way we are unable to renew the certificates using win-acme.
It is astounding, but explains perfectly what happens. Please, can you tell me how you have obtained that response (two certificates, second being probably the obsolete R3)?
Hello, we are using centos 7. I updated the ca-certificates package and checked to make sure it's removed trust list | grep -C3 'DST Root CA X3', however, I'm still seeing the root certificate listed when I check our sites:
when an embedded certificate expires, if the device isn't getting updated, that's that. check the expiration date of the embedded root certificate on the older system you want to support, and the browser is probably deriving it's trusted root from the operating system.
exception: firefox, but firefox accepts expired trusted root certs, unlike chrome, so there's that.
we're using HAProxy 2.4.4 and seeing some older macs and ubuntu 15 seeing cert expired messages when they go to docucopies.com is there a config change I can make in haproxy that will fix that?
Hi @deckberg-qd, welcome to the LE community forum
That site is using the exact same trust path (chain) that this forum is using.
You have only three choices:
upgrade the clients to work with this trust path (chain)
[may not even be possible now, or ever (for some no-longer-supported clients)]
modify all the servers to use a different trust path (chain)
this isn't very likely; as you can't possibly control the very large number of systems on the Internet that are using this same trust path (chain)
put all your troubled clients behind a proxy (one that terminates the TLS connections
that may keep those clients within your trust path (chain) control; as they would only see the proxy
for your 2nd bullet. am I thinking correct that I can update certbot to 1.12 and put in the correct whatever for --preferred-chain ?
sorry, I'm not trying to make the clients work everywhere on the net, I just want my older customers to be able to get to my website docucopies.com without the expired cert warning
Your server is already sending the cross-signed cert. It's #3 in the second section in your screenshot. That's part of the "default" chain Let's Encrypt sends to your ACME client.
The --preferred-chain option you alluded to would be the way to get the "alternate" chain that removes that cross-signed cert and also then breaks compatibility with old Android devices. Whether that is an improvement for your overall userbase, only you can determine.
so there's nothing I can do server side to have those older clients be able to connect? it's simply up to the client to update their trust store if they are able?
If those older clients do not trust the ISRG Root X1 cert, the only thing you can do server side is change to a different Certificate Authority that they do trust. Personally, I would try switching to the shorter chain first and seeing how those clients respond. But again, that will definitely break old Android devices.
I can Confirm a fix that worked on both a 10.9.5 & 10.11.6 Mac OS users. Simply set the DST Root CA X3 to "Always Trust" on several Mac's I manage in an office and home's this fix work for 4 websites that previously had issues with this CERT ERR.
This expiry of DST Root caused me to really look at and understand my own setup And thank you all for helping each other here!
I had two issues:
I had to remove the DST Root from my system store on the server because openssl s_client kept failing my tests.
The existing fullchain.pem files still had the DST Root CA X3 certificate in them which caused my webserver to continue to send it, causing failures on some clients. The solution was to force a renewal of the certificate.
I'm not using the apache installer and authenticator, but instead use the webroot athenticator as I found it better when using a mix of services:
# certbot --webroot --dry-run -w /var/www/domains/wiki.tnonline.net/htdocs -d wiki.tnonline.net -v certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Certificate not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/wiki.tnonline.net.conf)
What would you like to do?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Keep the existing certificate for now
2: Renew & replace the certificate (may be subject to CA rate limits)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):
I found that certtool from the GnuTLS package is better to look at the full chain than with openssl:
]
