Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Error: config.privateKey does not exist at given fs path #18

Closed
NoobTW opened this issue Nov 21, 2020 · 4 comments
Closed

Error: config.privateKey does not exist at given fs path #18

NoobTW opened this issue Nov 21, 2020 · 4 comments

Comments

@NoobTW
Copy link

NoobTW commented Nov 21, 2020

New version is not working. (I was able to do this 5 hours ago)

Here's my config:

- name: deploy using SSH
      uses: garygrossgarten/github-action-ssh@release
      id: remote
      with:
        host: ${{ secrets.HOST }}
        username: ${{ secrets.USERNAME }}
        password: ${{ secrets.PASSWORD }}
        port: ${{ secrets.PORT }}
        command: |
          echo test

And here's the log.

Establishing a SSH connection to ***.
⚠️ The GitHub Action couldn't connect to ***. AssertionError [ERR_ASSERTION]: config.privateKey does not exist at given fs path
at new AssertionError (internal/assert/assertion_error.js:418:11)
at NodeSSH.connect (/home/runner/_work/_actions/garygrossgarten/github-action-ssh/release/dist/index.js:10101:31) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: undefined
}
Error: config.privateKey does not exist at given fs path

I have seen that there are a few updates (0.6.0 & 0.6.1), so maybe something breaks. Haven't check any code yet; just try to provide some information first.

@garygrossgarten
Copy link
Owner

garygrossgarten commented Nov 21, 2020

@NoobTW Sorry to hear, please use an older version (0.5.0) until I found the issue. I also moved the release tag back to 0.5.0.

@garygrossgarten
Copy link
Owner

@NoobTW The bugs seems to be coming from updating the node_ssh dependency. Seems like this library now handles it's config different from what I was used to. This should be resolved in 0.6.3. Are you able to try this version and report back?

@NoobTW
Copy link
Author

NoobTW commented Nov 22, 2020

The release tag is working right now. I'll check 0.6.3 later. Thanks!

@NoobTW
Copy link
Author

NoobTW commented Nov 22, 2020

Yes, I can confirm that my config works on v0.6.3. This issue can be closed, I think. Thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants