Solved Can't login to account on transfered install
ianhyzy last edited by girish
I recently migrated my entire cloudron install to a new host. Some apps restored, but most did not, with the error
Network Error: Network error downloading icon : getaddrinfo EAI_AGAIN api.cloudron.io
I found out I wasn't logged in anymore as I see a login screen when clicking the app store. but I can't login — I get "An account with this email already exists". I tried changing the email on my primary account to something else but that didn't work.
@ianhyzy It looks like the DNS server is down. Are you able to resolve things ?
host www.cloudron.io 127.0.0.1? Can you check if unbound is running with
systemctl status unbound.
ianhyzy last edited by ianhyzy
@girish looks like it isn't running:
root@cloudron:~# 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 Wed 2022-03-23 00:30:02 UTC; 3h 18min ago Process: 1061 ExecStart=/usr/sbin/unbound -d (code=exited, status=1/FAILURE) Main PID: 1061 (code=exited, status=1/FAILURE) Mar 23 00:30:01 cloudron systemd: unbound.service: Main process exited, code=exited, status=1/FAILURE Mar 23 00:30:01 cloudron systemd: unbound.service: Failed with result 'exit-code'. Mar 23 00:30:01 cloudron systemd: Failed to start Unbound DNS Resolver. Mar 23 00:30:02 cloudron systemd: unbound.service: Scheduled restart job, restart counter is at 5. Mar 23 00:30:02 cloudron systemd: Stopped Unbound DNS Resolver. Mar 23 00:30:02 cloudron systemd: unbound.service: Start request repeated too quickly. Mar 23 00:30:02 cloudron systemd: unbound.service: Failed with result 'exit-code'. Mar 23 00:30:02 cloudron systemd: Failed to start Unbound DNS Resolver.
root@cloudron:~# host www.cloudron.io 127.0.0.1 ;; connection timed out; no servers could be reached
@ianhyzy was your disk maybe full at some point? You can follow the unbound troubleshooting at https://docs.cloudron.io/troubleshooting/#unbound otherwise, maybe enable remote ssh for us and send us a mail to email@example.com if we should take a direct look.
You can also see
journalctl -u unbound -fato see why unbound is not starting. You can try that along with
systemctl restart unboundto get fresh logs.
If Cloudron cannot resolve
cloudron.iothen it won't show app store view since it cannot contact cloudron.io to get the app listing.
ianhyzy last edited by
@girish I think it was ultimately a disk space issue - I restarted unbound and that seemed to do the trick. I have to move servers again because of a Vultr restriction (block storage not in the zone I had the VM in) that's unrelated to Cloudron so I'll see what happens. Thanks guys!