Website not building [HELP]


Recently we have started to experience problems with building our sites due to authentication, it seems the key is no longer working with our private self-hosted git repository. We thought the issue was with our legacy pro plan so we upgraded to the business plan but to no avail.

Here is the site;

Here is the full build log;
4:36:15 PM: Build ready to start

4:36:16 PM: build-image version: 09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41

4:36:16 PM: build-image tag: v3.5.0

4:36:16 PM: buildbot version: 172aa31cb336bae73f9eb30159b9f95fe46f2e63

4:36:16 PM: Building without cache

4:36:16 PM: Starting to prepare the repo for build

4:36:17 PM: User git error while checking for ref refs/heads/dev

4:36:17 PM: Failing build: Failed to prepare repo

4:36:17 PM: Failed during stage 'preparing repo': error checking for ref: Warning: Permanently added '[]:7999' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
: exit status 128

4:36:17 PM: Finished processing build request in 616.277592ms

Please help!

Hi, @and0. When you link a site to a private third-party Git repository, we provide the public key for the SSH key we will use to access the repository. This is covered in our documentation here:

I’m showing that this Git repository was changed or relinked less than 24 hours ago. Each time this is done, we generate a new SSH key and the new key will need to be uploaded to the Git host for this repository.

I’m sending you a private message (PM) with the new public key now. Again, if this sites repository is relinked again, the SSH key will also need to be updated each time this is done.

If there are other questions or concerns, please let us know.

Hey Luke, I’m getting the same error message for deploys on my staging site:

I haven’t touched anything in a while, so not sure how it came to be.

Can we do the same fix you mention here?


Hi, @mcb-11561. I don’t see any submodules being uses so relinking the repo should resolve this. There are instructions for this here:

For the last step after clicking “Link to a different repository”, then just relink the existing repo. If that doesn’t work though, please let us know.

1 Like