environment variable cannot be read intermittently in getServerSideProps about next.js HOT 3 OPEN

Hello @hanwool95 , since you are working in different environment and all seems to be working fine, my first instinct would check if the API_URL is defined properly in vercel production server. Also are you getting this error suddenly or are you getting this error from start?

from next.js.

Hello @hanwool95 , since you are working in different environment and all seems to be working fine, my first instinct would check if the API_URL is defined properly in vercel production server. Also are you getting this error suddenly or are you getting this error from start?

Hi @Abhishek-90,

The API_URL environment variable is correctly set to Production. However, even the VERCEL_ENV system environment variable from Vercel cannot be read from getServerSideProps in the Production environment. In the preview environment, both API_URL and VERCEL_ENV are read correctly.

This logic has been working well in Production for over a year. However, around 4 a.m. UTC on May 28, 2024, an issue occurred during deployment. None of the deployed content changed the server-side rendering logic.

Upon further investigation today, other pages using server-side rendering are also encountering errors and are currently being examined.

from next.js.

Our team eventually created a new vercel project and tested it by setting the same environment variables as the existing production, and there were no problems.
Therefore, the error has now been resolved by moving the production domain to a new project.

We still don't know what the exact cause is.

from next.js.