SSH keys isseu when using self-runners

[nenadcvetkovic84]

Hi

We are trying to run a self-runner for Bitbucket for development and some testing. But I have a problem with SSH key. 

What did I do:
- SSH key created in pipelines > ssh-keys 

- new SSH key added to server (added to ~/.ssh/authorized_keys) through SSH KEY Management - key exists in file 

- A new runner added to pipelines > runners

- bitbucket-pipeline.yml

- Runner: I'm running on my local pc (tested also on a remote server)

After running the pipeline on the git change, I see only an error, and the pipeline stops

If we run on Bitbucket Runner, there are no errors and everything works.

[Ben]

Hi @nenadcvetkovic84 

Those steps seem correct, and this would be supported by Atlassian Cloud runners executing the build without issues.

To troubleshoot this further - we will need access to your runner logs, YAML config/pipelines settings. For this - our system requires that you raise a support ticket. As you have access to a paid workspace - you can raise a support ticket from the link below:

• https://support.atlassian.com/

If you have issues raising a support ticket, please let me know your timezone so I can raise one on your behalf with the team that operates within your region.

Cheers!

- Ben (Bitbucket Cloud Support)