Certbot - connection refused

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: sydneybackgammonclub.org.au

I ran this command: sudo docker compose up -d

It produced this output: Network wordpress1_app-network Created 0.1s
:heavy_check_mark: Network wordpress1_default Created 0.1s
:heavy_check_mark: Container db Started 0.3s
:heavy_check_mark: Container wordpress Started 0.4s
:heavy_check_mark: Container webserver Started 0.6s
:heavy_check_mark: Container certbot Started

My web server is (include version): wordpress:5.1.1-fpm-alpine

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

My hosting provider, if applicable, is:

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 not yet

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

2

Welcome @johnmhedge

You need to be able to reach your site using HTTP from the public internet. That is required by the HTTP Challenge.

You did not show the command and error for Certbot so I am guessing that is what you used. It is the most common and I can reproduce the message in your title using Let's Debug. Check any router or internet connection you have. Check your port assignments in your containers. Looks like you have several containers. It will take some care to get that all communicating properly.

This site will be helpful as you adjust your comms settings

3 Likes
3

Thanks Mike.
I've been trying to set up Multisite Wordpress using Nginx in Docker but keep hitting problems. I was beginning to think there was an issue with my router's port forwarding but I've checked and that's ok.
On to the next issue.
Regards,
John

2 Likes
4

OK Mike I believe I've sorted most of my challenges but one remains; I still can't get a certificate to give me https://www.sydneybackgammonclub.org.au status.
Http works now.
TIA
John

1 Like
5

Not for me. Or, for Let's Debug

Your cube subdomain looks to be working so that's progress.

3 Likes
6

Oh dear!

7

If at first you don't succeed try try again!
Can you give it another try Mike?
Thanks,
John

1 Like
8

You can try for yourself using Let's Debug, which shows all green now: Let's Debug

1 Like
9

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