Deploying your own push-proxy server

[gperdomor]

Hi... I have my own server instance and a custom mobile app.

The ios app has this variable:

#define k_pushNotificationServer                @"https://push-notifications.nextcloud.com"

I need to change to

#define k_pushNotificationServer                @"https://push-notifications.my-custom-domain"

??

I enable the app but in the server i don't see any configuration params for this app

[MorrisJobke]

cc @marinofaggiana @nickvergessen

[nickvergessen]

The app provides the proxy-server URL to the nextcloud-server.
However the proxy code is currently not public.

[karlitschek]

@gperdomor This is still in development. Can you share some more insights what you want to achieve here? Thanks

[gperdomor]

@karlitschek i use my own instance of nextcloud server, and i have a custom ios and android app, both apps have a few modifications, including the bundle id, how get push notifications from my server?

[shadoxx]

Is there any update on this? If there needs to be a community effort to document how to set this up as a standalone server, I volunteer.

[dockay]

@karlitschek @nickvergessen there is more than one year passed, there are still some people who customized the nc apps (ios/android) and rely on the source of the proxy to get the push notifications to work. It would be super helpful to get this open source or at least a documentation on how to configure it on our own.

[nickvergessen]

@mario @tobiasKaminsky please open an issue in the android repos then, at least in this repo and especially in this issue it is offtopic.

[ElectrifyPowr]

Are there any updates on this?

This issue is already more than 4 years old.
Unfortunately, the documentation is rather very small on how to use push proxy servers, well it's is actually non-existent.

It is understandable that the push proxy code is not public.
However, this does not mean that there should be no concrete documentation on how to implement it yourself.

@nickvergessen you don't have to make the whole code public, but you could for example share code snippets on how to exactly set up a push proxy and use it with Nextcloud and with its clients (custom iOS/Android apps).

This would be very helpful for everybody concerned and I'm sure everybody would be very thankful for it.

[tcitworld]

I'm guessing nextcloud/server#29363 will require this issue being solved?

[jospoortvliet]

I'm guessing nextcloud/server#29363 will require this issue being solved?

Not really. It is simply low priority at the company - there are loads of things that we prefer to do because they will help many more Nextcloud users. Of course, anyone is free to work on this.

[ramezrafla]

@jospoortvliet

We would like to add Huawei push notifications. If you can open source the push proxy would be great so we can contribute. Otherwise we will develop one from scratch and share with the community. Don't worry about pretty-ing up docs etc. Of course, you will need to hide your Firebase and other API keys.

Thanks

[Pilzinsel64]

With the fair-use feature (wich is absolutely understandable) it seems to be more and more important to become deplyoing your own push-proxy real.
Nextcloud wants to reduce their server-load as it costs free. Also they want to provide Nextcloud Hub as fully indipendent, it's your control. But with the limits of fair push and no alternative, it's a very little bit loosing control over your instance.

I would use my own push proxy with own certificates for my instances, even if they are small and does fall under "fair-use". Probably that will do more people and the server load of Nextcloud's push proxy will be less.

My idea for how the setup could looks like:
The push proxy could be setted up via some certificates. In your cloud's config.php you enter a https url for the push proxy. All mobile apps will then listen to the instances push-proxy of the account(s) setted up (hopefully it would work like this, otherwise they need to build and provide their own apps like Nextcloud and Talk too).

EDIT: Not sure how valid my message here is, as I notices that also the Client Apps (like Files Android and Talk Android) also need the certificate (or at least a valid 'public key'). So probably my idea also isn't working.