Can't login for the Apps Page

[MeeksFamily06]

I did check and I can log out and back in, so the issue seems to be between the server and cloudrons servers. I did notice when I look at the console and then click on the apps tab, it says "Failed to get apps. Will retry. " in the console

[MeeksFamily06]

With the new information, I did some searching and decided to try host api.cloudron.io and it responded with

;; connection timed out; no servers could be reached

Then I tried host api.cloudron.io 8.8.8.8 and it responded with

Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

api.cloudron.io has address 3.209.21.239

[girish]

@meeksfamily06 Ah, this can happen if unbound is not running/working. Can you please check systemctl status unbound ?

[MeeksFamily06]

It says

[girish]

@meeksfamily06 that seems good. Is your server on linode by any chance? We already got 2-3 reports here that DNS resolution fails on linode for some reason via unbound. The "workaround" is to snapshot the server and create a new server from the snapshot (to get a different IP). There is some issue on the linode side, I think we have to investigate a bit more and report to them.

[girish]

@meeksfamily06 If the server is on linode... if the snapshotting does not solve it, do you think you can give us access to the server? I would like to debug it further to find the root cause.

[MeeksFamily06]

I sent you a private message

[MeeksFamily06]

I'm guessing you guys did something because it seems to be working again

[girish]

@meeksfamily06 Interesting, we didn't actually do anything. Please let us know if you hit this again.

[MeeksFamily06]

Figured I would add an update. I did figure out what was causing the issue.

If I ran the command

systemctl status systemd-resolved.service

It said it was Active: inactive (dead)

So I ran

systemctl enable systemd-resolved.service
systemctl start systemd-resolved.service
systemctl status systemd-resolved.service

That fixed the issue

[girish]

@meeksfamily06 Cloudron uses unbound and does not use systemd-resolved. You won't see any issues unless when trying to use the mail server (or maybe some apps like nextcloud might act strange when going to the apps section).