Cloudron Forum

Tried restoring with "Decrypt Filenames" on and off, neither are working. There is no error indicating that the encryption password is wrong, preeeeety sure it's the right one. Am I just completely screwed here? Or is there something else I can do to debug this?

Trying to debug what's going on here.. should fsmetadata.json ever be encrypted? The file appears to just have garbage characters in it, but even with my encryption pw it's still unable to parse.

Fiddled around with some settings, it can find the file now but can't parse it. I am using rsync if that matters

The file is in the backup, but it's at [backup date]/box_v7.5.2/fsmetadata.json. I don't see any home folder anywhere in the backup folder. I did restore the backup manually with the UI form.

Hey! I'm trying to restore a backup (from 7.5.2) to a fresh install of 7.5.2 and am getting an error:

Any ideas?

@girish alright was able to get the dashboard back, thanks! When can we expect that update with the fix?

@girish yeah the dashboard

@girish I didn't remove that file, just the application certs and nginx is now running fine according to systemctl status nginx, just the webserver isn't loading. Unbound & box are fine too. Should I still delete that file even though nginx is running?

@girish the error it gives is the same as this one above; it is not clear that I need to actually just delete the application certs ( just found their location again at nginx/applications )

nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.myserver.net.key": 
PEM_read_bio_PrivateKey() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: ANY PRIVATE KEY)

Deleting the application certs allowed nginx to restart but my webserver is still not running, gah

@nebulon hey, not sure if you guys already implemented this fix, but I just had the exact same issue happen again this morning on a fully up-to-date Cloudron instance. Trying to remember wtf I did to fix this

@girish increased it to 72 hours; does this file get regenerated perhaps? Looks like the timeout is back to 24 hours when I checked it. Maybe on Cloudron update?

@girish yeah that is what I was doing before but it no longer working

@robi setting the timeout manually now seems to not affect the actual timeout time like it used to

@subven I am using tgz because rsync couldn't handle the char length of my encrypted file names, lol. Just need a way to manually adjust this upload time

@girish Sorry yeah it is 24 hours, however that's not enough for my uploads. My uploads take like 3 days usually. Is there a new way to manually change it?

Hello! I've been using this method described here to manually set my timeout for my long backup uploads to be much longer than the default. However after the most recent update this method no longer seems to be working.

Is there a new way I need to manually adjust the timeout of my backup uploads?

@girish I've been using this method of manually editing the js file to a longer timeout for a while now for my uploads and as of the most recent update this no longer works. Any ideas?

@girish that seems to have fixed all my problems! Can access the dashboard again. Looking forward to the next release when this is automated lol.

@girish I've deleted the nginx conf file (home/yellowtent/platformdata/nginx/nginx.conf) and am encountering a new error. It seems systemctl restart box did not regenerate this.

[emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)

Thanks for the responses guys!

I realized that my backup server was unmounted after it bugged out the other day, and it was storing backups locally in mnt/backups/snapshots folder. After purging that folder the disk space issue is resolved.

However! My cloudron instance is still inaccessible.

I followed all of the steps on this troubleshooting guide, to no avail.

After rebooting after cleaning up disk space, both nginx and unbound were in an error state. unbound restarted right away, but nginx had some issues with old certs preventing it from restarting. After purging the old certs (which I read was safe in the troubleshooting guide ), nginx was able to restart and is now running.

Unfortunately, my cloudron instance is still inaccessible and I'm not sure why. All other services mentioned in the troubleshooting guide are working properly (docker, mysql, box) according to the logs.

As far as I can tell everything is working properly, I just can't access my cloudron instance and don't know where to go from here. Any ideas for troubleshooting?

EDIT: Looks like nginx just died again for some reason. It restarted successfully once after I purged old certs, but now has the same error again even though the certs are gone.

This is the error it's giving me when I run nginx -t:

nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.myserver.net.key": 
PEM_read_bio_PrivateKey() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: ANY PRIVATE KEY)