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.
My domain is: mrpinoy.cf
I ran this command: sudo certbot --nginx -d mrpinoy.cf -d www.mrpinoy.cf
It produced this output:
aving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for mrpinoy.cf and www.mrpinoy.cf
Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.
My web server is (include version): Nginx
The operating system my web server runs on is (include version): macOS Catalina 10.15.7
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):
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
Your title asks to help verify your DNS and access to your server.
Your DNS points to an IP 184.108.40.206. There is no way for us to know if that is correct but you can confirm this yourself. A command of curl ifconfig.co from your server will return your IP. Many other ways to confirm but this is easy way.
Just fyi, EC2 can have a public IP address without needing it to be an Elastic IP. But, agreed the Security Group may need adjusting. I see how you got that from the IP. Was not clear from the posts AWS was involved at all.
I cannot reach your nginx server using that IP address. If you are still on AWS you should review your Security Groups.
Note: That was not the IP you had in DNS at first. You should know that if you are not using an Elastic IP with EC2 that each time you stop and start the EC2 Instance you will get assigned a new IP and you must update the DNS. I do not know this is why you have a new IP - I am just noting it.