Domain Setup Error Message

[alphy]

I have Cloudron installed on my little home server and set up port forwarding (443) on my router. (per blog post here).

I turned on the API key with Namecheap (and whitelisted my IP address), waited for a few hours, but am getting an error on the Domain Setup page.

The error says: getaddrinfo ENOTFOUND api.namecheap.com

I didn't see any posts that seemed to address this exact issue during set up, so thought I would see if anyone had any suggestions.

[nebulon]

Can you ping api.namecheap.com via SSH from your server? Seems like the DNS resolution does not work properly. Also check host api.namecheap.com for this.

[girish]

I would give https://docs.cloudron.io/troubleshooting/#unbound a try as well if the host command is not returning any results.

[alphy]

@nebulon @girish

Here's what I got for the ping/host:
ping: api.namecheap.com: Name or service not known
Host api.namecheap.com not found: 2(SERVFAIL)

For the unbound, I had to set up the forward-everything.conf to get Cloudron to install, so that part is already set.

I checked the status of unbound and this is the result, in case it's useful info:

unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor prese>
Active: active (running) since Thu 2024-01-11 13:05:40 UTC; 1 day 1h ago
Main PID: 934 (unbound)
Tasks: 1 (limit: 34650)
Memory: 9.3M
CPU: 1.123s
CGroup: /system.slice/unbound.service
└─934 /usr/sbin/unbound -d

Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:31 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:32 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:32 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:45:32 cloud-alphy unbound[934]: [934:0] error: read (in tcp s): Conne>
Jan 12 14:48:10 cloud-alphy unbound[934]: [934:0] info: generate keytag query _>
lines 1-20/20 (END)

[girish]

@alphy yeah, it seems the dns resolution is not working on the server because unbound seems to have some trouble. Not sure about your networking setup, but DNS requires UDP port 53 outbound to work.

In forward-everything, have you tried putting in your router's IP / DNS instead of the cloudflare/google DNS ?

[alphy]

@girish

I updated the forward-everything.conf to point to my router and got the same results. unbound status also had the same errors.
I did a ping of api.namecheap.com from my regular desktop, and it seemed to worked normally (maybe not useful info lol).

I then tried pointing the forward-everything.conf to the DNS address listed in my router (the modem from my ISP forwards everything to the router). Using that changed the status results of unbound but the ping to api.namecheap.com still didn't work unfortunately.

Results from forwarding to DNS address listed in router:
alphy@cloud-alphy:~$ ping api.namecheap.com
ping: api.namecheap.com: Name or service not known
alphy@cloud-alphy:~$ systemctl status unbound
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor prese>
Active: active (running) since Fri 2024-01-12 16:34:39 UTC; 27s ago
Main PID: 6907 (unbound)
Tasks: 1 (limit: 34650)
Memory: 7.0M
CPU: 56ms
CGroup: /system.slice/unbound.service
└─6907 /usr/sbin/unbound -d

Jan 12 16:34:39 cloud-alphy systemd[1]: Starting Unbound DNS Resolver...
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 0: subn>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 1: vali>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 2: iter>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] info: start of service (unb>
Jan 12 16:34:39 cloud-alphy systemd[1]: Started Unbound DNS Resolver.
Jan 12 16:34:51 cloud-alphy unbound[6907]: [6907:0] info: generate keytag query

[girish]

@alphy Is there a way for us to access the server? Not sure why unbound is not resolving but that's the root of the problem. If it's possible to access it, please send us info at support@cloudron.io and we can debug further.