Certificate not validating

[kash1]

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: kmqenterprisesllc.com

I ran this command:sudo certbot --apache

It produced this output:
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: kmqenterprisesllc.com
Type: unauthorized
Detail: 104.189.116.103: Invalid response from http://kmqenterprisesllc.com/.well-known/acme-challenge/gRaOIr4Th9fofqgaSIbOjL-kHXQHJdewgMj-SbB9LyY: 404

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

My web server is (include version): Chrome is up to date
Version 132.0.6834.111 (Official Build) (64-bit)

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

My hosting provider, if applicable, is:Ubuntu 22.04

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

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

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: kmqenterprisesllc.com
Type: unauthorized
Detail: (PUBLIC IP ADDRESS REMOVED: Invalid response from http://kmqenterprisesllc.com/.well-known/acme-challenge/CgNP3ePxWS3T93q7J7wudHB0d4eiziaRkYZZHD7mQfQ: 404

[MikeMcQ]

Welcome @kash1

Make sure HTTP requests of the form shown in the error message actually reach your Apache server. Because HTTP requests to your "home" page get a login page for MyCloud.

Based on a test HTTP request, I think your MyCloud may be replying to the Let's Encrypt HTTP challenge rather than your Apache. Usually we see a "Server: Apache" response header. It is not required but is very common. In any case, if the Let's Encrypt HTTP request was getting to your Apache properly you wouldn't get a 404 error.

curl -i http://kmqenterprisesllc.com/.well-known/acme-challenge/Test404
HTTP/1.1 404 Not Found
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1
Date: Sat, 25 Jan 2025 16:10:54 GMT
X-Frame-Options: sameorigin

HTTP to your "home" page shows

[kash1]

Thank you I'm configuring with your guidance now.