Setup and configuration
Network requirements for push notification
To send push notifications, Notification Service must be able to send HTTPS requests to the endpoints of the according provider. Following domains must be accessible by the Notification Service Backend.
| Browser | Addresses |
|---|---|
Google Chrome |
https://fcm.googleapis.com https://mtalk.google.com |
Apple Safari |
https://*.push.apple.com |
Mozilla Firefox |
https://updates.push.services.mozilla.com |
Microsoft Edge |
https://*.notify.windows.com |
-
If the proxy setting is not specified via the proxyEnabledServices global environment variable, the proxy configuration can be established in the Helm configuration in the following manner:
######### Optional: Notification service proxy for web push and email notifications in the Helm chart ########
notification:
deployments:
notification-service:
env:
HTTP_PROXY: "http://your-proxy.com:8080"
HTTPS_PROXY: "http://your-proxy.com:8080"
NO_PROXY: "localhost,127.0.0.1, domain-of-the-notification-service.com"
######### End of Notification Service Proxy for Web Push ########The NO_PROXY environment variable is used to exclude the Notification Service from the proxy. This is necessary to avoid routing the requests to the proxy, which might result in a loop or additional latency. Ensure that the domain of the system and its IP addresses are included in the NO_PROXY list.
Similar applies to the client side (Browsers on the client devices). Strict firewall or proxy configurations may block the incoming web push notifications. In case of issues, please check the browser vendor documentation about communication requirements.