Hey there! We've found the following might help you get unblocked faster:

• 🧵 Node.js Service Failing to Deploy with SIGTERM Error (Health Check Timeout)
• 🧵 Server cant read read env variables i set
• 🧵 Persistent Network Connection Failure
• 🧵 Node.js project throwing sissing environment variables error

If you find the answer from one of these, please let us know by solving the thread!

Can you please provide a screenshot of the service's variables tab, like this:

Furthermore, you can check these things:

a. Correct naming of variables in the server file & railway service

b. Variables have been added to the right environment (production, staging)

c. Private Key Formatting: In the Railway dashboard, input the private key exactly as it is and make sure line breaks are preserved. If you paste a multi-line key into a web form and it gets stripped or line breaks are lost, Node.js may see it as an empty or garbled value.

Are you able to see those variables when consoling them in the code?

Both server file & Railway use the same name of variables

All screenshots attached below.

And like mentioned above in production deploy logs do not pick up any data for the variables

info: [GSC] ENV GSC_CLIENT_EMAIL:

info: [GSC] ENV GSC_PRIVATE_KEY length:

info: [GSC] ENV GSC_PRIVATE_KEY start:

info: [GSC] ENV GSC_PRIVATE_KEY end:

info: [GSC] ENV GSC_PROJECT_ID:

And I've created a simple test script to see if the firebase email has permissions for GSC and if it can pull the data from the websites which i got a positive result for it is returning all domains with user permissions set to Full

Private key is formatted in one line which I have checked multiple times.

I have firstly tried just using the GOOGLE_APPLICATION_CREDENTIALS_JSON variable for GSC cause for every other aspect of the dashboard that uses these credentials are working, but GSC did not, after that I have tried this step with setting 3 seperate variables and adjusting the code to those variables, but for some odd reason it just does not want to pull the info given to it.

error: [GSC] Error fetching GSC sites:

error: Error fetching GSC sites: No key or keyFile set. {"stack":"Error: No key or keyFile set.\n at GoogleToken. (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:299:17)\n at Generator. (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:36:1660)\n at Generator.next (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:37:362)\n at asyncGeneratorStep (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:38:70)\n at _next (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:39:163)\n at /usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:39:299\n at new Promise ()\n at GoogleToken. (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:39:90)\n at GoogleToken._getTokenAsyncInner2 (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:319:31)\n at GoogleToken._getTokenAsyncInner (/usr/src/app/node_modules/gtoken/build/cjs/src/index.cjs:281:31)"}

I've created a log for the variable test itself and it returns to:

GSC_CLIENT_EMAIL: undefined

GSC_PRIVATE_KEY length: undefined

GSC_PRIVATE_KEY start: undefined

GSC_PRIVATE_KEY end: undefined

GSC_PROJECT_ID: undefined

Missing one or more required GSC environment variables.

1. Have you restarted the service/re-deployed it after changing the variables, so that the new variables could be fetched?
2. Can you please share the code snippet in which you did this: "setting 3 separate variables and adjusting the code to those variables", along with the screenshot which shows the initial lines of your server configuration.
3. Do add a "healthcheckup" endpoint in your server to check whether the server is being loaded properly! Refer to this post: https://station.railway.com/questions/node-js-service-failing-to-deploy-with-s-dc58e402#mk2w
4. Also, for just an instance, do not use env variables, and hardcode the same into your code to see whether then the code is working or not (that will confirm that Railway is having some issue with env variables)

Any update, d3dic1