Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: navigation to /404 throws server side exception #1185

Open
bautistaaa opened this issue Nov 26, 2023 · 7 comments
Open

[Bug]: navigation to /404 throws server side exception #1185

bautistaaa opened this issue Nov 26, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@bautistaaa
Copy link
Member

What happened?

appear to be fine on other invalid urls

What browsers are you seeing the problem on?

No response

Relevant log output

No response

@bautistaaa bautistaaa added the bug Something isn't working label Nov 26, 2023
@rbrtj
Copy link
Contributor

rbrtj commented Nov 27, 2023

It seems like it is working properly locally. After a quick research, it appears that there could be a problem with Vercel variables, but I'm not sure, and I don't really see a way to test it myself.
image

@bautistaaa
Copy link
Member Author

It seems like it is working properly locally. After a quick research, it appears that there could be a problem with Vercel variables, but I'm not sure, and I don't really see a way to test it myself. image

what in the world. ill check sentry logs

@mdwiltfong
Copy link
Contributor

I'm seeing this in production as well. @bautistaaa , did Sentry logs reveal anything? Here's an instance if that helps.

I was wondering if possibly adding a dynamic catch-all route would help here?

Screenshot 2024-01-06 at 10 45 50 PM Screenshot 2024-01-06 at 10 40 19 PM

@bautistaaa
Copy link
Member Author

perhaps? does that fix the issue

@bautistaaa
Copy link
Member Author

thought we had a catch all already though

@mdwiltfong
Copy link
Contributor

mdwiltfong commented Jan 7, 2024

It worked in either case 😂 It sounds like a environment issue though. It would be interesting to see what the logs say.

@mdwiltfong
Copy link
Contributor

I should also mention that I see the 404 page on random paths. It's only at /404 that it throws a server error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

3 participants