Connections to remote servers

I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)

on

Which general topic do you have

There are some connections, I would rather not have to allow on my community version of NextCloud. In the linked document there are connections to cloud.nextcloud.com, updates.nextcloud.com and apps.nextcloud.com, ltd[1-3].nextcloud.com, garm[1-5].nextcloud.com. Are these for the Enterprise version only, because they use a subscription key that afaik I do not have in the community version. And the other non optional connection mentioned that bothers me a bit more is push-notifications.nextcloud.com. It seems to submit data like unique device identifiers. Does this mean, if I want to use push notifications on my community edition of NextCloud, I need to send uid of my customers devices to a third party?

you can try blocking this connections, obviously you should be prepared some functionality is broken.. test and decide if you want to go this path.

regarding notification a quick search tells you why this works this way e.g. What exactly is the pushnotificationproxy at https://push-notifications.nextcloud.com/?

Thanks a lot for your answer. I am aware of being able to block these connections. My intention to ask about it here, where tons of experienced and helpful people are generous enough to share their wisdom, was because I do not have a lot of experience and time to dig deep into each rabbit hole of NextCloud, even when I would love to learn everything about it. So my question was about why it is necesseray and if it is necessary for a community edition. And yes, I missed searching for the push notification thing first. Thank you for the link.

After consulting the post you provided you closed it on December 2nd 2024 and the GitHub issue 82 still open has last activity at October 24. I left my comment on the issue. I would appreciate if we could self-host the notification server.

The page you referenced on the initial post describes what is the goal.

you can - use search to find relevant discussions. but this is not easy - I would say “don’t do it at home

And again, thanks for taking time to answer and hinting about the search option. Sure, the page mentions reasons for the connection. I will figure it out, was only a bit confused by the subscription key. Obviously only necessary for Enterprise Edition. I will do some more research about the notification stuff later. It is not the most important thing. We will figure out a way to do it without the proprietary usage of the current proxy. Thanks for your support.

No, push notifications can be completely self-hosted by running a service locally see GitHub - nextcloud/notify_push: Update notifications for nextcloud clients · GitHub.

That is correct, if you don’t have a subscribtion, no data is transferred.

Please note also, there is only one version of Nextcloud (snap, AIO, bare-metal etc. are all based on the same open source code). The subscription key entitles you to documentation and official support! The update-frequency of a subscription instance is much lower than a non-subscription instance, as stability is prioritised.

Many thanks. I appreciate your helpful answer and your support. I will be glad to evaluate the solution for self-hosting the push-notification server. Considering the differences between the Community Edition and the Enterprise Edition I am happy to hear, that these are only differencing in non functional aspects. I truly love the mindset and governance of the NextCloud GmbH and their commitment to free and opensource Software. This was one of the reasons, we choose it for our planned SMB offerings we are currently prototyping. It makes sense to have an Enterprise Edition for customers with higher demand on availability and vendor support. I am happy to find out to what extend our solution will make sense without needing to go Enterprise. Thanks again for your help. Appreciate it.