plasmic internal server error

macrozone commented 5 months ago

according to the customer after deploying a new version through plasmic studio, the site went complete down.

I now see in the logs that plasmic itself is throwing a 502 error:

⨯ Error: Error parsing JSON response: SyntaxError: Unexpected token < in JSON at position 0; status: 502; response: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.25.3</center>
</body>
</html>
    at Api.<anonymous> (/path/to/project/node_modules/@plasmicapp/loader-fetcher/dist/index.js:162:15)

This error happens only when preview is set to false (like in production), if preview mode is on, it works as normal

macrozone commented 5 months ago

plasmic support is looking into it (via slack)

one faulty request ist https://codegen.plasmic.app/api/v1/loader/code/versioned?cb=17&platform=nextjs&loaderVersion=10&projectId=eyip6GNwDBeQnbGopR8mfg%4052.1.3

macrozone commented 5 months ago

https://codegen.plasmic.app/api/v1/loader/code/versioned?cb=17&platform=nextjs&loaderVersion=10&projectId=eyip6GNwDBeQnbGopR8mfg%4051.0.2

is the last version that worked, after that its faulty

macrozone commented 5 months ago

had to revert to an older version. Waiting for plasmic support to find the culprit

macrozone commented 5 months ago

culprit seems to be a very deeply nested component:

this seems to be the result of a bug or glitch in plasmic studio when copy pasting certain elements

plasmicapp / plasmic

plasmic internal server error #108