You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated to latest build, utilizing digital products recipe. Everything works correctly in dev environment, but i get an internal 500 error when in production environment. looks like it's failing at reaching
GET {backendURL}/{countryCode}/products/{product.handle}? rsc=1amso
edit: production Home page loads products correctly with the 3 get errors per product, but internal 500 error when any product is selected.
Expected behavior
correctly load dynamic product pages
Actual behavior
production fails with internal 500 error when trying to go to any product page, yet products and images display on homepage, but also gives the same GET errors on homepage, see below.
GET error on product page (prod)
Nextjs (prod)
Medusajs (prod)
however everything works as it should in dev environment.
Package.json file
Node.js version
v22.12.0
Operating system name and version
22.04.5 LTS
Browser name
Brave
What happended?
Updated to latest build, utilizing digital products recipe. Everything works correctly in dev environment, but i get an internal 500 error when in production environment. looks like it's failing at reaching
GET {backendURL}/{countryCode}/products/{product.handle}? rsc=1amso
edit: production Home page loads products correctly with the 3 get errors per product, but internal 500 error when any product is selected.
Expected behavior
correctly load dynamic product pages
Actual behavior
production fails with internal 500 error when trying to go to any product page, yet products and images display on homepage, but also gives the same GET errors on homepage, see below.
GET error on product page (prod)
Nextjs (prod)
Medusajs (prod)
however everything works as it should in dev environment.
Nextjs (dev)
Medusajs (dev)
Link to reproduction repo
https://github.com/nextjs-starter-medusa
The text was updated successfully, but these errors were encountered: