Requesting a certificate for my domain

[Tiswhord]

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: meet.xolanibridge.com

I ran this command: sudo certbot certonly --standalone -d meet.xolanibridge.com

It produced this output: ertbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: meet.xolanibridge.com
Type: unauthorized
Detail: 162.213.251.237: Invalid response from https://meet.xolanibridge.com/.well-known/acme-challenge/v3C48kO-NqoGLMasteuU9DYwirYp2BkRUlnSsWrJKCE: 404

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

My web server is (include version): Ubuntu

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

My hosting provider, if applicable, is:

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

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

[MikeMcQ]

Welcome @Tiswhord

Are you running Certbot on the machine with the public IP for that domain? If so, did you stop the LiteSpeed server before using Certbot --standalone ?

Because right now I see a LiteSpeed server replying to HTTP requests and it redirects HTTP requests to HTTPS

Did you see an error about port 80 already being in use when you tried to use the --standalone option? Because it requires exclusive use of port 80. The standalone temp server also would not redirect the HTTP request to HTTPS. Notice in the error message it shows an HTTPS URL failing which means the Let's Encrypt server request was redirected. This indicates the standalone temp server was not processing the HTTP request.