Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for etherealplayground.com
Waiting for verification...
Challenge failed for domain etherealplayground.com
http-01 challenge for etherealplayground.com
Cleaning up challenges
Some challenges have failed.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
I was able to connect to the websites earlier from my pc that is not the server and it would see the website from the pc, and this was working the first time I talked to you.
Now after a reinstallation of my webpanel I had a problem with hostname and had to change postfixes to the hostname instead of an ip and am thinking of reinstalling the entire server for a fresh install, I posted above what im getting now.
when i changed the dns a record from 10.0.0.228 into the public ipv4 address this is when i could no longer see etherealplayground.com however other things started to work.
Yes it is connected to the same modem and i could not test it outside of that area. etherealplayground.com is the domain. What actually threw it off is i set my web panel to use ssl and it started forcing https and then i couldnt see them anymore but the certbot was working better otherwise i can see etherealplayground.com when no ssl is checked in settings of my control panel.
So, you're not going to be able to get a certificate via the method you're using until you can figure out and resolve the problem that prevents people from the Internet from connecting to your server.
Based on the errors that we're seeing, the problem is not with your Certbot command, nor with EHCP, nor with your Apache configuration. It's more likely to be with your home router configuration or Comcast not allowing you to receive incoming connections, or both, and the problem doesn't seem to be exactly the same between IPv4 and IPv6. You'll need to be able to successfully receive some kind of incoming HTTP connection on port 80 from outside of your own network before you can usefully begin to request your certificate.
@layz1307 As you make changes test for the comms problems you should either use the Certbot staging option or better yet the Let's Debug test site. If you keep trying and failing with the Let's Encrypt production system you may get temporarily blocked.