Set up Web push notifications in your test environment

To enable web push notifications on your website, it's crucial that your site is served over HTTPS and has a valid SSL certificate. This ensures secure communication between your website and the user's browser, which is a strict requirement for web push functionality.

Why is HTTPS necessary?

Web push notifications rely on a secure connection to function correctly. This security is provided by HTTPS, which encrypts the data exchanged between your website and the user's browser. A valid SSL certificate, signed by a trusted Certificate Authority (CA), verifies your website's identity and establishes this secure connection.

How to ensure your website meets the HTTPS requirement:

• Access via HTTPS: Verify that your website is accessible using https:// in the URL, rather than http://.
• Valid SSL Certificate: Confirm that your SSL certificate is valid and issued by a trusted Certificate Authority. Self-signed certificates are generally not trusted by browsers and will prevent web push from working.

Testing on Localhost

When testing web push notifications on a local development environment (localhost), you might encounter issues if you are not using a proper HTTPS setup. Browsers, particularly Chrome, strictly enforce the HTTPS requirement for web push. Using HTTP or a self-signed certificate that isn't trusted by your browser during localhost testing can lead to connection problems or prevent web push notifications from being delivered.

To avoid these issues during development, ensure your local environment mimics a production HTTPS setup as closely as possible, or be aware of the browser's security restrictions.

If you have any additional questions or concerns, please contact Support team