WS debugging chat
Thats it for the error message but this is the web socket error event object:
Event {isTrusted: true, type: 'error', target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
isTrusted
:
true
bubbles
:
false
cancelBubble
:
false
cancelable
:
false
composed
:
false
currentTarget
:
WebSocket {url: 'wss://dev.api.mage.stream/wsinit/channelid/a496d37…e20fbc5cd99abad15faaefa46e389e2537faa1962/connect', readyState: 3, bufferedAmount: 0, onopen: null, onerror: null, …}
defaultPrevented
:
false
eventPhase
:
0
returnValue
:
true
srcElement
:
WebSocket {url: 'wss://dev.api.mage.stream/wsinit/channelid/a496d37…e20fbc5cd99abad15faaefa46e389e2537faa1962/connect', readyState: 3, bufferedAmount: 0, onopen: null, onerror: null, …}
target
:
WebSocket {url: 'wss://dev.api.mage.stream/wsinit/channelid/a496d37…e20fbc5cd99abad15faaefa46e389e2537faa1962/connect', readyState: 3, bufferedAmount: 0, onopen: null, onerror: null, …}
timeStamp
:
2583.800000011921
type
:
"error"8 Replies
Bringing this into a thread
good idea
Can you provide an example repo of exactly what you have deployed? Or are you saying it’s the chat demo with zero changes - ?
nearly zero changes. but its been working for years. so im assuming its account related
and that demo hasn't been changed since last year.
its working locally.
just not in dev and prod environments
Nearly zero is not zero.
There’s no “account level” changes we make.
i can share my desktop with you if that makes it easier to run through any issues you may see
can this be an issue?
And DNS records of workers are navigating to "/workers/services/view/mage-api-dev/production/triggers" that got moved.
triggers are now under:
"/workers/services/view/mage-api-dev/production/settings/triggers"
this wss url should at least be reachable. im testing in https://websocketking.com/
wss://dev.api.mage.stream/
✅ solved. remove smart placement in workers.