Trying to add SSL via Certbot

Help
1

My domain is: https://v3-api.bloxpvp.com

I ran this command: sudo certbot --nginx -d v3-api.bloxpvp.com

It produced this output: Requesting a certificate for v3-api.bloxpvp.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: v3-api.bloxpvp.com
Type: unauthorized
Detail: 2606:4700:20::681a:9b1: Invalid response from http://v3-api.bloxpvp.com/.well-known/acme-challenge/ay8RJBklVJMDJXaqPGmM0r_MT0_1N3zIP939oIDEuRo: 522

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 version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

The 522 is an error the Cloudflare CDN Edge (proxying your domain) gets when trying to reach your Origin Server. See below for their debug instructions

Do you even need a Let's Encrypt cert on your origin? Could you instead use the Cloudflare Origin CA cert?

Cloudflare also has an active community: https://community.cloudflare.com/

2 Likes
3

yeah i want to use Let's Encrypt, my server is up @ http://5.42.102.187/ but it's still not working when i try to add the certificate

4

I am not sure what else to say. I still see that the Cloudflare edge fails to reach your Origin Server and issues a 522 error. Have you followed its debug procedure here: Troubleshooting Cloudflare 5XX errors | Cloudflare Support docs

I can reach your IP address and see an nginx/1.24.0 Ubuntu server. But, is that the correct IP you have in your Cloudflare DNS panel? That is one of several items the above Troubleshooting page suggests.

I cannot reach your Origin Server using your domain name which goes through Cloudflare's proxy CDN

You really need to visit the Cloudflare community for help. This is a network or Cloudflare configuration issue.

image
image1563×423 104 KB

2 Likes
6

You won't be able to use an LE cert to secure an IP.
This won't work: https://5.42.102.187/

Also, port 443 is not open:

curl -Ii https://5.42.102.187/
curl: (7) Failed to connect to 5.42.102.187 port 443 after 125 ms: Connection refused
2 Likes
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.