Certbot failed to authenticate some domains (authenticator: apache). Please Help

Help
22

OK, good to know. I guess @mr1assou should try what you linked above then.

1 Like
23

Yeah, it's fairly easy to identify. If you see multiple IP for GoDaddy DNS, do a reverse IP lookup. If you see AwsGlobalAccelerator for any IP that is the marker.

I think all the cases of only two IP and both AwsGlobalAcclerator were people with Domain Forwarding enabled who had to disable that before adding their own A record. These cases go back a long time.

I think all of the cases with 3 IP and only two show as AwsGlobalAccelerator have been due to residual Parking setup. These have started only more recently.

The thread I linked to described both of the above and has helped several others.

3 Likes
25

but when i select my domain then i go to forward, the option of remove forwarding doesn't appear ,i'm new in go daddy i buy the domain 4 days ago and i add the dns records to point my domain to ip address of my server and that's it.

26

What about the Parking issue described here at the link I provided earlier?

2 Likes
28

dns
dns1184×284 15.7 KB

i fix the problem the certbot can reach the domains but i get this error

29

That is good progress. That error means something about your Apache config is not what Certbot understands.

Would you show output of this?

sudo apache2ctl -t -D DUMP_VHOSTS

It is easier for us if you copy/paste the screen output text rather than pasting image capture.

2 Likes
31

output:*:80 gym-manager.com (/etc/apache2/sites-enabled/gym-manager.com.conf:1)

32

Can you show output of this?

ls -lR /etc/apache2/{sites-available,sites-enabled}
2 Likes
33

output:
/etc/apache2/sites-available:
total 16
-rw-r--r-- 1 root root 1332 Dec 4 2023 000-default.conf
-rw-r--r-- 1 root root 6339 Jul 27 18:13 default-ssl.conf
-rwxrwxrwx 1 root root 327 Jul 26 21:19 gym-manager.com.conf

/etc/apache2/sites-enabled:
total 0
lrwxrwxrwx 1 root root 39 Jul 26 05:15 gym-manager.com.conf -> ../sites-available/gym-manager.com.conf

1 Like
34

Thanks. Can you show contents of below file? So far that all looks very normal. But, there must be something odd

/etc/apache2/sites-available/gym-manager.com.conf
2 Likes
35 
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName gym-manager.com
    ServerAlias www.gym-manager.com
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
36

Mike i want to see thank you hhhhh i appreciate your help look at this message it works for me:

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Deploying certificate
Successfully deployed certificate for gym-manager.com to /etc/apache2/sites-available/gym-manager.com-le-ssl.conf
Successfully deployed certificate for www.gym-manager.com to /etc/apache2/sites-available/gym-manager.com-le-ssl.conf
Congratulations! You have successfully enabled HTTPS on https://gym-manager.com and https://www.gym-manager.com

If you like Certbot, please consider supporting our work by:

1 Like
37

https://gym-manager.com/ you can access to my website via https can you tell me how can i renew the certificate for free?

1 Like
38

A site like https://ssllabs.com is good for testing your server and its HTTPS configuration. Your apex domain and its www subdomain both look good.

You can test the renewal process using this command. It will not affect your current production certs. The --dry-run is only a test.

sudo certbot renew --dry-run

For Ubuntu, you would be better off using the Certbot snap install rather than the apt version you are using. The current version of Certbot is 2.11 so you can see the apt version you have is much older already. The snap install will automatically keep Certbot updated.

Installing from snap will also ensure the certbot renew is run automatically.

Carefully follow the instructions here. The Ubuntu 20 instructions work for Ubuntu 22

2 Likes
39

I closed your other thread with the failing certbot-auto and asking about auto-renew

Did you follow my instructions to install the snap version of Certbot?

what does this say?

sudo certbot --version
1 Like
41

i follow the instruction and i configure it correctly thank you MIKE for your time,i don't know is this command sudo certbot renew --dry-run enough to do auto renewl certificate because i follow old tutorials in YT

42

Those are very old tutorials and you should not rely on them if they suggest certbot-auto

The --dry-run command is a way to test the certbot renew. Did that work?

Once we prove that works we can make sure that this command is scheduled to run regularly. The snap install of Certbot I suggested will ensure that. Otherwise review the Certbot docs. I think you would be best to install the snap version of certbot anyway. This would help a lot.

What does this command show: sudo certbot --version

1 Like
44

root@gym-droplet-1:~# sudo certbot --version
certbot 2.11.0
root@gym-droplet-1:~# certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/gym-manager.com.conf

Certificate not yet due for renewal

The following certificates are not due for renewal yet:
/etc/letsencrypt/live/gym-manager.com/fullchain.pem expires on 2024-10-25 (skipped)
No renewals were attempted.

45

there is any problem?

46

What about ?

sudo certbot renew --dry-run

Right now the actual renew shouldn't do anything and it did not. It only needs to renew the cert once it is within 30 days of expiration.

The --dry-run will use the Let's Encrypt staging system to get a test cert but will not affect your existing production certs.

2 Likes