I have successfully issued a certificate using certbot but when I open my website it’s showing me Error 522

Help
1

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. https://crt.sh/?q=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: code.kodnest.com

I ran this command: sudo certbot --apache

It produced this output: Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/code.kodnest.com/fullchain.pem

My web server is (include version): Apache/2.4.29 (Ubuntu),

The operating system my web server runs on is (include version): Ubuntu 18.04

My hosting provider, if applicable, is: Cloudflare

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 0.31.0

I have successfully issued a certificate using certbot but when I open my website it’s showing me Error 522.

1 Like
2

http://code.kodnest.com/ works (serving a redirect to https://code.kodnest.com/).

https://code.kodnest.com/ shows a Cloudflare 522 “Connection timed out” error page.

Maybe your origin server has a firewall blocking (Cloudflare’s) access to port 443?

3 Likes
3

Where can I check the origin server blocking port?

By the way I have created instance in AWS, where in I have added only two type of rules 1. SSH with port 22 and 2. HTTP with port 80, nowhere I have used port 443.

4

Hi @abhi

what's the ip address of your server? Check that ip address directly via "check-your-website", then you see, if port 80 is open.

5

If it's blocking everything else, then you need to add a rule allowing port 443.

6

Ok, will check that.

7

Turns out there was a problem with the port 443, fixed it by adding a rule for port 443.
Thanks for the help.

8

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