How to setup nginx, certbot/dns-cloudflare using docker-compose?

Help
1

Hi everyone. Now, I am trying to setup the nginx web sever with certbot using dns-cloudflare plugin. Is there anyone who can help me how to setup the flow including enroll and renewal of certificates using cron job together with docker-compose setup?

My domain is: example.testlab.com, www.example.testlab.com,

I ran this command:
certbot certonly
--dns-cloudflare
--dns-cloudflare-credentials ~/.secrets/certbot/cloudflare.ini
--dns-cloudflare-propagation-seconds 60
-d example.testlab.com, www.example.testlab.com

It produced this output: I can successfully enroll the certificates, But when I setup the nginx, I faced 520 error but my backend application is running in the background using pm2.

My web server is (include version): nginx/1.18.0 (Ubuntu)

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

My hosting provider, if applicable, is: Namecheap with cloudflare setup

I can login to a root shell on my machine (yes or no, or I don't know): yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 1.21.0

Thank you for assisting us in helping YOU!

2

Hello @MrPhyaeSoneThwim, welcome to the Let's Encrypt community. :slightly_smiling_face:

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:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

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):

Thank you for assisting us in helping YOU!

1 Like
3

You might find nginx documentation and https://forum.nginx.org/ helpful as well.

And the nginx plugin:
https://eff-certbot.readthedocs.io/en/stable/using.html#nginx
And the Cloudflare DNS plugin:
https://certbot-dns-cloudflare.readthedocs.io/en/stable/

1 Like
4

Can you give me the precise solution for that? Otherwise, Would you rather suggest me to ask in nginx forum?

5

Kindly wait to see if there are more knowledgeable Let's Encrypt community volunteers willing to assist.

1 Like
6

It doesn't sound like the certificate is responsible for this. Usually 520 errors are from something else. As you're using certbot with the certonly subcommand, you've installed the certificate manually, so it's also not a nginx configuration problem caused by Certbot.

3 Likes
7

Maybe visit:

3 Likes
8

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