#Error: Connection closed - on Production deployment

11 messages · Page 1 of 1 (latest)

fluid garnet
#

I'm getting this error:

927-aaed07e464307c3b.js:1 Error: Connection closed.

Only on production deployments, and it happens sometimes when routing between different pages that use React.Suspense to stream. This doesn't happen in local development.

peak raptorBOT
#

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

fathom rapidsBOT
#
Please add more information to your question

Your question currently does not have sufficient information for people to be able to help. Please add more information to help us help you, for example: relevant code snippets, a reproduction repository, and/or more detailed error messages. See more info on how to ask a good question in https://discord.com/channels/752553802359505017/1138338531983491154 and #welcome message

fluid garnet
#

how is this not enough info lol?

#

that's literally it

olive niche
#

when does it appear? is it when you access a page or a route? what's the code for the page or the route?

fluid garnet
#

it happens sometimes when routing between different pages that use React.Suspense to stream
the code is too verbose to paste in here, but it is basically just a server component that renders a client component in suspense, something like:

const Comp = () => {
  <Suspense fallback={<Comp3 />}>
    <Comp2 />
  </Suspense>
};

const Comp2 = async () => {
  const data = await getData();
  return <Comp3 data={data} />
}
#

Comp and Comp2 are server components and Comp3 is a client component

#

the error shows up sometimes, but if I refresh on the same page that the error showed up on, it goes away

fluid garnet
#

this is a screenshot