Novu•2y ago

Troubleshooting In-App Notification Issues with Websockets

I got this question from one of our community members: "I am trying to integrate In-App notifications in my applications. I have deployed novu in seperate VM. Triggering working fine. But unable to get notification using socket in browser console I am getting Error: websocket error."

19 Replies

Unknown User•2y ago

Message Not Public

Pawan Jain•2y ago

It means websocket is not running or not properly configured in notification center

Unknown User•2y ago

Message Not Public

ebm•2y ago

I'm having a similar issue, "Invalid frame header" this is a new issue, things were previously working and there are no changes that I am aware of on the novu configuration

Pawan Jain•2y ago

Hi @ebm_3 You are also self hosting or using local env?

ebm•2y ago

Hi @Pawan Jain local env

Pawan Jain•2y ago

@ebm_3
could you please share more details or how to reproduce it. I tested in local with latest next branch. it is working fine for me

ebm•2y ago

websocket.js:124 WebSocket connection to 'wss://ws.novu.co/socket.io/?token=SECRETSTUFF*&transport=websocket' failed: Invalid frame header WS.doOpen @ websocket.js:124 Transport.open @ transport.js:84 Socket.open @ socket.js:250 Socket @ socket.js:122 Socket @ socket.js:28 Manager.open.Manager.connect @ manager.js:226 (anonymous) @ manager.js:544 I'm not sure what else I can give you to assist, I'm using a react app with local env variables for the subscriberId and applicationIdentifier I've checked inside of my account, nothing is out of the ordinary there I appreciate your help!

Pawan Jain•2y ago

@Engineering I see we have updated socket.io in this PR https://github.com/novuhq/novu/pull/2223 On stackoverflow, I found that version mismatch on client and server can be issue for above error. https://stackoverflow.com/questions/43526607/invalid-frame-header We have mismatch socket version in latest next branch WDYT??

Pawan Jain•2y ago

--•2y ago

Let me do a quick PR.

dr.really•2y ago

@paweltymczuk or @pablo.fernandez.otero does this fix the following error in v0.10?

TypeError: o.div is not a function
    at Object.<anonymous> (<redacted>\node_modules\.pnpm\@novu+notification-center@0.10.0_2zx2umvpluuhvlq44va5bta2da\node_modules\@novu\notification-center\src\components\notification-center\components\layout\header\Header.tsx:99:28)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (D:\code\monorepo\firefly\apps\web\app\routes\__admin.tsx:7:30)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)

TypeError: o.div is not a function
    at Object.<anonymous> (<redacted>\node_modules\.pnpm\@novu+notification-center@0.10.0_2zx2umvpluuhvlq44va5bta2da\node_modules\@novu\notification-center\src\components\notification-center\components\layout\header\Header.tsx:99:28)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (D:\code\monorepo\firefly\apps\web\app\routes\__admin.tsx:7:30)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)

--•2y ago

No, has nothing to do, but please open another support thread regarding this. 🙏

dr.really•2y ago

Will do!

Tobias•12mo ago

@Emil did you solve your original issue with the websocket error? Facing the same and was not able to find a solution yet?

Novu_Bot•12mo ago

@Tobias, you just advanced to level 1!

empeOP•12mo ago

Hey @Tobias! Well I have hard time recalling what was the fix.. Can you please open a new Support post in this channel and add all the details you can provide?

Tobias•12mo ago

Thanks, yeah i did, i will tag you there if that's ok 🙂

empeOP•12mo ago

SUre

Gaming

Programming

Troubleshooting In-App Notification Issues with Websockets