High Performance Back-end for Nextcloud Files
-
@girish Awesome! Thank you. Put it into production today and can see all the team on it with no problems. Looking good.
One thing that would be very helpful would be if the default Nextcloud nginx.conf could be set to include the block from the guide, i.e.:
location ^~ /push/ { proxy_pass http://[LOCAL_IP]:7867/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }Presumably that won't cause an issue for installs that don't want the HPB Files (though please correct me if I have that wrong). But it would massively simplify things for those that do, guaranteeing no overwrite of the nginx config and allowing for a very simple instruction to be added in the manual (i.e. find local IP, modify script and make executable, run executable to make sure everything is working, add to cron on reboot).
@eganonoa I have to read more on that this service is , but we have to use the apache config - https://github.com/nextcloud/notify_push#apache .
BTW, why is this just not part of nextcloud itself? Seems complicated having to maintain this as a parallel system outside of nextcloud.
-
@eganonoa I have to read more on that this service is , but we have to use the apache config - https://github.com/nextcloud/notify_push#apache .
BTW, why is this just not part of nextcloud itself? Seems complicated having to maintain this as a parallel system outside of nextcloud.
"I have to read more on that this service is , but we have to use the apache config - https://github.com/nextcloud/notify_push#apache".
The way I did it was to set it up via the nginx config in the main cloudron server and then use the direct IP when running the binary in order to bypass the second proxy. So I didn't touch the apache config in the Nextcloud app (I understand it goes through both the Nginx proxy on cloudron and the apache on the Nextcloud container, right?). As of now everything works perfectly and if you don't add the block into Nginx it will fail. That's why I think it would be useful to automatically have that block in there (it redirects [NEXTCLOUD URL]/push).
"BTW, why is this just not part of nextcloud itself? Seems complicated having to maintain this as a parallel system outside of nextcloud."
Indeed it does. Given that it is just a simple service in the end, it doesn't make a whole lot of sense. Probably because it's ultimately all about desktop sync speed (with notifications a bonus) they keep it out of the main one for those who only use the web-interface or to keep overheads lower for people who either don't care about speed or would rather not add overhead to their nextcloud offerings (I'm thinking of those who might be providing it for free or for very low cost).
-
@eganonoa that all sounds great, thank you for working this out. I've not closely followed the whole thread, but it sounds like we're getting close to be able to say: it you want to enable Nextcloud's High Performance Back-end for Nextcloud Files do this: ....
I'd really love to be able to use the HPB with my Cloudron Nextcloud!
@jdaviescoates said in High Performance Back-end for Nextcloud Files:
@eganonoa that all sounds great, thank you for working this out. I've not closely followed the whole thread, but it sounds like we're getting close to be able to say: it you want to enable Nextcloud's High Performance Back-end for Nextcloud Files do this: ....
I'd really love to be able to use the HPB with my Cloudron Nextcloud!
I think now we're close enough to be able to say that indeed, and you can use the HPB with your Nextcloud without too much hassle. Once the change to Cron comes through, I think we're in good shape. Indeed it would be useful if others would try out what I have above so that we can be sure it's not just some fluke on my end!
-
@eganonoa said in High Performance Back-end for Nextcloud Files:
Noticed that the app-level nginx conf is getting overwritten daily, breaking the backend. Am trying the fix suggested by @girish here.
@girish Just to say, still no half-daily overwriting of the ngnix config since I made that change, as per the link. Everything moving smoothly. So indeed this change appears to have worked. Not sure its something you intend to incorporate into a coming release. But thought I'd give you that feedback in case you do want to.
-
@eganonoa said in High Performance Back-end for Nextcloud Files:
Noticed that the app-level nginx conf is getting overwritten daily, breaking the backend. Am trying the fix suggested by @girish here.
@girish Just to say, still no half-daily overwriting of the ngnix config since I made that change, as per the link. Everything moving smoothly. So indeed this change appears to have worked. Not sure its something you intend to incorporate into a coming release. But thought I'd give you that feedback in case you do want to.
-
@eganonoa thanks for the notes! I will test this out once we have get 7.2 out and see how we can fix up nextcloud.
@girish said in High Performance Back-end for Nextcloud Files:
@eganonoa thanks for the notes! I will test this out once we have get 7.2 out and see how we can fix up nextcloud.
Awesome. Thank you. Glad I've been able to help out somewhere. Cloudron is a very important business to us.
-
@eganonoa Looks great! The cron stuff should be released with the next release in the coming 2-3 days.
@girish I've updated to 7.2.2 just now and cannot seem to get the binary to run with @reboot. I have tried in the crontab:
@reboot /app/code/config/notify_push.sh
and
@reboot sleep 60 /app/code/config/notify_push.sh (just in case a delay is necessary)
and watching the logs I can't seem get the binary to run.
Any thoughts on what I'm doing wrong.
-
@girish I've updated to 7.2.2 just now and cannot seem to get the binary to run with @reboot. I have tried in the crontab:
@reboot /app/code/config/notify_push.sh
and
@reboot sleep 60 /app/code/config/notify_push.sh (just in case a delay is necessary)
and watching the logs I can't seem get the binary to run.
Any thoughts on what I'm doing wrong.
-
Is this incorporated now?
We're having issues with speed in Nextcloud Talk (just the text chat, not calls) specifically.
Wondering if this is a solution, or these threads ending in 2020 are still relevant advice: -
J jdaviescoates referenced this topic on
-
@eganonoa thanks for the notes! I will test this out once we have get 7.2 out and see how we can fix up nextcloud.
-
@girish Hi Girish, I wonder if nowadays there is a way to get this working? It seems like you all got quite far a long a while ago but I can't see any updates. Would be great to get it to work, especially client push!
@avatar1024 Still can recommend this one https://forum.cloudron.io/post/76397
-
@avatar1024 Still can recommend this one https://forum.cloudron.io/post/76397
@andreasdueren Thanks! The script you link to is great and provide a full package with the NC Talk HPB, Collabora etc. But I wondered if we might have gone closer to an easy solution for just the Files HPB which seems to be a rather small and light component compared to all the other stuff in the script. While simple, that script still requires to set-up a whole other server just for that, which if you don't need the Talk HPB feels a bit heavy handed.
In this thread it looks like @girish and @eganonoa got very close to get the Files HPB working smoothly.
-
@girish I've updated to 7.2.2 just now and cannot seem to get the binary to run with @reboot. I have tried in the crontab:
@reboot /app/code/config/notify_push.sh
and
@reboot sleep 60 /app/code/config/notify_push.sh (just in case a delay is necessary)
and watching the logs I can't seem get the binary to run.
Any thoughts on what I'm doing wrong.
@eganonoa said in High Performance Back-end for Nextcloud Files:
@girish I've updated to 7.2.2 just now and cannot seem to get the binary to run with @reboot. I have tried in the crontab:
@reboot /app/code/config/notify_push.sh
and
@reboot sleep 60 /app/code/config/notify_push.sh (just in case a delay is necessary)
and watching the logs I can't seem get the binary to run.
Any thoughts on what I'm doing wrong.
Did you ever find a solution to that?
-
I've packaged the Nextcloud Talk HPB (nextcloud-spreed-signaling 2.1.1 plus Janus 1.4.1 VideoRoom SFU) for Cloudron and am currently testing it in production with a few Nextcloud instances.
What it does:
- Single instance signaling server plus Janus SFU, NATS built in (loopback mode)
- One install can serve multiple Nextclouds via isolated [backend:<id>] sections
- Selectable TURN modes: Cloudron TURN addon (default), local coturn, external coturn, Cloudflare Realtime TURN, or disabled
- Works with both / and the sunweaver style /standalone-signaling/ URL prefix, so migrating from a VPS setup is straightforward
- Sensible video quality defaults (4 Mbit/s camera, 8 Mbit/s screen share) with a documented knob in config.ini
The recording backend is currently intentionally not included. May add this in the future.
TURN choice: i'm personally running the Cloudflare Realtime TURN mode. Cloudron's platform TURN was a bit unreliable for us, and Cloudflare gives you an anycast TURN edge including TURN over TLS on 443 for restrictive networks. Since Talk only speaks coturn shared secrets and Cloudflare issues short lived credentials, the package ships a small credential minting Worker plus a Talk companion app that handles caching and fallback.
So far my experience with it is slightly better than the sunweaver HPB server. But time and more concurrent users will tell.
Repo: https://git.due.ren/andreas/nextcloud-hpb-cloudron
CloudronVersions.json:https://git.due.ren/andreas/nextcloud-hpb-cloudron/-/raw/main/CloudronVersions.jsonStill early. I'd be happy about any feedback, especially from people running other TURN modes or setups with multiple backends.
-
I've packaged the Nextcloud Talk HPB (nextcloud-spreed-signaling 2.1.1 plus Janus 1.4.1 VideoRoom SFU) for Cloudron and am currently testing it in production with a few Nextcloud instances.
What it does:
- Single instance signaling server plus Janus SFU, NATS built in (loopback mode)
- One install can serve multiple Nextclouds via isolated [backend:<id>] sections
- Selectable TURN modes: Cloudron TURN addon (default), local coturn, external coturn, Cloudflare Realtime TURN, or disabled
- Works with both / and the sunweaver style /standalone-signaling/ URL prefix, so migrating from a VPS setup is straightforward
- Sensible video quality defaults (4 Mbit/s camera, 8 Mbit/s screen share) with a documented knob in config.ini
The recording backend is currently intentionally not included. May add this in the future.
TURN choice: i'm personally running the Cloudflare Realtime TURN mode. Cloudron's platform TURN was a bit unreliable for us, and Cloudflare gives you an anycast TURN edge including TURN over TLS on 443 for restrictive networks. Since Talk only speaks coturn shared secrets and Cloudflare issues short lived credentials, the package ships a small credential minting Worker plus a Talk companion app that handles caching and fallback.
So far my experience with it is slightly better than the sunweaver HPB server. But time and more concurrent users will tell.
Repo: https://git.due.ren/andreas/nextcloud-hpb-cloudron
CloudronVersions.json:https://git.due.ren/andreas/nextcloud-hpb-cloudron/-/raw/main/CloudronVersions.jsonStill early. I'd be happy about any feedback, especially from people running other TURN modes or setups with multiple backends.
I've packaged the Nextcloud Talk HPB (nextcloud-spreed-signaling 2.1.1 plus Janus 1.4.1 VideoRoom SFU) for Cloudron and am currently testing it in production with a few Nextcloud instances.
Excellent, and thank you!
Is it ok to deploy the HPBE on the same server / Cloudron that is running the Nextcloud?Peertube has something like this too.
-
I've packaged the Nextcloud Talk HPB (nextcloud-spreed-signaling 2.1.1 plus Janus 1.4.1 VideoRoom SFU) for Cloudron and am currently testing it in production with a few Nextcloud instances.
Excellent, and thank you!
Is it ok to deploy the HPBE on the same server / Cloudron that is running the Nextcloud?Peertube has something like this too.
@LoudLemur It should be ok. Not what I'm doing currently but the only technical constraint would be CPU bandwidth with too many call participants.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login