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.
The operating system my web server runs on is (include version):
NAME="Amazon Linux"
VERSION="2023"
My hosting provider, if applicable, is:
amazon ec2
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):
No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 2.6.0
I had issues before, I think it is likely my problem relates to the set up of my ssl.conf for httpd.conf files. I am an amateur web developer, so any help is appreciated. Much thanks!
Close but more likely related to config of the VirtualHost handling port 80. An HTTP request from the Let's Encrypt server on port 80 isn't seeing the expected challenge token. That token is placed by Certbot in the webroot folder you used earlier. The "404" in the error message is an HTTP Not Found error.
A good place to start is showing us output of this
sudo apache2ctl -t -D DUMP_VHOSTS
You may need to use httpd instead of apache2ctl in the above command. I don't remember what AL2023 uses.
Hi mike, thanks a lot for your response. Here's what running the code gave me:
VirtualHost configuration:
*:80 is a NameVirtualHost
default server api.lumo-edu.com (/etc/httpd/conf/httpd.conf:32)
port 80 namevhost api.lumo-edu.com (/etc/httpd/conf/httpd.conf:32)
port 80 namevhost api.lumo-edu.com (/etc/httpd/conf.d/api.lumo-edu.com.conf:1)
*:443 api.lumo-edu.com (/etc/httpd/conf.d/ssl.conf:54)
Let me know if this gives you any insight- and thanks once more for your help
You have the same name and port defined twice. While Apache will startup with this it won't give consistent results.
I can make a good guess as to what you should do but it would be better for you to post the contents of both files. Use 3 backticks before and after so not to lose Apache tags to forum formatting. Like
```
config
```
I am going to have to leave you to another volunteer. I have a feeling this is going to take awhile to get you sorted out. I don't have that much time this afternoon for that. Maybe later today.
You could just delete that file in your conf.d folder. That VirtualHost isn't doing anything. That will at least fix the duplication problem.