whoami•2y ago

Firefox can’t establish a connection to the server at wss://.../api/0.14

I am frequently getting this the error in the title while developing with convex along with

WebSocket closed unexpectedly with code 1006 next-dev.js:23:26
    error webpack-internal:///../../node_modules/next/dist/client/next-dev.js:23
    overrideMethod moz-extension://8b846726-665b-46d4-910c-79fac2e24176/build/react_devtools_backend.js:4012
    onclose webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:90
    (Async: EventHandlerNonNull)
    connect webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:80
    WebSocketManager webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:34
    BaseConvexClient webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/client.js:112
    get sync webpack-internal:///../../node_modules/convex/dist/esm/react/client.js:72
    setAuth webpack-internal:///../../node_modules/convex/dist/esm/react/client.js:88
    setToken webpack-internal:///../../node_modules/convex/dist/esm/react/ConvexAuthState.js:25
    ConvexProviderWithAuth webpack-internal:///../../node_modules/convex/dist/esm/react/ConvexAuthState.js:32
    React 13
        commitHookEffectListMount
        commitPassiveMountOnFiber
        commitPassiveMountEffects_complete
        commitPassiveMountEffects_begin
        commitPassiveMountEffects
        flushPassiveEffectsImpl
        flushPassiveEffects
        performSyncWorkOnRoot
        flushSyncCallbacks
        commitRootImpl
        commitRoot
        finishConcurrentRender
        performConcurrentWorkOnRoot
    workLoop webpack-

WebSocket closed unexpectedly with code 1006 next-dev.js:23:26
    error webpack-internal:///../../node_modules/next/dist/client/next-dev.js:23
    overrideMethod moz-extension://8b846726-665b-46d4-910c-79fac2e24176/build/react_devtools_backend.js:4012
    onclose webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:90
    (Async: EventHandlerNonNull)
    connect webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:80
    WebSocketManager webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/web_socket_manager.js:34
    BaseConvexClient webpack-internal:///../../node_modules/convex/dist/esm/browser/sync/client.js:112
    get sync webpack-internal:///../../node_modules/convex/dist/esm/react/client.js:72
    setAuth webpack-internal:///../../node_modules/convex/dist/esm/react/client.js:88
    setToken webpack-internal:///../../node_modules/convex/dist/esm/react/ConvexAuthState.js:25
    ConvexProviderWithAuth webpack-internal:///../../node_modules/convex/dist/esm/react/ConvexAuthState.js:32
    React 13
        commitHookEffectListMount
        commitPassiveMountOnFiber
        commitPassiveMountEffects_complete
        commitPassiveMountEffects_begin
        commitPassiveMountEffects
        flushPassiveEffectsImpl
        flushPassiveEffects
        performSyncWorkOnRoot
        flushSyncCallbacks
        commitRootImpl
        commitRoot
        finishConcurrentRender
        performConcurrentWorkOnRoot
    workLoop webpack-

6 Replies

ian•2y ago

@whoami if you send @presley your deployment name (like friendly-animal-123) we can dig into what was happening here. is it still an issue?

whoamiOP•2y ago

I’m not sure if it’s gone, I’ll keep monitoring it now I got this again, I kept refreshing the page locally and got WebSocket closed unexpectedly with code 1006 and my log just shows waiting for new logs Ok I just dm'ed @presley WebSocket closed unexpectedly with code 1006 got this again I have no idea what's going on waiting it to automatically resolve on its own is painful 🥲 Firefox can’t establish a connection to the server at wss://clean-dinosaur-909.convex.cloud/api/0.14.0/sync. @ian @presley I think i need to sort this out

presley•2y ago

This is quite strange. I assume the last occurrence happened around 4:45am PDT? I do not see anything interesting on the backend. All servers were up and running with no errors reported. Just to confirm, you see those errors in the browser and it takes a while (many seconds or minutes) for the web socket to reconnect? Does this happen when you open a new tab or existing tab suddenly disconnects? What happens if you open the another tab or use another browser?

whoamiOP•2y ago

I think it lasts for a few minutes, during that period, I tried opening a new tab, restart with yarn dev, none of these reconnects the websocket. It typically happens when I walk away from my laptop for a few hours (I left my project open with yarn dev) I think this should be some issue on the client side, I’ve seen a similar case in the discord channel, have you met anything like this?

presley•2y ago

There is one bug we have a fix for in the upcoming npm release. But it would not explain a connection from new tab not working.

whoamiOP•2y ago

Now I’m not sure if I opened up a new tab or just keep refreshing the page. What was the problem you have fix? just got this again firefox keeps notifying me the error after close / open tabs, then I tried Chrome and it works for me

Firefox can’t establish a connection to the server at wss://.../api/0.14

Did you find this page helpful?