Noticed a small typo there: https://docs.cloudron.io/guides/upgrade-ubuntu-22/
Currently it says: If you are still on Ubuntu 20, you must first upgrade to Ubuntu 20 before upgrading to Ubuntu 22.
Should say (I guess): If you are still on Ubuntu 18...
Apologies if this is not the right place to post that kind of thing.
@nebulon Thanks. If by the folder you mean /mnt/cloudronbackup then it is:
drwxr-xr-x 3 root root 4096 Aug 18 03:00 cloudronbackup/
Though this is the same for /mnt/volumes and they work fine.
drwxr-xr-x 5 root root 4096 Apr 3 09:22 volumes/
Inside /mnt/cloudronbackup I have "snapshot" folder (even thought he volume is not mounted) and this has the exact same permissions.
Inside /mnt/volumes I can see the three mounted volumes with the following permissions (top and last are mounted as sshfs and middle one is mounted as cifs - all are folders on the same Hetnzer storage box as the one I use for backups).
drwxrwxrwx 1 hetznerusername hetznerusername 4 Aug 19 10:21 8f327ff1a4c24810a6adf910170251e3/
drwxrwxrwx 2 yellowtent yellowtent 0 Jan 28 2022 a6c6bddb7ddc424596a3150383e2e4b2/
drwxrwxrwx 1 hetznerusername hetznerusername 4 Sep 8 15:10 f26fe5bedfed484db30497140b5a605d/
Let me know if you'd like ssh access.
@avatar1024 said in backup storage not mounting since update to Cloudron 7.3:
I change the backend will not that trigger a full backup without increment
Anyone knows?
Also has anyone else been facing this issue?
I know we already have Wekan, but Planka has now reached v1.0 (in fact v1.8.1), is well maintained, has a docker image, and is generally less cluttered / more modern looking and friendly to use than Wekan. Depending on how hard it is to package it could be good to have it on Cloudron.
@subven Thank you for the suggestion. I use rsync with hard-link for backup, so if I change the backend will not that trigger a full backup without increment @staff?
Hello,
Since the upgrade to 7.3 it says my backup storage is not mounted (red dot). It is a sshfs mount (Hetzner box) and used to work just fine. The exact same drive is also mounted as a volume and there it is fine (green dot).
When clicking the "Remount Storage" button, that doesn't work. When opening the config and click "Save" I get this:
Unable to create test file as 'yellowtent' user in /mnt/cloudronbackup: EACCES: permission denied, open '/mnt/cloudronbackup/cloudron-testfile'. Check dir/mount permissions
@girish I wonder if this ever got addressed?
I mean currently my memory graph is showing very odd things:
So I wonder if these issues have to do with the averaging timespan?
Also in general I do find it pretty hard to read and get info for the individual apps because they're all stacked at the bottom and you can hardly select an individual app. Is this just me? And to be fair to overall graph area is pretty small, would their be a way to "zoom" into it or something? - sorry this show be in another post, shouldn't it.
@jdaviescoates That was my thinking too 
I mean I did really like Hetzner UX but as I said when I saw the difference in prices/offering I felt it was an acceptable (/necessary as I needed more power for professional purposes) trade off. I actually kept a Hetzner VPS for my personal use for a while, but even that I switched some time ago when I was getting limited in resources. As you say storage space on Netcup VPS is also a BIG plus!
I was using Hetzner for VPS but I switched to Netcup for VPS + Hetzner storage box for backups. Currently I use their Root Server RS 2000 for company and VPS 500 for my personal one. I use Hetnzer BX11 for backups and volumes mounted as sshfs (most reliable) or cifs, works like charm.
Web interface and overall flexibility (payment, scalability, etc) are better with Hetzner but Netcup VPS are cheaper by quite a stretch and given how easy it is to switch server with Cloudron I thought the saving were worth the drawbacks (also low cost makes adoption easier when I try to promote Cloudron).
@jdaviescoates I had backup failing in the past and it was due to an issue with cifs mounting in some rare cases with Cloudron. Never had a problem since using a sshfs mount for backups.
I agree that Zulip would be quite handy as Rocket.chat seem to be going a strange way. I wonder:
Is there anyone currently working on packaging it?
Is there any particular technically difficulty when it comes to integrating it Cloudron?
@timconsidine said in Why not make Cloudron fully open source again?:
Being fully open source is a red-herring IMHO.
I love Cloudron, I promote it and recommend it because as you say it is the most accomplished platform in that field, plus I love the community and have massive respect for the two main developers, for their skills and the great software they make but also because of their friendly attitude, their care for customer support and the way they engage with users. Plus while Cloudron is not Free Software the code source is out there for any to inspect so that's great in terms of users knowing what the software actually does and that's good enough for me.
However, the point of Free Software is not only about how things are now but also about future proofing. Things might change in the devs' lives, they might need to move on, they might need a lump of cash cause something terrible happen and sell the company, or whatever else. And if the new devs have a different ethics what do we do? Look for another software and all the time and energy spent on Cloudron is kinda wasted and then not as many people benefit from this amazing platform? And to be honest the current situation makes it hard to recommend it and promote in some context because not everyone is just interested in the best software or value for money but also care about software license but ethical and practical reasons.
I don't have a perfect solution as I understand and respect Girish and Nebulon's current position in that they don't want someone to just fork everything and release it for free.
Maybe something could be added in the license that says the code must be made publicly available, and that if the license changes to a more restrictive one (one that removes the public release of the code), then the current license reverts to a Free Software license e.g. AGLP 3.0 or its successor. This would basically guarantee Freedom 0 and 1 and would implement some kind of (twisted) copyleft. And that would be enough to make me happy 
But I don't know if that is possible at all?? I'm a legal geek but not on software license...yet Anyone know?
Is there anyone still working on this? Or is there any update of some kind? Would be great to have it on the app store
@girish Thanks Girish. I'll email you directly (support@cloudron) so we can tidy things up.
@girish Hi Girish, sorry if there is something I'm missing here but you're saying you have a cost per invoice / transaction. I have a few instance on the yearly contract (so the $15/month), yet payments and invoices still happen monthly. How does that reduces your cost?
And to be honest I would much rather pay you yearly, so if that'd be better for you I'm a taker
@jdaviescoates Yes I still use mainly Collabora with Nextcloud and I have noticed tremendous improvements, especially since NC and Collabora have worked together to improve the integration.
However, I wouldn't say it is still quite like Google doc, or quite as fast as OnlyOffice. I tired OnlyOffice when I installed CryptPad and something about it feels more responsive than Collabora due to client rendering. It is basically just like editing on a desktop and Collabora is not quite there...but pretty close. Also we can feel that both Gdocs and OnlyOffice were designed as a collaborative editing tool whereas Collabora somewhat inherits the LO single user approach and tries to adapt it for collaboration and the result still does not feel quite as sleek....but here again it is getting much better than it used to be.
I can say that Collabora does not suffer from issues from the past, does not feel laggy and is perfectly fast enough to use while not feeling it's slow or weird. Also I do think it provides the most complete online office suit in terms of functionalities, and the best if you using open document formats.
@atridad Yep and it's been proposed we start adding apps in the arr family, one of which is a modern and maintained replacement for couchpotato. One of the dev @esawtooth has packaged those apps for Cloudron a while back, I think @girish is supposed to look at some of the legality behind it and see if they can be updated and added.
Hi all,
Just want to share a little tip on here. It looks like if you subscribe an external calendar to your NC instance (say you add your Gcalendar), then NC only refreshes it every week, which seems a little insane to me...or at least that was not enough more me.
So here is how to change the frequency on Cloudron NC instance. Simple open the NC terminal from Cloudron dashboard and enter:
sudo -u www-data php -f /app/code/occ config:app:set dav calendarSubscriptionRefreshRate --value "P1D"
Where P1D is the frequency period of 1 day. Period / time intervals are entered in the php format. P is for periods of day(D)/week(W)/month(M)/year(Y), if instead you want to enter a period in hour(H)/minute(M)/second(S) need to enter PT, e.g. PT5M will refresh every 5 minutes.
@nebulon Hello, just updated to 7.2.2 today and on dark theme the new contrast on app hoover looks a bit off I think. Actually it feel like something in between 7.1 and 7.2 would be good, i.e: lighter than in 7.1 so it stands out more but darker than in 7.2 so it blends more with the background.
Also I think the square around the gear icon should remain with the same background as the rest of the app if not hoovered over (as it was the case in 7.1) since the gear itself stands out enough with it's white colour.
@girish disabling the dashboard is entirely fine. You can even do it through the Web UI apps settings. In fact I've disabled the dashboard on most of my NC instances ever since it was put as the default landing page as i don't find it particularly useful.
Thanks for the tip though. Useful to land to directly Files, while keeping the dashboard enabled.
@necrevistonnezr Since the upgrade I find the overall experience in the WebUI snappier than before
Is there a plan for more backup backends like restic / borg for 7.3?
I recall it being listed for 7.2 at some point but looks like it got dropped off the list due to the need for a speedy release.
@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
Sorry for reviving one part of an old thread but since the whole thread was marked as solved but only one of the two features got implemented (it was my bad probably to request two features in one post ).
This feature request is about adding a basic moderation feature to Cloudron list without requiring require much code changes compared to the existing set-up.
So the idea is that for private list we could set one of the list member (an email address) as "the moderator" who would automatically receive emails coming from non-members of a private list (external senders) and who could then manually forward those emails (or not) to the list (since they are a member of the list).
I'm thinking about an implementation that looks like this:
I know Cloudron email lists are just forwarding lists and not real email lists and I don't intend to ask for it to become a fully fledged email list but wondered if we could add this function in a quite simple way since it is a probably the on of the key feature missing for most common uses of mailing lists (even if not as fine tuned as actual mailing lists software). Especially as it seems there having been much progress or interest to add actual mailing list apps to Cloudron (mailman or sympa).
Hello,
Was wondering if it'd be possible to add Cloudron users, and even more so groups as member of a mailing list instead of having to add their email addresses manually?
It's just that if you want to have an email list for a Cloudron group it would reduce steps and improve consistency to be able to add a group directly to a list so each time a new user gets added to a group it gets added to that list manually.
systemctl status notify_push gives me:
notify_push.service - Push daemon for Nextcloud clients
Loaded: loaded (/etc/systemd/system/notify_push.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-04-01 09:58:44 UTC; 14h ago
Process: 180019 ExecStart=/home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/apps/notify_push/bin/x86_64/notify_push /home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/config/config.php (code=exited, status=1/FAILURE)
Main PID: 180019 (code=exited, status=1/FAILURE)
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 0: Failed to connect to Nextcloud database
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 1: error communicating with the server: failed to lookup address information: Name does not resolve
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 2: failed to lookup address information: Name does not resolve
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Location:
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Backtrace omitted.
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
And journalctl -u notify_push
-- Logs begin at Mon 2022-03-28 21:45:49 UTC, end at Sat 2022-04-02 00:34:23 UTC. --
Apr 01 09:33:43 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients.
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Error:
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 0: Failed to parse config
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 1: Failed to parse nextcloud config
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 2: Failed to read config file
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Location:
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: src/config/nc.rs:8
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Backtrace omitted.
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:33:43 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:33:43 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
Apr 01 09:34:44 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients.
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Error:
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 0: Failed to parse config
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 1: Failed to parse nextcloud config
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 2: Failed to read config file
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Location:
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: src/config/nc.rs:8
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Backtrace omitted.
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:34:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:34:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Location:
Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: src/config/nc.rs:8
Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Backtrace omitted.
Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:35:05 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:35:05 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
Apr 01 09:54:28 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients.
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Error:
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 0: Failed to connect to Nextcloud database
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 1: error communicating with the server: failed to lookup address information: Name does not resolve
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 2: failed to lookup address information: Name does not resolve
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Location:
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Backtrace omitted.
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:54:28 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:54:28 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
Apr 01 09:58:44 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients.
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Error:
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 0: Failed to connect to Nextcloud database
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 1: error communicating with the server: failed to lookup address information: Name does not resolve
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 2: failed to lookup address information: Name does not resolve
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Location:
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Backtrace omitted.
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
@jdaviescoates I have now tried to just follow the basic instruction instruction on the notify push github.
What I have done:
[Unit]
Description = Push daemon for Nextcloud clients
[Service]
Environment=PORT=7867
Environment=NEXTCLOUD_URL=https://files.xxxxx.net/
ExecStart=/app/data/apps/notify_push/bin/x86_64/notify_push /app/code/config/config.php
User=www-data
[Install]
WantedBy = multi-user.target
I have replaced the path to the actual path to the binary and the config file like so
[Unit]
Description = Push daemon for Nextcloud clients
[Service]
Environment=PORT=7867
Environment=NEXTCLOUD_URL=https://files.xxxxx.net/
ExecStart=/home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/apps/notify_push/bin/x86_64/notify_push /home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/config/config.php
User=www-data
[Install]
WantedBy = multi-user.target
ran sudo systemctl enable --now notify_push as indicated.
But then it says the binary is not running.... so for now it's a fail. Anyone got any idea?
Do you have dedicated GPU? Otherwise high cpu usage is pretty normal, since the client is decoding video streams.
@girish true that it's pretty hard for this post to keep up with your coding speed
Maybe we should start a new clean one and you can let us know what you think on some of the newer ideas that were proposed (e.g. this one on my side)
Well done for you amazing work! (and the friendly support I have to say!)
I wonder if @girish you ever had time to look into this? Would be great to have Radarr as a Couch Potato replacement (since the latter has not been maintained since 2015)
@hakunamatata have tried to actually start a meeting? With version 0.3 anyone can still access the page where you can create a meeting but when you actually join the meeting it asks for authentication.
@ultraviolet sorry just bumping this to see if you'd have time to upload your package or submit a PR to https://git.cloudron.io/cloudron/wekan-app as @girish suggested here?
It feels like we got really close to get this package for Cloudron and so would be nice for it not to get dropped.
@rmdes @nebulon Just to add to this. I was in touch with @girish through support, reporting a similar issue of the backup listing getting cleared if the storage is not mounted while the automated job of cleaning up the listing is run (the listing gets cleaned regularly to get rid of stale backup entries in the listing). I believe they are trying to find a solution to this.
I proposed that either the automated cleaning job should first check that the backup location is accessible before cleaning up the entries in the db (preferred solution), or that the listing should not get cleaned automatically but only if triggered manually by pressing the "Cleanup Backup" button, in which case the user can ensure the volume is mounted before doing it (but this is less preferred as there is still a risk of deleting the entries by errors).
@murgero Updated to 23.0.2 two weeks ago with no issues.
@BrutalBirdie Actually for me the issue appeared after:
I've been in touch with support about this. I've given them ssh access and wait to hear what they say but perhaps simply upgrading to 7.1.1 might solve it.
@BrutalBirdie Can you confirm which version you are on, 7.1.0 or 7.1.1? I've hit this issue after restoring an instance that was on 7.1.0 already.
@nebulon Thanks for your reply and sorry the question was confusing cause I talked about "volume partition".
The Cloudron docs says that hard link will be used only with the filesystem back-end.
So the question is, if we use another backend (sshfs, CIFS, etc.), and if the remote file system and server do support hard links, will hard links be used on the backup to save space on the remote drive, or will they not be used because of not using the filesystem backend?
Hello, just got a quick question.
The Cloudron docs says that rsync will use hard links to save space only if using the filesystem backend so only if backups are saved on the local server. I was wondering if this is strictly true or whether it is possible to use hard link on a remote volume if the volume partition is ext4?
@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).
I wonder if there any scope for implementing the restic backend for backups in cloudron 8.0?
See this thread https://forum.cloudron.io/topic/1575/backup-improvements-restic-backend
@jdaviescoates Many thanks for looking into this and for the info.
I'll try to switch to tarball zip and see if it improves as this is not really workable at the moment.
The time it takes might just to do with all of the http requests rsync has to do to check for changes on every file but still almost 6 hours seemed quite extreme for "only" 38,000 files (mind that it is just under 2s per file so it might just be it).
Again today it took almost 6 hours to just backup nextcloud even though there were almost no changes in files / contents.
Is this normal??
It's kinda creating issues because running the backup is now going through the day.
This Nextcloud instance is about 24GB and 38,000 files.
Here is the log:
2022-02-20T05:16:50.935Z box:backuptask runBackupUpload: result - {"result":""}
2022-02-20T05:16:50.949Z box:backuptask uploadAppSnapshot: file.xxxxxxx.org upload with id snapshot/app_af90ceac-46a1-476a-88f8-26d36c6e2bcd. 11.795 seconds
2022-02-20T05:16:50.950Z box:backuptask rotateAppBackup: rotating file.xxxxxxx.org to id 2022-02-20-020000-723/app_file.xxxxxxx.org_v4.12.1
2022-02-20T05:16:50.953Z box:tasks update 9112: {"percent":65.70588235294119,"message":"Copying /mnt/cloudronbackup/snapshot/app_af90ceac-46a1-476a-88f8-26d36c6e2bcd to /mnt/cloudronbackup/2022-02-20-020000-723/app_file.xxxxxxx.org_v4.12.1"}
2022-02-20T05:16:50.953Z box:shell copy spawn: /bin/cp -al /mnt/cloudronbackup/snapshot/app_af90ceac-46a1-476a-88f8-26d36c6e2bcd /mnt/cloudronbackup/2022-02-20-020000-723/app_file.xxxxxxx.org_v4.12.1
2022-02-20T11:00:32.842Z box:backuptask copy: copied successfully to id 2022-02-20-020000-723/app_file.xxxxxxx.org_v4.12.1. Took 20621.889 seconds
2022-02-20T11:00:32.842Z box:backuptask fullBackup: app file.xxxxxxx.org backup finished. Took 20635.402 seconds
The backup is done on an Hetzner storage box via sshfs
@fbartels The thing is I can't check since the volume now works for me. But what I'm saying is that the issue was wider than just not being to write with the NC app, since data in the volume was not read / written into correctly anywhere (in NC app, in NC terminal and in Cloudron file browser) and that has nothing to do with the www-data user as far as I can tell.
And by the way you are right that the user in the terminal is root so it's true that being able to write with the terminal could still mean there is a restriction on the folder which would prevent the NC app to write. But as explained above, I don't believe this was the problem in my case.
@fbartels The problem in my case was not that. I had write access and I could create folders using the NC terminal. There is definitely an issue that might hit some users with mounted volumes.
The behaviour was rather strange:
I could write with the NC terminal, I could write with Cloudron file manager, I could read but not write with NC app (and I could see in the NC app any test folders created via NC terminal and Cloudron file manager). But in fact it turned out that even the read / write was wrong. After ticking+save and then unticking+save as describe in previous comments, I could see folders I created a while ago on the volume which I couldn't see just before, all test folders created with the NC terminal and Cloudron file manager were not there any more and now the disk was correctly readable and writeable by everything.
But let's see if what I proposed actually solves @lg2_soft issue. If this is the case then we can try to investigate further. If it doesn't work then we'll have to keep looking.
Haha, so going to the terminal I could create a folder just fine. But back in Nextcloud it still didn't work. As I said previously the Read Only box was not ticked in my case. But for sake of testing I ticked that box, pressed saved, waited for Nextcloud to restart. Then unticked the Read Only box and waited again for NC to restart. Then back to terminal and I started to see some old folders I had created on the volume ages ago (which I had forgotten about and which I couldn't see until now in neither the nextcloud app, the nextcloud console or when opening it using Cloudron filemanager). And now back in Nextcloud it works fine
It seem they might be a small bug somewhere with volume mounting.
So @lg2_soft try ticking the Read Only box, save, and then untick the box and save again.
I have the exact same issue. The solution proposed by by @mehdi unfortunately did not work for me.
And if I create a directory in the volume with Cloudron file manager I can see it in Nextcloud but still nothing seem writeable.
Of course I made sure the volume mounted in the Cloudron NC app config is not read only.
@nebulon just FIY version 21.11.1.1 is out.
Actually CODE has now got better (since version 21.11) and now renders more elements on the client side (toolbars, etc.), reducing server load.
In any case I would try to install the CODE app on the cloudron and connect it to NC and see how that works.
I'm not super keen on the OnlyOffice approach in terms of :
@ultraviolet Hello, do you have any news on this by any chance?
@nebulon @girish Just letting you know. And there'll probably be another one coming out soon.
I can never remember, am I suppose to create a new topic or should I post in the Package Update thread for those things?
Also, it might be useful to indicate the full version number with that package.
Thanks!
@jdaviescoates said in High Performance Back-end for Nextcloud Files:
Perhaps we should wait until notify_push (as it's called on Github) is at 1.0.1? (it's currently on 0.3.0) and/ or until Client Push (as it's called in Nextcloud Apps) has a positive overall rating? (currently neutral, see https://apps.nextcloud.com/apps/notify_push ).
Yes but this is only the NC app side of things. People can choose to enable it or not like any other app if there is any issue with it (plenty of apps are below the 1.0.0 version). So the question is, do the changes required on the server config have an impact if the app is disabled? It didn't look like that it would be the case.
@jdaviescoates said in High Performance Back-end for Nextcloud Files:
Yes, but slow speed (especially of the web ui) is also the worst thing about Nextcloud.
Agreed 
@jdaviescoates said in High Performance Back-end for Nextcloud Files:
@avatar1024 have you tried getting it to work by following those instructions?
I didn't because this tuto is for a native install (not in docker) and so I don;t know how some of these translate in the case of a docker / containerised install like the cloudron one.
If the process is easily adaptable, then activating the HBP for files could just be as simple as adding the steps on how to do it in the Cloudron NC package documentation. And there again, users can choose to go with it or not. It might not require any change to the app package itself.
@nebulon Sure, I agree stability is key, and we should definitely take our time with NC update!
However, HPB for files has been there since NC21 and I wasn't aware of stability issues with it. You're right that the app (notify push) is not installed by default but I think that's only because it requires extra config on the server. So I don't think we need to modify the Cloudron NC package as such but "only" create an easy way to make the appropriate change on the server. I might be wrong though.
Procedure feels fairly simple on a stand alone NC instance but I don't know how that would apply to a cloudron set-up:
https://www.youtube.com/watch?v=l_rtgzKRqTU&t=1959s (relevant part at 32:39)
With nextcloud 23 it seems there is again more improvement on performance for files, but it probably still requires the high performance back-end.
Has anyone looked into how to enable this for NC Cloudron package?
It feels like if we don't have it we're going to fall behind other NC instances which would be a shame.
Hello all,
Don't know if it's just me but the new major upgrade of collabora feels buggy. For example I've had issues with rendering in spreadsheets with copy and paste where you cannot see what is being pasted until you reload the document. I tried with firefox and Brave. Let me know if you have similar experience. Thought people should be warned about these potential issues before they upgrade just in case.
It might all come together and work nicely with Nextcloud 23 since it seem this Collabora upgrade is what is used for the new Nextcloud Office (same new features are announced in both release announcements).
@nebulon Oh yes, I see what you mean, tricky. And I agree, probably best to keep the current behaviour to avoid confusion. Maybe just adding something about it in the doc for that app would be good so people know they might not be running the latest version.
Hello,
I have noticed that on my different the loolwsd.xml had been updated at different time, one 2 months ago, another 11 months ago, another 12 months. I noticed it because on one of them I don't have the so called Cool UI (i.e. notebook) bar. Not a problem as I can probably just update the file manually if I need to and I also quite the classic bar anyway but it seemed an odd behaviour for the config file not being in sync (at least in terms of options) between the different instances. E.g. the one 11 month ago don;t have the <user_interface><mode> option at all or the version header.
So not a big deal but thought it was worth pointing out.
@girish said in Wekan-gantt-gpl: Wekan with a Gantt chart plugin:
@avatar1024 sounds like a plan! do you have a package already working? alternately, if you submit a PR to https://git.cloudron.io/cloudron/wekan-app , we can merge that as well.
It sounded like @ultraviolet has a package working for this, no? https://forum.cloudron.io/post/39263
Sadly I don't personally, I'm an enthusiastic Cloudron user and promoter but not a coder...yet!
Thanks Girish for picking this up.
@jdaviescoates indeed, using the integrated whiteboard. I think the other app been depreciated.