Failed to render SSG page for ${getSsgPageIdentifier(ssgPage

Error message

Failed to render SSG page for ${getSsgPageIdentifier(ssgPage)}.${reason ? ` ${reason}.` : ''} Check details above.

What it means

The summary warning printed by the same 'warn'-mode SSG renderer error handler after the page and error details. It identifies the failed page via getSsgPageIdentifier(ssgPage), appends an optional reason, and tells the developer to look at the details printed above. The build continues; the failed page is simply not (fully) prerendered.

Source

Thrown at app-vite/lib/modes/ssg/ssg-builder.js:71

      console.error(ssgPage)
      error('Render error for the above SSG page:')
      console.error(err)
      error(
        `Failed to render SSG page for ${getSsgPageIdentifier(ssgPage)}.` +
          (reason ? ` ${reason}.` : '') +
          ' Check details above.'
      )
    }
  }

  if (onSsgRendererError === 'warn') {
    return ({ err, reason, ssgPage }) => {
      console.log()
      warn('SSG build failed to render SSG page:')
      console.warn(ssgPage)
      warn('Render error for the above SSG page:')
      console.warn(err)
      warn(
        `Failed to render SSG page for ${getSsgPageIdentifier(ssgPage)}.` +
          (reason ? ` ${reason}.` : '') +
          ' Check details above.'
      )
    }
  }

  if (onSsgRendererError === 'ignore') {
    return () => {}
  }

  fatal(
    'Invalid value for quasar.config.ssg.onSsgRendererError:' +
      `"${onSsgRendererError}". Must be one of: "abort", "error",` +
      ' "warn", "ignore" or a function.',
    'FAIL'
  )
}

View on GitHub (pinned to 4841521b5f)

Solutions

Scroll up in the build log to the 'Render error for the above SSG page' output; fix the root error there.
Use the page identifier to locate the failing route, then reproduce with `quasar dev` and inspect server-side behavior.
Guard SSR-unsafe code paths or fix the failing data fetch.
Exclude the problematic route from SSG generation if prerendering is unnecessary.

Defensive patterns

Strategy: try-catch

Try / catch

try {
  await buildSsg()
} catch (err) {
  // locate the failed page identifier from the log above this summary
  console.error('SSG build completed with unrendered pages:', err)
}

Prevention

Read the detailed error printed above this summary line before changing config.
Run builds with onSsgRendererError:'fail' in CI to fail fast with full stacks.
Fix SSR-unsafe code per failing page identifier.
Exclude non-prerenderable routes from generation.

When it happens

Trigger: Same as the renderer error itself: getSsgRendererErrorHandler (onSsgRendererError === 'warn') invoked with a failed { err, reason, ssgPage }; this message is the closing line of the warn() call at ssg-builder.js:71.

Common situations: Prerendering routes that throw during SSR — client-only APIs, failing data fetches without error handling, or misconfigured base/publicPath causing asset resolution errors during render.

Related errors

AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30). Data as JSON: /api/errors/f4d4f4697af7742c. Report an issue: GitHub.