Notifications troubleshooting

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Start with the obvious

Settings → Notifications — is New Message Notifications actually on for this device? Preferences are per device.
Is push enabled for the specific account you’re expecting messages from? Each connected account has its own toggle.
Click Send test. If the test arrives, push works and the problem is elsewhere.
Click Refresh to re-read the current status.

Reading the diagnostics

The Troubleshooting section reports the real state of the push stack:

Field	Healthy value	If not
GCM Sender ID	Present	Missing GCM sender ID in manifest — a server-side config issue; contact support
FCM reachable	Yes	Your network or VPN is blocking Firebase Cloud Messaging
Permission	Granted	Enable notifications for the site in browser settings
Service worker	Registered	Clear site data and reload
Subscription	Active	Failed (timeout) usually means FCM is blocked
Endpoint	A URL	Missing means no subscription exists

When Entergram recognises a specific failure it names it and suggests the fix directly.

Force reset

Force reset — “Use this if notifications are stuck or missing.”

It clears the local push registration and re-subscribes from scratch. This resolves most “it used to work” cases, especially after a browser update or a site-data clear.

Manual steps

If the reset doesn’t help, in order:

Open chrome://gcm-internals and check whether your browser has a registration at all.
Sign in again in an incognito window — this rules out a corrupted service worker or extension interference.
Clear site data for Entergram and reload.
Try Firefox to confirm whether it’s Chrome-specific.
Open chrome://settings/content/notifications to reset notification permissions for the site.

Blocked at the network level

The most common cause of Subscription timed out is that FCM is blocked — by a corporate firewall, a VPN, or a DNS filter.

Test by tethering to a phone hotspot. If push works there, the fix is a network change (allow fcm.googleapis.com and Google’s push endpoints), not an app setting.

Platform notes

Installed as a PWA — push works in installed mode; make sure OS-level notifications for the app are enabled too.
macOS — check System Settings → Notifications for your browser; Focus modes silently suppress notifications.
Windows — Focus assist does the same thing.
Mobile browsers — support varies. If the app says “Push notifications not supported”, your browser doesn’t implement them.

Sound but no toast (or vice versa)

They’re independent settings. The panel tells you which state you’re in:

Toast notifications are disabled, but sound notifications are enabled
Toast notifications are enabled, but sound is muted
All notifications are currently disabled
All notifications are enabled

Reminders are different

Reminder notifications come from the Telegram reminder bot, not from browser push. If reminders don’t fire, run the bot setup rather than debugging push — see Reminders.