PEM routines:get_name:no start line
See original GitHub issueHi, I’m trying to get this action running to use with peter-evans/create-pull-request.
I’m using it like this:
- uses: tibdex/github-app-token@v1
id: generate-token
with:
app_id: ${{ secrets.PR_APP_ID }}
private_key: ${{ secrets.PR_APP_PRIV_KEY }}
and the error is
2021-04-29T19:57:42.4816536Z ##[group]Run tibdex/github-app-token@v1
2021-04-29T19:57:42.4817128Z with:
2021-04-29T19:57:42.4817976Z app_id: ***
2021-04-29T19:57:42.4818651Z private_key: ***
2021-04-29T19:57:42.4819098Z ##[endgroup]
2021-04-29T19:57:42.5590518Z ##[error]Error: error:0909006C:PEM routines:get_name:no start line
I don’t have any ideas of how to debug this since I’m pretty new to using github actions. Any help would be appreciated.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
error:0909006C:PEM routines:get_name:no start line - node
What this typically means is that the PEM file is missing the indicator that the key portion has begun. PEM files are structured...
Read more >Please tutorial how to fix "error:0909006C:PEM routines ...
error:0909006C:PEM routines:get_name:no start line. How to fix it? Provide a properly formatted pkcs8 , pkcs1 , or sec1 PEM private key.
Read more >Solved: error:0909006C:PEM routines:get_name:no start line
When making a request to a HTTPS end point, we might need to pass the certificate also. This error usually comes if the...
Read more >error:0909006C:PEM routines:get_name:no start line - YouTube
json web token sign() function requires keys in certain format. Use the codehttps://gist.github.com/ygotthilf/baa58da5c3dd1f69fae9ssh-keygen ...
Read more >error:0909006C:PEM routines:get_name:no start line.
The certificates that were used in the configuration.xml file were not in PEM format. Resolution. Ran the following to generate new certificates.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This error usually means that the private key is in a wrong format. Here are a few options of what you could have done wrong:
Generate a private key, not a Client secret.When you click the generate button, you will download a
.pemfile, then copy-paste its content (literally, no changes) to yourPR_APP_PRIV_KEYGitHub secret.It was due to it being a private repo in a different org, so installing the app into the org and giving it the right permissions and all that fixed it. If the app you’re trying to do this with isn’t a private one, then the issue might be something different.