View in #help on Slack
@Mahta_Khoobi: Hi, I am trying for hours now to set up the nginx-orthanc-keycloak solution, I have registered a domain with Duck DNS and I want to try it on a private server with constant IP. However, I keep getting connection refusal problems when I want to create a certificate for this domain. I have checked port 80, it is open and there is no firewall issue. Did anyone have a problem like this before? I am grateful for your insights in advance!
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: .duckdns.org
Type: connection
Detail: (IP_Address) : Fetching http://.duckdns.org/.well-known/acme-challenge/cv2IO…: Connection refused*
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
@Alireza_Sedghi: duckDNS sometimes don’t work, it was just for tutorial i guess
you can buy a proper domain if you are at that state
@Mahta_Khoobi: Thanks! I found the problem: my port 80 was not open from the router side, although on my PC (server) it was open. So I used the manual and DNS challenge methods. It has worked pretty well so far 
@Alireza_Sedghi: great to hear, is there any tip that we need to add to our docs?
@Mahta_Khoobi: I just used the manual and DNS challenge instead of the provided command,
docker run -it --rm --name certbot
-v ./config/letsencrypt:/etc/letsencrypt
certbot/certbot certonly
–manual
–preferred-challenges dns
–email your_email@example.com
–agree-tos
–no-eff-email
-d hospital.duckdns.org
Then added the DNS TXT record:
• Logged in to DuckDNS account.
• Add a TXT record with the value provided by Certbot.