Cant deploy my gatsby site because of env variables

[l0st0]

Hello by build I get this error

Error: error:0909006C:PEM routines:get_name:no start line
It is because I set .env variables … they working fine on computer but there is some issue.

I need advice to debug deploy https://app.netlify.com/sites/pizzalucky/deploys/5e6f6ca14f77b900095d3a3a

thanks for help

[perry]

hi there, welcome. where and how are you trying to set .env variables? We need a little more information on what you are trying to do before we can assist.

[l0st0]

Thanks for answer… well they are set in Build & deploy key: GATSBY_CLIENT_EMAIL value: “projec…” it looks like it dont want to read quotation marks (") … on my computer works nice and if I get out quotation marks it runs same error like here

[l0st0]

And using in gatsby-config on top I have
require(“dotenv”).config({
path: .env.${process.env.NODE_ENV},
})
and need to use it in
credentials: {
client_email: GATSBY_CLIENT_EMAIL,
private_key: GATSBY_PRIVATE_KEY
},

[perry]

hi, are you setting up your environment variables here? I am still trying to understand what is happening

here is some additional info:

Build environment variables

[l0st0]

Yes I did set them here. And cant find out why it is not working.

[Jinksi]

I have had a similar issue using a Firebase private key as an env variable.

If it is a similar issue, you could try processing the GATSBY_PRIVATE_KEY with JSON.parse()

credentials: {
  client_email: GATSBY_CLIENT_EMAIL,
  private_key: GATSBY_PRIVATE_KEY[0] === '-' ? GATSBY_PRIVATE_KEY : JSON.parse(GATSBY_PRIVATE_KEY)
}

See previous post:

Using Firebase Admin SDK with Lambda Function

Hey @AnthonyFromTheVault I came across the same problem and I ended up running the production variable through JSON.parse() to correctly format the key in production. I continued to use dotenv for local and production env variables, with this ternary condition: const { FB_PRIVATE_KEY } = process.env const serviceCredential = { // ... privateKey: FB_PRIVATE_KEY[0] === '-' ? FB_PRIVATE_KEY : JSON.parse(FB_PRIVATE_KEY), // ... }

[l0st0]

Thank you. It did not work like you wrote but when I set it together it worked.

credentials: JSON.parse(${process.env.GATSBY_CREDENTIALS})

[Jinksi]

Awesome glad you worked it out

[luke]

Hi, @Jinksi, thank you for sharing your solution and, @l0st0, thank you for sharing the solution that worked for you also. Both answers are likely to be helpful if someone searches the community site for similar errors.

[rajan-magar]

@luke I am facing the same issue. But I am creating an environment variable to access my private keys with double-quotes. Settings > Build & deploy > Environment > Environment variables

Getting this error:

[luke]

Hi, @rajan-magar, would you please take a look at these topic and let us know if they are helpful or not?

[Support Guide] How do I access private repositories in the build environment?

The link from your repository to our service only authenticates us against the “main” repo that you first configured, and won’t automatically allow access to submodules even if they also belong to you and you’ve granted Netlify access to those repositories. In case your submodule is public , you can change the URI schema for it to start with https:// and it will should work without further adjustment (so, in .gitmodules , change git@github.com… to https://github.com/… ) If you have a privat…

[Support Guide] Using an SSH key via environment variable during build

Some workflows require use of an SSH private key during build - for instance, logging in to a server to restart your backend, or using git clone on a private repo during build. There are better ways to accomplish this goal for most use cases, but in case you choose to do that, below is an approach that can work. First, create an ssh key and add the public key (shorter one) to your service (e.g. on your GitHub repo settings, or in ~/.ssh/authorized_keys on your server) Then, take the private k…

[muskos]

Hi @rajan-magar . I got the same issue.

I added a quote to SERVICE_ACCOUNT_PRIVATE_KEY. Like
SERVICE_ACCOUNT_PRIVATE_KEY="----key----"

Also in code, I added:
JSON.parse(SERVICE_ACCOUNT_PRIVATE_KEY)

It helped me.