{"record":{"id":"cdab83d9d46010c5","repo":"vercel/next.js","slug":"cannot-render-page-with-path-pathname-did-yo","errorCode":null,"errorMessage":"Cannot render page with path \"${pathname}\", did you mean \"/${pathname}\"?. See more info here: https://nextjs.org/docs/messages/render-no-starting-slash","messagePattern":"Cannot render page with path \"(.+?)\", did you mean \"/(.+?)\"\\?\\. See more info here: https://nextjs\\.org/docs/messages/render-no-starting-slash","errorType":"console","errorClass":null,"httpStatus":null,"severity":"error","filePath":"packages/next/src/server/base-server.ts","lineNumber":2250,"sourceCode":"    }\n\n    return this.getInternalWaitUntil()\n  }\n\n  protected getInternalWaitUntil(): WaitUntil | undefined {\n    return undefined\n  }\n\n  private async renderImpl(\n    req: ServerRequest,\n    res: ServerResponse,\n    pathname: string,\n    query: NextParsedUrlQuery = {},\n    parsedUrl?: NextUrlWithParsedQuery,\n    internalRender = false\n  ): Promise<void> {\n    if (!pathname.startsWith('/')) {\n      console.warn(\n        `Cannot render page with path \"${pathname}\", did you mean \"/${pathname}\"?. See more info here: https://nextjs.org/docs/messages/render-no-starting-slash`\n      )\n    }\n\n    if (\n      this.serverOptions.customServer &&\n      pathname === '/index' &&\n      !(await this.hasPage('/index'))\n    ) {\n      // maintain backwards compatibility for custom server\n      // (see custom-server integration tests)\n      pathname = '/'\n    }\n\n    const ua = req.headers['user-agent'] || ''\n    this.renderOpts.botType = getBotType(ua)\n\n    // we allow custom servers to call render for all URLs","sourceCodeStart":2232,"sourceCodeEnd":2268,"githubUrl":"https://github.com/vercel/next.js/blob/258b1c1bc05f7099816b88f70b7b3422b24a4b8d/packages/next/src/server/base-server.ts#L2232-L2268","documentation":"Route-path warning in Server.renderImpl (base-server.ts): the pathname handed to the internal render API does not start with '/'. Internal rendering expects root-relative paths; a bare 'foo' silently fails route matching, so the dev-facing warning (console.warn, not a throw) suggests the leading-slash form '/foo' while rendering continues.","triggerScenarios":"Thrown at packages/next/src/server/base-server.ts:2243 when the library encounters an invalid state.","commonSituations":"See trigger scenarios.","solutions":["Prefix the page path with a leading slash, e.g. render \"/pathname\" instead of \"pathname\"."],"exampleFix":null,"handlingStrategy":"validation","validationCode":null,"typeGuard":null,"tryCatchPattern":null,"preventionTips":[],"tags":[],"backgroundTag":null,"analyzedSha":"258b1c1bc05f7099816b88f70b7b3422b24a4b8d","analyzedAt":"2026-08-19T02:10:13.922Z","contentChangedAt":"2026-08-19T02:10:13.922Z","schemaVersion":2},"datasetVersion":"2026-09-14T00:17:10.932Z"}