Forums Bug Reports Thread

Push notification test fails — VAPID keys should be provisioned automatically

Patrick Bass · May 26 · 33 · 1 Locked
[Major] [High Priority] [Bug Fixed] [Always Reproduces]
🚀 OP May 26, 2026 9:09am

What happens: On /account/settings?tab=notifications, the "Test Push Notification" button fails. The tenant admin should not need to manually configure anything for push notifications to work.

Expected: VAPID key generation and web-push configuration should be part of the automatic tenant provisioning process. Push notifications should work out of the box for every tenant.

Impact: Push notifications are broken on new tenants until manually configured.


Patrick Bass
@mobieus

🚀 May 26, 2026 9:32am

Resolved. Added VAPID_PUBLIC_KEY to the FPM pool template (tenant-fpm.conf.tmpl) and the provision-tenant.sh sed substitution pass. VAPID keys were already generated at step 8.5 and written to .env, but the FPM pool did not expose the public key to the PHP process environment. New tenants now get working push notifications at provision time. Existing tenants that already have VAPID keys in .env work via phpdotenv. Deployed to all tenants.


Patrick Bass
@mobieus

Log in or register to reply to this thread.