Cloudron Forum

"Thank's" is like.... [image: 1722345022070-90ea0e22-68ef-4c6a-aa8f-2e9dbc9eebe4-image.png]

Ah, thanks! I hadn't seen the app-mail-folders before.

@girish I tried this one, but i get a sad no-go : Error put object cloudron-testfile. Message: Socket timed out without establishing a connection HTTP Code: TimeoutError I'll wait the next update Tx for the patch

no sorry. Just coincidentally having a similar issue with backups, at the same time I think. I can see why you'd think that, I kind of jumped into the conversation.

@girish I don't think it requires seal encryption. I believe using seal encryption causes a different code path to be taken that avoids the underlying bug but it is not the presence or absence of seal encryption in and of itself that I believe fixes the issue. After a kernel upgrade this works fine without seal encryption though I have now enabled it as it seems like a good idea to have anyway so making it the default is probably a good idea but as long as Ubuntu 22.04's default kernel version is 5.15.0-102 this issue will likely still occur.

@girish I saw that thread, its a different problem. One I was also having on another customers site. That site the backup goes to a windows workstation share. After the last prompt "server requires a reboot" triggered it. However because of the other threads existence I fixed it by clicking the SEAL encryption box. FYI That site is on 7.7.2

I got it, thx. I will check

@girish well, not sure why it didn't work before when I rotated my keys, but backups are back up.

@nebulon I don't really know the S3 system they used

Things work like a charm indeed. I'll likely move the vps over soon or later once answering the question of where I should go. Also looking for a good option for CI/CD runner and to mitigate most issues faced this last month with Contabo.

@girish said in Make Cloudron Restore dialog more Human friendly: Is there any easy fix which does not involved coding? Yes, have the pattern available in the textbox so it's obvious what is expected. It's more the "backup date/box ver file" than just a "path".

thanks, fixed in https://git.cloudron.io/cloudron/box/-/commit/1d1a7af48ebd41fa9a54f73c124a708c226e38e8

@nebulon Ok, I'll proceed with this suggestion.

This should all be automatically handled by Cloudron already based on whatever your retention policy is https://docs.cloudron.io/backups/#retention-policy

Yes, I can see how that would make sense, however, keeping the subdomains while allowing for the domain.tld to change is I think the best of both worlds. If there needs to be a checkbox at restore to keep or discard subdomains, that would be a bonus.

@lukas Next release is 8.0, so hopefully not too long!

I had this for a while, with an instance of PeerTube, I think. But then the problem went away. Edit: nope, it was The Lounge, and possibly it went away because of this.

Good to know, thanks Girish. It never happened again, only once so I guess it was transient in nature.

Maybe search for "Hetzner" and "EACCES" - and thou shalt find....

I don't think there is any backup option out there which can do what you are hoping can be done. The one exception is if you are manually extracting the data to be restored, and putting them in different locations. I just say this so you don't go feeling like this is some sort of weakness of Cloudron. Backups rely on timestamps and exact conditions. You couldn't restore the second backup because it would look for the time slot from which it was built, in the records, and those records aren't going to be in the currently restored backup. But if it is the media you want, then the fact you do have separate sets of backups does mean you can at least navigate through the backup and find that media, and then as @nebulon said, manually add them back to your Mastodon. But I gotta say, why do you need to have this media? I mean, Mastodon IS social media, and it's meant to be ephemeral. If there is some info you like, then screenshot it, or click the link and bookmark it, print it out to PDF, or follow the poster (to then check them out post-restore to see that specific post) etc. But saving it and keeping it to be viewable only within your Mastodon seems like a use even Mastodon wasn't really meant for. Anyway, good to hear you are back up and running. Hope the new year remains happier. I'm @shane@social.futurnumerique.com if you want to expand your follow/followers!