Cloudron Forum

@avatar1024 ah, I missed that part that you restored! Thanks for reporting.

@avatar1024 Might be best to ask this upstream at https://github.com/docusealco/docuseal/discussions

For the first question: maybe https://github.com/docusealco/docuseal/issues/132 ?

Well spotted, I had done a search in there before posting but missed it. Thank you!

And well, obviously that's a shame.

Many thanks for this. The function is not actually activated but for some reasons the client seem to apply some kind of spam filter (even though when I open my spam folder it explicitly says that spam filtering is not done by the client but by the server). Anyway I definitely know where to look now so THANK YOU for your help and sorry for the tangent as this is not a Cloudron issue

Turns out the mountpoint for backups, which is /mnt/cloudronbackup/ had leftover files, which prevented it from being mounted. After clearing that folder it works fine.

I will see how we can better communicate this into the dashboard to make this more obvious in the future.

Great tip, thanks!

Agree it's insane the default is only once a week. Perhaps we should report this upstream...

@girish said in Mailing feature: add users and groups as members:

When added to a list, are you expecting the primary email of the user to be used ?

Indeed 🙂

I have clarified the text a bit more now.

@avatar1024 thanks we will update. The reason for it not being updated yet, is that their package repositories are usually lacking behind their release tag by a day and we have to wait for those.

It just so happens, that the whole file is now renamed in upstream since their loolwsd part is now called coolwsd 🙂

The package should do the config file rename and sed things for that renaming automatically.

I pushed our fork for now.

@jdaviescoates said in Cannot mount Hetzner storage box for backups using SSHFS:

@chetbaker said in Cannot mount Hetzner storage box for backups using SSHFS:

Oh I'm sorry, just to clarify, I'm trying to use Storage Boxes as Cloudron Volume.

Ah, OK. I've got that set-up but I've only ever used CIFS and not SSHFS so not sure what you have to do myself sorry.

Ah, but Girish gave instructions above in this very thread! 😆

As @robi said if you don't have ssh-keygen installed, install it.

@nebulon : interesting about Nextcloud
I used to have 4 x Nextcloud instances in my Cloudron server (different projects). 3 of them about 10Gb of files (other smaller).
My backups were working but slow.
Even after switching to 'better' VPS provider.
So after testing Seafile for a while, I have moved 2 of the Nextcloud instances over to a single Seafile VPS (with different libraries for segregation). The other 2 Nextcloud instances will follow.

I have nothing against Nextcloud and been very happy for it for long time. But if it is really only being used for file collaboration and device syncing, and you don't actually NEED the extra facilities it provides, my personal view is that Seafile is a better solution.

So would be awesome to get Seafile onto Cloudron.
But I'm quite happy running it on a separate VPS.

@avatar1024 you can send the logs to support@cloudron.io

Given that the backups are working fine on the hetzner instances, this indicates an issue during backup with the mountpoint. Maybe the connection to the storage box sees some hiccups. Those issues are generally quite hard to debug since they are often on the lower system levels 😕 Maybe you can also reach out to netcup/hetzner if they see any interruption between their networks during the time your backup failed last time.

Having a real hate / love relation with Cloudron...
The convenience of having all apps securely managed under one roof is simply fantastic.
That said, we installed Cloudron to eliminate time spend setting up simple, open-source applications - but many times we end up trying to find workarounds installing certain dependencies needed for 3rd party plugins from installed Cloudron apps...
I'm really hoping they'll allow a bit more control within the containers in the future..

Did guys figure out a solution to this issue yet?

@girish Many thanks Girish. It must have been a space problem indeed. Looking at the log, the processed froze while downloading the last big part of the image (~570MB). I tried to duplicate the app, which worked fine but and the process also froze when trying to update it (also while downloading that part the image).

Anyway, I had a about 3GB of free space which I though would be enough to update Wekan but after doing some cleaning up on the server (like deleting old apps I wasn't using), I went to about 7GB of free space and the update started working again.

There is now an update in the Cloudron Appstore that brings both a fix for this and also updates Meet to version 2.3.1.

@girish weird, "./" was the first thing I tried when it didn't on its own but there again it threw me an error about command not found and minio-credentials not being a folder. I resorted to trying bash in case I got it wrong and that's the only time it at least tried to run something (but ran into those errors).
But have just done it again and it worked fine, I must have done something wrong the first time.
Sorry for reporting a non issue and thanks for getting back