Cloudron Forum

@subven I rebooted many times and unbound never came back so this isn't necessarily true. It wasn't until coming across this post that I was able to solve by repeatedly trying to start unbound times about 3 tries.

Thank you to OP and @girish for the solution!

Yeah, I think that was the problem. I have no idea what password was used because I tried quite a few of them! I ended up just biting the bullet and taking another backup with the proper password. It seems like it's working. Thanks for your help.

@jdaviescoates Hmm. The password should be correct as i'm pulling it from the manager, but I will look into this. Thanks for the lead!

@girish Yeah I was starting to think that as well. I'll give it a shot and report back. Thanks!

Hey folks,

I'm in the process of migrating to a new setup. My old setup is on 7.5.2 due to the AVX/Mongo business so on the new setup I installed Ubuntu 22.04, Cloudron 7.5.2, and I uploaded the backup config to the new install. Upon dry run restore I had to do a chown for yellowtent and it seemed like after that I was off to the races until the restore stopped with an error stating "Incorrect Header Check". That's it. I tried again and got the same results.

I'm not sure what else to do here as there's not much to go on. I just took this backup last night and I don't think anything has changed, but I don't think that would matter anyways on a dry run, right?

It looks like maybe mySQL is still causing an issue? Not sure...

Hi folks,

I had this same exact thing happen to me, though not minio. I tried the recreate docker steps and got to the third step where it says, "This will take a while...........", but i'm probably on my second or third page of only dots at this point. I can't tell if anything's actually happening or not. When should I pull the plug and just do a restore? It's probably been about four hours.

I let it run all night just to be safe and it's still doing the dots. I see a chown error?

All of the apps were stuck configuring (queued) and there was a banner at the top saying "starting services, this can take a while".

It stayed like that for quite a while so I checked the forums and saw the previous post. I tried the usual fixes of rebooting etc... But I noticed in services that mysql and postgres were spinning. I figured I'd give the docker rebuild a try rather than restore. Once I rebooted twice I got to the, "this will take a while........." And that's where it stayed.

That makes sense that there was no apt repo, but the fact was that we couldn't even get out to apt due to the DNS issue so i'd caution an immediate dismissal of AI hallucination. We were also able to get the healthcheck up and running for postgresql after it had gotten stuck during the docker recreate (see forked post) using AI as well so i'm not sure how many of the commands were inappropriate as they all went through. We did indeed disable resolved, stopped unbound, overrode resolv.conf (which i've done before for pihole many times), digged DNS, bypassed DNS using hosts, and I myself had previously performed a docker recreate. All of those commands exist except I guess the apt reinstall, but that's something I myself might have tried, if i'm being honest as it's a fairly common command on other apps.

After the 8.3.1 update many services wouldn't come up and nothing worked on this instance. I guess if you have all the information you care about on this issue, i'll go ahead and restore since i've been down for quite a while at this point.

I get the whole "AI = bad" thing, but I spent about 2 hours troubleshooting with GPT 4o (the paid version) and made significant progress until we hit a wall that we couldn't get around, which at least gave me satisfaction that we tried everything we could.

Take care.