Error: Something went wrong during remote rendering.

[steve-nay-sage]

I hadn't been able to work with Redocly Dev Portal for a few weeks. When I got back to it and tried to run my local configurations, I saw errors when the site was loading. I finally cloned the developer-portal-starter repository fresh, followed by yarn install, yarn clean, and then yarn start. Bundling and linting are fine, but then I get these errors:

success Checking for changed pages - 0.001s
success source and transform nodes - 12.114s
success building schema - 0.902s

 ERROR #11321  PLUGIN

"gatsby-node.js" threw an error while running the createPages lifecycle:

Something went wrong during remote rendering. Please, save this Ray ID:
b3220e78-c4af-4425-ba7a-60863e87e1b0 and contact Redoc.ly team.

  Error: Something went wrong during remote rendering. Please, save this Ray ID:
   b3220e78-c4af-4425-ba7a-60863e87e1b0 and contact Redoc.ly team.

  - index.js:1 remoteRender
    [redocly-12-7-21]/[@redocly]/developer-portal/dist/engine/plugins/gatsby-red
    ocly-mermaid/index.js:1:696

  - task_queues.js:93 processTicksAndRejections
    internal/process/task_queues.js:93:5

  - index.js:1 module.exports
    [redocly-12-7-21]/[@redocly]/developer-portal/dist/engine/plugins/gatsby-red
    ocly-mermaid/index.js:1:1002

  - extend-node-type.js:209 parseString
    [redocly-12-7-21]/[gatsby-transformer-remark]/extend-node-type.js:209:11

  - extend-node-type.js:167 getAST
    [redocly-12-7-21]/[gatsby-transformer-remark]/extend-node-type.js:167:29

  - extend-node-type.js:264 getHeadings
    [redocly-12-7-21]/[gatsby-transformer-remark]/extend-node-type.js:264:19

  - extend-node-type.js:578 resolve
    [redocly-12-7-21]/[gatsby-transformer-remark]/extend-node-type.js:578:26

  - async Promise.all

  - async Promise.all

  - async Promise.all

  - async Promise.all

  - async Promise.all

  - async Promise.all

  - graphql-runner.ts:207 GraphQLRunner.query
    [redocly-12-7-21]/[gatsby]/src/query/graphql-runner.ts:207:14

  - api-runner-node.js:434 runAPI
    [redocly-12-7-21]/[gatsby]/src/utils/api-runner-node.js:434:16

info Total nodes: 205, SitePage nodes: 2 (use --verbose for breakdown)
failed createPages - 11.038s
success Checking for changed pages - 0.000s
success createPagesStatefully - 0.084s
success update schema - 0.046s
success write out redirect data - 0.001s
success Build manifest and related icons - 0.110s
success onPostBootstrap - 0.114s
info bootstrap finished - 33.347s
success onPreExtractQueries - 0.001s
success extract queries from components - 0.276s
success write out requires - 0.034s
success run static queries - 0.229s - 9/9 39.27/s
success run page queries - 0.028s - 2/2 70.83/s
⠀
You can now view portal-template in the browser.
⠀
  http://localhost:3000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀
  http://localhost:3000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build
⠀
success Building development bundle - 37.093s

Needless to say, the site isn't actually there even though the server is running. Do I need to update some dependency?

Windows 10 Node v14.16.0

[RomanHotsiy]

HI @steve-nay-sage, we have an outage right now caused by AWS outage.

Please follow https://status.redocly.com/ for updates.

[steve-nay-sage]

Thanks @RomanHotsiy . I hope they finish getting all services up soon. It's too bad that an AWS outage affects trying to run the dev portal on my laptop with local OAS definitions.

[RomanHotsiy]

@steve-nay-sage you can remove all the mermaid diagrams from the portal to temporary workaround the issue.

Look for

```mermaid

[steve-nay-sage]

Thank you. I deleted the mermaid entry from index.md and deleted the whole mermaid.md file, and now the site starts.

:-)