Error fetching loader data: Internal Server Error

After recent changes, I can’t make any further adjustments without getting an “Internal Server Error” when trying to actually render the site on my server. Within studio it works fine. I’ve tried to revert to an old version and publish again, without luck. I now had to lock in a specific version (yesterday evening) to get it working at least.

I don’t think it’s specific to what I’m using, because also the Render API gives error. But only on “published” mode, “preview” returns HTML, even though it only partly contains adjustments.

This is what I’m getting using @plasmicapp/loader-react:

Plasmic: doing a fresh fetch...
Error: Error fetching loader data: Internal Server Error
    at Api.<anonymous> (/Projects//node_modules/@plasmicapp/loader-fetcher/dist/index.js:139:17)
    at Generator.next (<anonymous>)
    at fulfilled (/Projects//node_modules/@plasmicapp/loader-fetcher/dist/index.js:50:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

And with the render API:

Using “preview” (works, but it’s very very slow after a change):

GET https://codegen.plasmic.app/api/v1/loader/html/preview/q9hSnzyUHDypByFZRntHfh/Homepage
{
  "html": "<div data-plasmic-project-id=\"q9hSnzyUHDypByFZRntHfh\" data-plasmic-component=\"Homepage\" ..." 
}

Using “published” (doesn’t work, “html” always empty string):

GET https://codegen.plasmic.app/api/v1/loader/html/preview/q9hSnzyUHDypByFZRntHfh/Homepage
{
  "html": "" 
}

The rendering was always very very slow, I worked against it using cache. But after the recent change, it doesn’t work at all. What I think I did is converted a repeated element (repeats based on content returned by a REST call) into a component, and adding hover states there.

I also tried to import the project into another one, copying piece by piece, without luck. Additionally I tried to duplicate the project (to loose version history, I thought maybe it’s that), but it’s not working either.

The erroring project: Plasmic

2 Likes

we have the same error since this morning. Its a plasmic problem,

1 Like

Hello @carst_lvl5.

Sorry for the delay. The issue has been solved now.

1 Like