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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: glpi.hrc-environnement.com
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):
Welcome to the Let's Encrypt Community! 
What seems to be the trouble?
3 Likes
Bonjour .
j'ai un probleme de certification avec le meme nom de domaine si je suis en vpn ou hors vpn .
Lun est valide , et lautre est expiré . pouvez vous m aiguiller ?
1 Like
Je ne parle pas français, j'utilise donc un traducteur.
De mon point de vue, je ne vois pas de certificats multiples servis. Je vois plutôt la chaîne de certificats complète servie, y compris la racine autosignée. Normalement, la racine autosignée n'est pas servie et est supposée exister dans le magasin de confiance du client.
2 Likes
Would you please provide more details? Such as what command or tool are you using to get a certificate?
Currently that domain uses a wildcard certificate from Sectigo not Let's Encrypt.
I see you have many Let's Encrypt certs both wildcard and non-wildcard. You must use a DNS Challenge for the wildcard but the others could use a different method like HTTP Challenge. If using HTTP Challenge there may be problems because your domain redirects HTTP Challenge tests to a different website.
What services does infomaniak provide for you? Are you using one of their tools to get the certificate?
curl -i http://glpi.hrc-environnement.com/.well-known/acme-challenge/Test404
HTTP/1.1 302 Found
date: Thu, 31 Jul 2025 16:43:49 GMT
server: Apache
location: https://ssl-challenges.infomaniak.com/acme-challenge/Test404
The certificate used by that domain right now
echo|openssl s_client -connect glpi.hrc-environnement.com:443 | head -20
0 s:CN = *.hrc-environnement.com
i:C = GB, O = Sectigo Limited, CN = Sectigo Public Server Authentication CA DV R36
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
v:NotBefore: Jul 17 00:00:00 2025 GMT; NotAfter: Aug 17 23:59:59 2026 GMT
3 Likes