All Apps Error Status After Update to 8.0.3

[joseph]

@playsia ok, so back to DNS resolution error ? Can you check what is in your /etc/resolv.conf ?

[playsia]

GNU nano 6.2 /etc/resolv.conf

<snip comment prelude>

nameserver 127.0.0.53
options edns0 trust-ad
search .

[joseph]

@playsia ok, that looks correct.

Now, systemctl status systemd-resolved should say running. Finally, resolvectl should show some nameservers. I suspect resolvectl is not showing any nameservers. In that case, edit /etc/systemd/resolved.conf and edit the DNS line like so:

DNS=8.8.8.8 1.1.1.1

Put your own network's nameservers above, if you have them. Otherwise, 8.8.8.8 is google and 1.1.1.1 is cloudflare dns. systemctl restart systemd-resolved . After this dns will work. resolvectl will also show the DNS servers you added.

[playsia]

systemctl status systemd-resolved: yes it's running

Results of resolvectl:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp1s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.5
DNS Servers: 192.168.0.5 192.168.0.6

Link 3 (wlp2s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (docker0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (br-60558136c824)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 7 (veth14a60e8)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 9 (veth781f0fd)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 11 (veth6430967)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 13 (veth1baaf71)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 15 (vethf12b789)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 17 (veth41c82ea)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 19 (veth23598f8)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 21 (veth279bdec)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 23 (veth6e84b1b)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 25 (veth305c936)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

[playsia]

resolvectl after changing /etc/systemd/resolved.conf. Only change is Global.

Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Current DNS Server: 192.168.0.5
DNS Servers: 192.168.0.5 192.168.0.6

Log:
box:tasks startTask: 7791 done. error: { stack: 'BoxError: Network error downloading icon : \n' + ' at /home/yellowtent/box/src/appstore.js:493:33\n' + ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' + ' at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)\n' + ' at async Object.downloadIcon (/home/yellowtent/box/src/appstore.js:487:12)\n' + ' at async downloadIcon (/home/yellowtent/box/src/apptask.js:208:26)\n' + ' at async configure (/home/yellowtent/box/src/apptask.js:564:5)', name: 'BoxError', reason: 'Network Error', details: {}, message: 'Network error downloading icon : ' }

[joseph]

So your DNS servers are 192.168.0.5 and 192.168.0.6 ? I am not able to work out why it still cannot resolve. If you can email support@ , we can take a look.

[micmc]

@joseph said in All Apps Error Status After Update to 8.0.3:

So your DNS servers are 192.168.0.5 and 192.168.0.6 ? I am not able to work out why it still cannot resolve. If you can email support@ , we can take a look.

These are local network IP addresses, very likely the local DNSs from his router.

[playsia]

They are my two piholes. I will reinstall with DNS=8.8.8.8 1.1.1.1 but I doubt this is the issue.

[necrevistonnezr]

They absolutely can be the issue depending on their configuration and filter lists(!)

[playsia]

1.1.1.1 and 8.8.8.8 did the trick.

... because my pihole wasn't able to do ipv6 dns resolution? which must have become a requirement from 7.7.2 to 8.0.3? As mentioned earlier I don't have any internet ipv6 connectivity so I'm not entirely sure how this is happening... but I'm not changing anything now that things are working.

For people finding the same issue the solution I did was to fresh install ubuntu server, set static IP and dns to 1.1.1.1 and 8.8.8.8, I then restored cloudron as normal.

[justin.poppi]

For anyone else out there that is having trouble, I was able to fix this issue by disabling ipv6 within ubuntu.

First I did the curl test as mentioned by @nebulon - it worked as expected, but when adding the --ipv6 option it failed.

When running "ip a" I could see an ipv6 address was present.

Using the link that @playsia supplied, I carried out the steps described in section 1: Disable IPv6 using Sysctl. I didn't need to modify the /etc/rc.local file.

Running "ip a" again, there was no more ipv6 addresses shown.

I only had these issues after upgrading to V8.0.3 and Ubuntu 24.04.1.