Unable to log into the app store
-
Hi all I have a cloudron instance hosted on linode and looking to add an app to it. I click on the cloud store link and it is requiring me to log in. No big deal, I enter the information and it is telling me that the email already exists. Which is correct I bought a subscription. I check to make sure I am on the log in screen and not the register for an account and verify that this is the case. Tried it in Firefox and Chrome and getting the same error. Any ideas?
-
Can you send an email with your cloudron.io account email to support@cloudron.io then I can see what is failing there.
-
Can you send an email with your cloudron.io account email to support@cloudron.io then I can see what is failing there.
-
@nebulon I just sent an email with the information, let me know if there is anything else you need.
@therealcoldguy thanks.
So, the issue here was that unbound was down for some reason (this is usually because server ran out of disk space at some point).
root@localhost:~# host my.cloudron.io ;; connection timed out; no servers could be reached root@localhost:~# systemctl status unbound ā unbound.service - Unbound DNS Resolver Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-12-30 15:18:35 UTC; 1 months 19 days ago Process: 2883 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE) Main PID: 2883 (code=exited, status=1/FAILURE) Warning: journal has been rotated since unit was started, output may be incomplete.systemctl restart unboundfixes the problem. -
@therealcoldguy thanks.
So, the issue here was that unbound was down for some reason (this is usually because server ran out of disk space at some point).
root@localhost:~# host my.cloudron.io ;; connection timed out; no servers could be reached root@localhost:~# systemctl status unbound ā unbound.service - Unbound DNS Resolver Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-12-30 15:18:35 UTC; 1 months 19 days ago Process: 2883 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE) Main PID: 2883 (code=exited, status=1/FAILURE) Warning: journal has been rotated since unit was started, output may be incomplete.systemctl restart unboundfixes the problem. -
@girish How can some test conditions be added so that when they fail, the affected service is restarted to attempt resilience, instead of failure?
@robi yeah, it's getting fixed! the appstore view needs to a show a proper error message that it cannot contact cloudron.io. As for unbound, what happens is:
- Server runs out of disk space
- unbound writes a 0 sized anchor file
- It won't start anymore despite server restart.
It's same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232555
-
G girish referenced this topic on
