cloudron account not working on web portal

[aestela]

@girish my shh login check: root@Axiom-Techs-Svr:~# systemctl status unbound
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-05-24 18:57:57 UTC; 8min ago
Main PID: 162204 (unbound)
Tasks: 1 (limit: 18648)
Memory: 7.7M
CGroup: /system.slice/unbound.service
└─162204 /usr/sbin/unbound -d

May 24 18:57:57 Axiom-Techs-Svr systemd[1]: Starting Unbound DNS Resolver...
May 24 18:57:57 Axiom-Techs-Svr unbound[162204]: [162204:0] notice: init module 0: subnet
May 24 18:57:57 Axiom-Techs-Svr unbound[162204]: [162204:0] notice: init module 1: validator
May 24 18:57:57 Axiom-Techs-Svr unbound[162204]: [162204:0] notice: init module 2: iterator
May 24 18:57:57 Axiom-Techs-Svr unbound[162204]: [162204:0] info: start of service (unbound 1.9.4).
May 24 18:57:57 Axiom-Techs-Svr systemd[1]: Started Unbound DNS Resolver.

[girish]

@aestela said in cloudron account not working on web portal:

Active: active (running) since Wed 2023-05-24 18:57:57 UTC; 8min ago

This seems to say it is running. Can you refresh the Services UI for sure?

Also, it is UDP port 53 and not TCP 53 (note , this is an outbound port and not inbound port).

[aestela]

Okay I made the corrections you recommeded

[aestela]

I did this as well don't know if the firewall fixed it or the changes to the name server.

If DNS queries are failing with SERVFAIL, then you can try forwarding all DNS requests to other nameservers to see if it fixes the problems. Add the following file /etc/unbound/unbound.conf.d/forward-everything.conf and restart unbound:

forward-zone:
name: "."
forward-addr: 1.1.1.1
forward-addr: 8.8.8.8

[aestela]

[girish]

@aestela So, it's all working now?

[aestela]

Yes, just mentioning I may have needed to do both methods change the outbound firewall rule to allow udp port 53 and change the DNS name server from default unbound to 1.1.1.1 and 8.8.8.8

[scooke]

@aestela Is the screenshot of the ports from the VPS host dashboard, or are you running other software already on the VPS itself?

[inane]

@girish I was having a similar issue, and adding the DNS 1.1.1.1 & 8.8.8.8 in forward-everything.conf file "solved" it.

Question... is this just a temporary solution, or are there problems with leaving it like that permanently?
It's not fully clear to me from how it's worded in the FAQ.

[girish]

@inane It seems on some networks, our internal DNS resolver (unbound) does not work. It's not clear why. Is yours a private network or some public VPS provider ?