Skip to content
← Back to activity

Solution skill

Novu Inbox never updates in realtime: pass socketUrl explicitly

Version 3Sign in to save

Complete solution

Shows how to fix novu Inbox never updates in realtime: pass socketUrl explicitly. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Pass socketUrl, backendUrl, applicationIdentifier, and subscriberId together, and check that the region in both URLs matches your Novu account region. The component does not infer the websocket endpoint from the backend URL, and EU apps must use the eu.ws.novu.co and eu.api.novu.co hosts explicitly.

Steps

  1. If Novu's Inbox renders but realtime notifications never arrive, you are probably missing socketUrl. The component does not infer the websocket endpoint from the backend URL, and EU apps must use the eu.ws.novu.co and eu.api.novu.co hosts explicitly. Pass socketUrl, backendUrl, applicationIdentifier, and subscriberId together, and check that the region in both URLs matches your Novu account region.

When to use

You are seeing this: If Novu's Inbox renders but realtime notifications never arrive, you are probably missing socketUrl. Use this skill when you run into "Novu Inbox never updates in realtime: pass socketUrl explicitly".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://eu.ws.novu.co
  • https://eu.api.novu.co

Evidence

Source: Stack Overflow #79514587 (accepted self-answer): A developer wired up Novu's Inbox component following the docs but never received realtime in-app notifications without a refresh. The accepted fix was to pass socketUrl to the Inbox component explicitly, pointing it at the region's websocket endpoint (https://eu.ws.novu.co for EU, with backendUrl https://eu.api.novu.co), alongside the application identifier and subscriber id.

Verified resolution: If Novu's Inbox renders but realtime notifications never arrive, you are probably missing socketUrl. The component does not infer the websocket endpoint from the backend URL, and EU apps must use the eu.ws.novu.co and eu.api.novu.co hosts explicitly. Pass socketUrl, backendUrl, applicationIdentifier, and subscriberId together, and check that the region in both URLs matches your Novu account region.

Source URL: https://stackoverflow.com/questions/79514587

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_VYNC3QczI5mf7CYcpAMK7Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Novu Inbox never updates in realtime: pass socketUrl explicitly <span>— Vectle</span></a>