Can't get certbot to work successfully

I can’t see why this is failing…
Let’s try --webroot method.
Since we still have that Alias for /.well-known/acme-challenge/, we really don’t need to be accurate about the actual webroot used.

Try this test:
certbot certonly --webroot -w /var/www/html -d voidcitymc.com --staging

Exactly the same error as before

Is there anything meaningful in the error.log file?
/var/log/apache2/error.log

[Wed Nov 06 01:33:09.168638 2019] [mpm_prefork:not$[Wed Nov 06 01:33:09.168769 2019] [core:notice] [p$[Wed Nov 06 01:39:15.943672 2019] [mpm_prefork:not$AH00558: apache2: Could not reliably determine the$[Wed Nov 06 01:39:16.301235 2019] [mpm_prefork:not$[Wed Nov 06 01:39:16.301351 2019] [core:notice] [p$[Wed Nov 06 01:39:23.235478 2019] [mpm_prefork:not$AH00558: apache2: Could not reliably determine the$[Wed Nov 06 01:39:23.571129 2019] [mpm_prefork:not$[Wed Nov 06 01:39:23.571231 2019] [core:notice] [p$

OK lets add back (if you removed them) the long path:
mkdir /ACME-challenges/.well-known/
mkdir /ACME-challenges/.well-known/acme-challenge/

and try:
certbot certonly --webroot -w /ACME-challenges/ -d voidcitymc.com --staging

Same error as before

OK rem out, or delete, the Alias line added to the /etc/apache2/apache2.conf file.
restart apache
try again:
certbot certonly --webroot -w /ACME-challenges/ -d voidcitymc.com --staging

Again it’s same error as before

Do you think the issue is with my domain names nameservers?

OMG! IMPOSSIBLE!

No.
Our test-file worked!

OK WE USE A BIGGER HAMMER!

We go --standalone

Not sure at this point

It’s a 3 step process (that can be integrated into a single statement - but we’ll do that part later).

Step 1. stop Apache
systemctl stop apache2

Step 2. get cert using temporary certbot webserver
certbot certonly --standalone -d voidcitymc.com --staging

Step 3. restart Apache
systemctl start apache2

I got the certificate:)

ABOUT TIME!
The downside is webservice stops during that minute (once every 60 days)

Now let’s get a real cert and roll that up into one line and ensure renewals are good to go…

Can I use cron for renewals?

certbot will handle all that (cron/system) for us

Good, when I visit https://voidcitymc.com it doesn’t seem to work though

we haven’t installed the cert yet - hold on
plus that was a staging cert - not valid in the real world

Ah the —staging argument

Next step: Roll those 3 steps into one (real) step:

certbot certonly --standalone -d voidcitymc.com --pre-hook "systemctl stop apache2" --post-hook "systemctl start apache2"