- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 39
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
fix(AWS-Lambda) "The specified key does not exist" when open /sitemap.xml on production #431
Comments
Hey, looks like maybe you solved this? I was going to suggest it was likely an AWS lambda config issue (i.e it thinks sitemap.xml should be a static file) |
No I didn't find a solution yet. Actually how this plugin works does it registers an ssr route to provide the sitemap data or how? |
Your reproduction looks fine though? plantsnap.com/sitemap.xml Yes it's a SSR route, you can choose to prerender the |
Yes, this is what I did, I uploaded a static file on S3 currently loaded at the What do you mean by "you can choose to prerender the /sitemap.xml path if you prefer it static"? |
🐛 The bug
I'm having issue with opening the sitemap on production. Here is the result I receive:
404 Not Found
🛠️ To reproduce
plantsnap.com/sitemap.xml
🌈 Expected behavior
To see the sitemap generated by the module instead if receiving 404 Not Found
ℹ️ Additional context
Here is part of my nuxt config:
The text was updated successfully, but these errors were encountered: