Certificate not generated

My domain is: ma-box.freeboxos.fr

Hello,
Through my internet provider “freebox”, I created the domain name: ma-box.freeboxos.fr.
Since one month the certificate is still not active!
Can you check why the certificate is not generated and intervene to remedy the situation
Thank you

Hi @christ2b

there are a lot of certificates ( https://check-your-website.server-daten.de/?q=ma-box.freeboxos.fr#ct-logs ):

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-08-05 2019-11-03 ma-box.freeboxos.fr - 1 entries
Let's Encrypt Authority X3 2019-08-04 2019-11-02 ma-box.freeboxos.fr - 1 entries
Let's Encrypt Authority X3 2019-08-03 2019-11-01 ma-box.freeboxos.fr - 1 entries
Let's Encrypt Authority X3 2019-08-01 2019-10-30 ma-box.freeboxos.fr - 1 entries
Let's Encrypt Authority X3 2019-07-31 2019-10-29 ma-box.freeboxos.fr - 1 entries

But you don't use one of these. Instead, there is a timeout (ipv6) or a wrong certificate:

Domainname Http-Status redirect Sec. G
http://ma-box.freeboxos.fr/
78.208.79.62 200 0.123 H
http://ma-box.freeboxos.fr/
2a01:e34:ed04:f3e0::1 -14 10.033 T
Timeout - The operation has timed out
https://ma-box.freeboxos.fr/
78.208.79.62 200 3.666 N
Certificate error: RemoteCertificateNameMismatch
https://ma-box.freeboxos.fr/
2a01:e34:ed04:f3e0::1 -14 10.030 T
Timeout - The operation has timed out

That's

CN=mon-domaine.eu, OU=PositiveSSL, 
OU=Domain Control Validated
	14.08.2019
	02.05.2020
expires in 241 days	mon-domaine.eu, www.mon-domaine.eu - 2 entries

Is this a home server? So you have to install the certificate?

What's your environment?


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:

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):

Thank you for your response voice additional information:

My domain is: ma-box.freebox.fr

I ran this command: any

It produced this output: any

My web server is (include version): 0

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

My hosting provider, if applicable, is: freebox.fr
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): Yes “freeboxos” provided by my internet provider: free.fr

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): ?

You will understand it is not me but my internet service provider who is applying for a certificate.
I thought the lock was coming from Lets’Encrypt, please tell me if the problem can be solved by me or Lets’Encrypt or if I have to turn to free.fr.
Thank you

Hi @christ2b,

Let’s Encrypt certificates are always generated automatically, by software talking to software, with no humans in the loop. Typically, certificates are generated and valid in just a few seconds.

In this case, it appears that your device is not successfully installing the certificates after obtaining them, so you should probably talk to the people who are responsible for supporting the device (which may be the ISP).

Then you have to ask your internet service provider why the certificate is created, but not installed.

That's a "black box", so only your ISP can find a solution.

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