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
Enabling PPR causes HTTP 500 when scanned by bots #60620
Comments
Update: |
I'm seeing this too. WhatsApp seems to be a problem for me. Twitter, Reddit, iMessage work. LinkedIn, WhatsApp not working. I opened a discussion regarding this too here before I saw this issue. Is there a fix that can be done for this? |
As a side note: Leerob's site, which is also using PPR, suffers from the same issue. |
@leerob 👀 |
Interesting, on LinkedIn, sharing home page for real is fine, but Post Inspector complaints. https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fleerob.io Yet, for blog pages, which uses PPR for real, the issue is reproducible. Edit: Thinking of that, @leerob, the current behavior you experienced in LinkedIn may be due to LinkedIn caching the metadata. You may try to share the auto-generated deployment URL to verify that. |
I too have noticed that the previews work for the website itself (ratik.in in my case) but fail to work for the blog or any of the nested pages. |
Updated the OP
|
Vercel seems to finally be able to show the full log, so here is one example of it.
|
Oh, adding www.partialprerendering.com as the reproduction. https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fwww.partialprerendering.com%2F |
@mwskwong Any luck with fixing this? Seems to still be an issue :/ |
Nope. I don't think there is anything I can do from the user side, besides not using PPR. |
As a reminder, PPR is still experimental. We are currently triaging and investigating other, higher requested bugs/features right now, but thank you for providing more details on this issue. |
Link to the code that reproduces this issue
https://github.com/mwskwong/http-500-when-visit-by-bot
main
branch: PPR enabledfeature/without-ppr
branch: removed theppr
flagTo Reproduce
Deployments
main
: https://http-500-when-visit-by-bot.vercel.appfeature/without-ppr
: http-500-when-visit-by-bot-git-feature-without-ppr-mwskwong.vercel.appCurrent vs. Expected behavior
Current
The app will throw a 500 error when it is scanned by some social media bots, typically when sharing the link of the website on social media.
Reproduced on LinkedIn, Twitter, and Facebook (also with their share debuggers respectively).
It seems that it's a hydration error, but I'm not sure why it shows up on the server log.
Expected
It should not throw an error when the site is scanned by a bot.
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed), Other (Deployed)
Additional context
No response
The text was updated successfully, but these errors were encountered: