Cloudron Forum

@girish got it, thanks 🙂

@girish said in Bunny Storage for Backups:

BTW, looks like they said S3 support is coming 2 years ago - https://bunny.net/blog/introducing-edge-storage-sftp-support-s3-next/

There is also a bit of an update here https://bunny.net/blog/whats-happening-with-s3-compatibility/

@girish Thank you very much !

@mic-testing-123 We have replied from there asking for more info. (specifically the backup backend and the backup logs).

@DualOSWinWiz yes, correct. This looks like some kernel related issue or some missing ubuntu package. Can you try to make the NFS mounting work with just the CLI . This will remove Cloudron out of the equation. I think it is possible some missing package or miscompiled kernel.

I got a failed backup now on the other server I have running Cloudron. There it is a first time, but it still puzzles me that the logs don't give anything but this:

InternalError: We encountered an internal error. Please retry the operation again later.

It would be helpful to get more information. At least I can see here which app this happens in (Immich), but I still wouldn't know what to do about this.

@archos for bugs like Synapse, I am fixing our code to have better logs . Off late, there's been a bunch of backup related issues. It's not clear (yet) whether this is some bug in node or some node module or the upstream provider. The error happens randomly and the logs are not helpful. I will update this post when I have a patch.

@TheMoodBoardz Does it fail with tgz format also? Not sure how to debug this since it is just crashing with no real logs. If you reach out at support@cloudron.io , we can debug further.

Yes, I know that failed backup notifications are already raised in the dashboard, but that requires me to go and look there. I have a mission-critical app that should update every day and I literally had the case that while I was on vacation, it failed one day. Nothing happened, it backed up the next day, but I simply didn't look into the dashboard that day like usually.

That's where the feature request is coming from.

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

I got that “uploading backup ***M@0MBps” too. I'll use Contabo Object Storage. But it happened on Backblaze and HetznerStorageBox too. At some days it seems to got stuck for 8 hours until I cancel. Additional Information: I'll use tgz-backup with encryption enabled.

@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".