Using Certbot Docker to mount letsencrypt doesn't work due to symlinks maybe

Help
1

nginx.conf.txt (916 Bytes)
Dockerfile.txt (693 Bytes)
Install-Certbot.txt (409 Bytes)
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. crt.sh | 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: https://fiscaltimeline.com/
Files can be accessed: GitHub - mrunal-modi/certbot

Makefile.txt (2.6 KB)

2

Hello @mrunal-modi, 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. crt.sh | 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

Hi @mrunal-modi,

It also seems that Ports 80 & 443 are filtered

$ nmap -Pn -p80,443 fiscaltimeline.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-12-15 03:25 UTC
Nmap scan report for fiscaltimeline.com (3.25.246.4)
Host is up.
rDNS record for 3.25.246.4: ec2-3-25-246-4.ap-southeast-2.compute.amazonaws.com

PORT    STATE    SERVICE
80/tcp  filtered http
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 3.29 seconds

And using the online tool Let's Debug yields these results https://letsdebug.net/fiscaltimeline.com/1737643

ANotWorking
ERROR
fiscaltimeline.com has an A (IPv4) record (3.25.246.4) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
A timeout was experienced while communicating with fiscaltimeline.com/3.25.246.4: Get "http://fiscaltimeline.com/.well-known/acme-challenge/letsdebug-test": context deadline exceeded

Trace:
@0ms: Making a request to http://fiscaltimeline.com/.well-known/acme-challenge/letsdebug-test (using initial IP 3.25.246.4)
@0ms: Dialing 3.25.246.4
@10001ms: Experienced error: context deadline exceeded

IssueFromLetsEncrypt
ERROR
A test authorization for fiscaltimeline.com to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
3.25.246.4: Fetching http://fiscaltimeline.com/.well-known/acme-challenge/9tKWj5i_7LZHm5mV2hQWbbdQIOXZmdDip-dPPUKv0SA: Timeout during connect (likely firewall problem)
1 Like
4

I tried too many time and now have been supended for 24 hours. Shall bring it online on 80 again tomorrow. Meanwhile, any issues with my setup to test? Makefile , Dockerfile ?

5

Testing and debugging are best done using the Staging Environment.
See Rate Limits - Let's Encrypt and Failed Validation Limit - Let's Encrypt

2 Likes
6

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