Overview
This guide covers how to add SYNQ’s public SSH key as an access key (deploy key) to your Bitbucket repository.Before you start: Create your Git integration in SYNQ first by following the integration form instructions. You’ll need the public SSH key from that integration.
Prerequisites
- Access to Bitbucket Cloud or Bitbucket Server/Data Center
- Admin access to your repository (required to add access keys)
- Public SSH key from your SYNQ Git integration
⏱️ Estimated time: 5 minutes
IP Whitelisting (If Required)
If your Bitbucket workspace uses IP allowlisting, add SYNQ’s egress IP addresses for your region. See SYNQ IP Whitelist for the complete list. For instructions on configuring IP allowlisting in Bitbucket, see Bitbucket’s guide on IP allowlisting.Adding the Access Key
Repository URL Format
When configuring the integration in SYNQ, use the SSH URL format for Bitbucket: Format:[email protected]:workspace/repository.git
Example: [email protected]:mycompany/analytics-platform.git
For Bitbucket Server/Data Center, the format may vary:
[email protected]:project/repository.gitssh://[email protected]:7999/project/repository.git
Troubleshooting
Access key not working
- Verify the complete public key was copied (including the
ssh-rsaorssh-ed25519prefix) - Ensure the access key was added to the correct repository
- Confirm the key has read-only permissions
Connection refused
- Check that your workspace’s IP allowlist (if configured) includes SYNQ’s egress IPs
- Verify the repository SSH URL is correct in SYNQ’s integration form
- For Bitbucket Server, ensure the instance is accessible from SYNQ’s IP addresses
No Repository Settings visible
- Confirm you have admin access to the repository
- Check with your Bitbucket administrator for access permissions
SSH URL format issues
- Bitbucket Cloud uses:
[email protected]:workspace/repo.git - Bitbucket Server may use a custom port:
ssh://git@hostname:7999/project/repo.git - Do not use HTTPS URLs - only SSH URLs are supported