Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version): Ubuntu 22.04.5
The operating system my web server runs on is (include version): Ubuntu 22.04.5
My hosting provider, if applicable, is: Oracle cloud
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 1.21.0
This command will show you the challenge URL to try from the public internet and the proper response. After showing you this it will say "Press Enter to Continue". DO NOT PRESS ENTER.
Leave it paused like that and use a different device to test connection. You can use a mobile phone with wifi disabled so use your carrier's network.
You do not have to use the full URL. Just try http://(yourdomain)
If the connection works this shorter URL should see a response like below. I am pretty sure you will initially get a similar failure message like Let's Encrypt reported. But, use this technique to modify your comms setup until it works.
It does everything you described, but when I go to the domain name, it doesn't work—it can't find anything, even though the domain name correctly redirects to the IP of my VPS server. This domain is hosted by No-IP.com. I had the same issue on another server before, and I managed to fix it by running the command sudo certbot certonly --standalone -d xxx.servepics.com, but this time it's not working.
Was there anything listening on port 80 when you tried that? Does this show anything
sudo ss -pant | grep :80 | grep -i listen
I see your command prompt says "pterodactyl". Are you planning on running an nginx server once it is setup? Because --standalone is a poor choice if that is your plan
Yes, I want to run an Nginx server, but I had to use that because Nginx crashes since it doesn't have a certificate, so I can't generate it through Nginx. I had already set up a site using standalone, and it worked, which is why I'm using it again.
If nothing is listening on port 80 your curl to that port will always fail.
If you keep --standalone running at least something will be listening
nginx can run without a cert. You just set up a server block with only HTTP support (for port 80). You could also create a self-signed cert and setup nginx server block for HTTPS with that. You might even have some in your Ubuntu system already in /etc/ssl (look for snakeoil and see Ubuntu docs). These are just basic nginx config techniques. How you do that in pterodactyl is probably better asked at their support forum.
That's not really a good reason. Once you've managed to get a certificate issued, that cert will be submitted to a few certificate transparancy logs and these logs are monitored by all kinds of people: benign people doing good stuff and malign people trying to abuse newly installed instances. E.g., some webapps got free certs during their onboarding process while a default password was still configured. Thus, script kiddies monitoring CT logs could easily "hack" these newly onboarded webapps using these default passwords.
Thus, once your cert is issued, expect portscans, scripted "hack" attempts and what not so. Therefore, you should NOT rely on this "security by obscurity" as it's dubious at best and plainly unsafe to begin with at worst.
The only difference between -A and -I is the position of the added rule.. "A" for "append" at the bottom of the chain and "I" for "insert" where you can specify a rule number, which defaults to "1", which is the top of the chain.
Please make sure you read up on how iptables works and make sure you've got your chain(s) in order. Figuratively and literally.
Example Domain
This domain is for use in illustrative examples in documents. You may use this domain in literature without prior coordination or asking for permission.
