Help to get my new certificate

[Hossam.elsawy]

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. crt.sh | 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: rawasi.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):

[Bruce5051]

Hello @Hossam.elsawy, welcome to the Let's Encrypt community.

My web server is (include version): looks like Caddy for HTTP; Framer/5595161 for HTTPS.

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

Here is a partial list of ACME Client Implementations - Let's Encrypt, what ACME client are you using?

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

Thank you for assisting us in helping YOU!

$ curl -Ii http://rawasi.com/.well-known/acme-challenge/sometestfile
HTTP/1.1 301 Moved Permanently
Location: https://rawasi.com/.well-known/acme-challenge/sometestfile
Server: Caddy
Date: Mon, 03 Jun 2024 02:20:03 GMT

There looks like there is a redirect loop from HTTPS to HTTPS

$ curl -k -Ii https://rawasi.com/.well-known/acme-challenge/sometestfile
HTTP/2 308
alt-svc: h3=":443"; ma=2592000
cache-control: public, max-age=0, must-revalidate
content-type: text/html; charset=utf-8
date: Mon, 03 Jun 2024 02:20:20 GMT
location: https://www.rawasi.com/.well-known/acme-challenge/sometestfile
server: Framer/5595161
strict-transport-security: max-age=31536000

$ curl -k -Ii https://www.rawasi.com/.well-known/acme-challenge/sometestfile
HTTP/2 404
alt-svc: h3=":443"; ma=2592000
content-type: text/html; charset=utf-8
date: Mon, 03 Jun 2024 02:23:12 GMT
server: Framer/5595161
strict-transport-security: max-age=31536000

[MikeMcQ]

Can you explain more about what you want help with?

Because HTTPS to rawasi.com and its www subdomain both connect correctly using a Let's Encrypt certificate.

Your domain looks to be hosted on a website service called "Framer".

You didn't answer any of the questions so I am guessing you don't know any of those answers. I would also guess the Framer system got your cert for you. Does that sound right? If so, you should talk with Framer support.

[mholt]

Framer is a Caddy sponsor. I am in contact with their team almost daily (at least weekly) as they roll out their Caddy integration globally.

Because Framer uses Caddy, if you are using Framer, your certificate is taken care of for you. I believe that's the case. I don't represent or speak for Framer.

It's too bad there's no information in your topic to help you though.

[Bruce5051]

Here is what I see for issued certificates, several on 2024-06-03.