Custom Error Page Not Working

[jvarness]

Bug report

Describe the bug

I've been following the instructions here for some time: https://nextjs.org/docs#custom-error-handling

But it doesn't seem that whether I deploy a site using @now/static-build or using @now/next, whenever I get a 404 on my site, the site gets redirected to the default now 404 page, not my custom page.

To Reproduce

I have a small example of a website that utilizes next and bulma and node-sass and @zeit/next-sass. Here's the source code:

https://github.com/jvarness/next-with-bulma

For convenience, I have deployed this public project to zeit using both the next builder and the static-build builder.

https://next-with-bulma-72ahovqkn.now.sh/ <- next lambdas
https://next-with-bulma-1lj0u8d2k.now.sh/ <- static

Might this have something to do with how next-sass alters the webpack config? I don't think so but I'm unsure.

Expected behavior

When I go to the fake page on both, I should get the custom 404 page, but I just get the zeit one:

https://next-with-bulma-72ahovqkn.now.sh/fake
https://next-with-bulma-1lj0u8d2k.now.sh/fake

Screenshots

I don't have any screenshots for this.

System information

• OS: Windows
• Browser (if applies) Chrome
• Version of Next.js: 8.1.0

Additional context

You guys are awesome and your products are fantastic!

[jvarness]

Please let me know if there is any other information I can provide.

[Timer]

Hello! We've fixed this in the latest @now/next builder canary.

You can try it by updating your now.json to use @now/next@canary.

[jvarness]

@Timer thanks for responding!

Will the static version of the page also work on the canary version of the static builder? Or is the intent to create some sort of custom node server that automatically redirects 404's to the error page?

[Timer]

Hmm, both versions should work. Let us know if it doesn't!

[Timer]

This change has been released to the stable builder.

[jvarness]

@Timer still doesn't appear to be working for static. New URLs:

https://next-with-bulma-j9nerbg2e.now.sh/woop <- Lambdas
https://next-with-bulma-7pamzks1f.now.sh/woop <- Static

[nozreh]

Same, even the custom error page for 500 errors is not showing. Using both version 9.5.2 and 10.

[jvarness]

@nozreh not to speak for the Next.js team or anything, but I think setting target to serverless in your next.config.js file is probably just going to be the your best bet.

Pages will automatically be built as lambdas in Vercel as-needed, so there's not really a good reason not to just set the target to serverless. While having this work with a target of static would be nice, I really don't see any noticeable difference between having it set either way with the exception of custom 404s.

[nozreh]

Hi @jvarness thanks for the response, actually my target was set to serverless since day one. I'm not really sure why for some reason even other configurations like redirects and rewrites are not working properly. I saw this issue thread and so I piggyback if in case you happen to found a solution for it. I can't share my repo though for replication since it's a private project.

[khaladj]

The same issue for me, the custom 404.js is not working

I'm using the example repo https://github.com/vercel/next.js/tree/canary/examples/cms-wordpress

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.