Skip to content
This repository has been archived by the owner on Nov 9, 2024. It is now read-only.

Problem with DNS configuration #248

Open
Bruno-Rawan opened this issue Oct 23, 2023 · 6 comments
Open

Problem with DNS configuration #248

Bruno-Rawan opened this issue Oct 23, 2023 · 6 comments
Assignees

Comments

@Bruno-Rawan
Copy link

I have the following error when configuring a DNS

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the li sted domains point to this machine and that it can accept inbound connections fr om the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See t he logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for mo re details.

Screenshot_2

@ZzBombardierzZ
Copy link

Hey, I had the same issue. You need to add a A record for auth.[yourdomain] and wg.[yourdomain]

if you are doing something like: vpn.mydomain.org
you need to add auth.vpn.mydomain.org and wg.vpn.mydomain.org

So you need a total of 3 entries...

@Bruno-Rawan
Copy link
Author

Ei, eu tive o mesmo problema. Você precisa adicionar um registro A para auth.[seudomínio] e wg.[seudomínio]

se você estiver fazendo algo como: vpn.mydomain.org você precisa adicionar auth.vpn.mydomain.org e wg.vpn.mydomain.org

Então você precisa de um total de 3 entradas...

Thank you very much, I will try again!

@tymwitko
Copy link

tymwitko commented Jan 17, 2024

I've got the same issue, but that also includes my base domain (eg. vpn.mydomain.org), so I'm pretty certain the suggested solution won't work.

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:

  Domain: [DOMAIN_NAME].duckdns.org
  Type:   connection
  Detail: [PUBLIC_IP]: Fetching http://[DOMAIN_NAME].duckdns.org/.well-known/acme-challenge/[KEY]: Timeout during connect (likely firewall problem)

And right after that I get the "hint" from the original question

EDIT: I noticed that you have to open ports 80, 443 and 51820 - I did that, and now I can ping the server via its domain name, but only locally - the problem persists

@scooterscott1
Copy link

Came here to say that I am too running into the same issue. I am on Ubuntu 22.04 in an Oracle VPS. I've added 80, 443 and 51820.

@sekhar989
Copy link

Hey, I had the same issue. You need to add a A record for auth.[yourdomain] and wg.[yourdomain]

if you are doing something like: vpn.mydomain.org you need to add auth.vpn.mydomain.org and wg.vpn.mydomain.org

So you need a total of 3 entries...

If someone is using duck DNS, how to configure the sub-domains for wg and auth.

@EdmundDuckDuck
Copy link

@ scooterscott1 commented on Feb 16
Came here to say that I am too running into the same issue. I am on Ubuntu 22.04 in an Oracle VPS. I've added 80, 443 and 51820.

HOW DO IDO THAT?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants