Unable to fetch fingerprints - non-standard port

[PiX06]

I'm trying to set up pipelines for a new project in the same way that I have set up many other projects in the past, however I'm getting the

"Unable to fetch fingerprints, check host SSH connection and try again"

error.

The target server is running the SSH daemon on a non-standard port so I'm supplying the Host address in the format x.x.x.x:y where y is the port number.

The firewall on the server is configured to allow SSH connections from any IP address on the non-standard port and I am able to connect without issue from my local machine via `ssh username@x.x.x.x -py` 

Not really sure how to further debug this issue

[Theodora Boudale]

Hi @PiX06 and welcome to the community.

Could you please provide the following?

• the workspace id and repo name of the repo where you are trying to add the host address, but masked (don't reveal the full names, just some characters from the workspace id and repo, so I can identify them from the ones you have access to)
• try adding the host address again and let me know the date and time in UTC that you did it

I can then check our logs and see what error we get when you try to add the address.

Kind regards,
Theodora

[PiX06]

Hi @Theodora Boudale 

Thank you for your reply.

The workspace ID is PiX** and the repo name is studi****

I've just tried fetching the host's fingerprint again at 15:00 UTC

Thanks,
Alex

[Theodora Boudale]

Hi Alex,

Thank you for the info. I can see in our logs a 404 error when we try to fetch the fingerprint.

However, for testing purposes, I tried running the following command from my work computer and it seems to work ok

ssh-keyscan -t rsa -p <port> <ip>

Additionally, this command works when testing it in a Bitbucket Pipelines build.

Is it possible that you have blocked on your firewall only some of Bitbucket IPs, listed here?

• https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

Does the command above work if you add it to your yml file?

If so, instead of fetching the fingerprint from the repo settings, you could also add the following commands in your yml file, before the commands that connect to your server via SSH:

- mkdir -p ~/.ssh
- ssh-keyscan -t rsa -p <port> <IP> >> ~/.ssh/known_hosts

I would suggest checking though if any of our IPs are blacklisted on your server.

Kind regards,
Theodora