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: jbrunette.xyz
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: jbrunette.xyz
Type: dns
Detail: no valid A records found for jbrunette.xyz; no valid AAAA records found for jbrunette.xyz
My web server is (include version): Apache2
The operating system my web server runs on is (include version): Ubuntu 18.04
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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.26.0
I keep getting an error when i try to do certbot --apache for my domain, I just want to know why and how to fix it. Any help would be great and i appreciate it. If you need more info you can ask, though i am still a novice at this kind of thing. I run my domain through cloudflare so that may also be an issue.
You set your DNS records with 192.168.0.11 as the IP address for your server.
That IP address is not on the internet, it's only in your local network. You need to use a public IP address to do serve a website on the internet.
A rule of thumb: if you can't see your website over mobile data, you're not using a public IP (or some firewall is not configured to allow you to serve a website)
Are you expecting your web site to be publicly hosted (so it can be accessed by the general public outside of your network)? If so, how is it hosted and who is your ISP or hosting provider?
You'll probably have to deal with port forwarding on your router because your plan probably only gives you one public IP address (which is, by default, used by your router). The router should have a configuration to allow you to forward ports as seen by the public to ports on devices on your internal network, such as your server. You'll probably need to forward port 443 (HTTPS) and port 80 (HTTP) to your internal server.
You may also want to double-check that your AT&T plan doesn't prevent you from hosting public web services, because some residential ISP plans interfere with that in some way.