Cert expired, connection issue

Hi, inexperienced with this (but learning:roll_eyes:). We have lost connectivity to out web site/s, due it seems to a certificate not auto renewing. I note the lines in the output of certbot in terminal about firewall but no changes have been made by me/us here. Obviously something has changed, port 443 is pointing to .50. I need help on where to start looking to fix/remove the issue creating the certbot output. Please could someone direct me any which way… log files? config files to check etc… Thanks in advance…

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: bodekerscientific.com

I ran this command: sudo certbot --nginx

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org

Which names would you like to activate HTTPS for?

1: confluence.bodekerscientific.com
2: jira.bodekerscientific.com
3: jira-webapps.bodekerscientific.com
4: rdc.bodekerscientific.com
5: svn.bodekerscientific.com

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel):

You have an existing certificate that contains a portion of the domains you
requested (ref: /etc/letsencrypt/renewal/confluence.bodekerscientific.com.conf)

It contains these names: confluence.bodekerscientific.com

You requested these names for the new certificate:
confluence.bodekerscientific.com, jira.bodekerscientific.com,
jira-webapps.bodekerscientific.com, rdc.bodekerscientific.com,

Do you want to expand and replace this existing certificate with the new

(E)xpand/©ancel: E
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for confluence.bodekerscientific.com
http-01 challenge for jira-webapps.bodekerscientific.com
http-01 challenge for jira.bodekerscientific.com
http-01 challenge for rdc.bodekerscientific.com
http-01 challenge for svn.bodekerscientific.com
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. rdc.bodekerscientific.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://rdc.bodekerscientific.com/.well-known/acme-challenge/T9H4ZFNzQCwut9pCIyMTrk5f7LEu7KxEdL7kRC7qCBw: Timeout during connect (likely firewall problem), confluence.bodekerscientific.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://confluence.bodekerscientific.com/.well-known/acme-challenge/tikrmlVANiKdI6rq3Zm4j9Np63pqtkQHhdQxtm4jV_Y: Timeout during connect (likely firewall problem), jira-webapps.bodekerscientific.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://jira-webapps.bodekerscientific.com/.well-known/acme-challenge/uff9w6Jt-apP_tYHJC9R0BGZDAqLjKugf25jUuXdx50: Timeout during connect (likely firewall problem), jira.bodekerscientific.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://jira.bodekerscientific.com/.well-known/acme-challenge/egg_XOxMcbbaYYu5lhjtr7DrsF3rzwkr0og2cL56OB8: Timeout during connect (likely firewall problem), svn.bodekerscientific.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://svn.bodekerscientific.com/.well-known/acme-challenge/VUEiw33QVyafJ_6ZW9RXRlv54ukEG5OaoczFADmiwZI: Timeout during connect (likely firewall problem)

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version): not sure
On the machine throwing the certbot output: nginx version: nginx/1.10.3 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu svr 16 lts

My hosting provider, if applicable, is: eNom

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

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

You need to open port 80 over the internet, whereas currently you just have port 443 open.

That’s the port over which the Let’s Encrypt HTTP validation process occurs.

Thanks for the fast reply, now where would I do that? On our modem/router? or…

Only you can answer that question, but yes, if you're using port forwarding/NAT, then you'll need to do that.

If you have any other firewalls, they need to be updated too.

You need to do the same for port 80.


Thanks so much _az, active now with tcp/udp 80=>.50:80. Certs renewed, jira and confluence back up.
I inherited this system with very limited info and assumed that this was an automatic renewal process. The modem may not have been in that long and so that port forward may not have been setup. Appreciate your help with this. Thanks again…


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