Netlify deploy fails remote: ERROR: Git access over SSH is not allowed

Support
, , ,
1

netlify site name: https://pncc-scheduling-form.netlify.app/

Experiencing issues building from gitlab repository (NOT self-hosted); I have already followed the recommended troubleshooting instructions found here ( Build troubleshooting tips | Netlify Docs)
this is not a new project and for the past year at least we were able to deploy to production and to create deploy previews without any issue. I have already re-linked the gitlab repo, removed any additional generated webhooks in the repo, created new secrets and have more-or-less exhausted any new approaches I could find in the documentation.

deploy log below:
2:09:19 PM: Build ready to start
2:09:35 PM: build-image version: fcb0c1b3ada6d25c1cb58e8bc514f5f23cc14f15 (focal)
2:09:35 PM: buildbot version: aa810d582dc14bf9392c9fc64b0002bffe04d8bd
2:09:35 PM: Fetching cached dependencies
2:09:35 PM: Failed to fetch cache, continuing with build
2:09:35 PM: Starting to prepare the repo for build
2:09:36 PM: Failed during stage “preparing repo”: For more information, visit Build troubleshooting tips | Netlify Docs Warning: Permanently added “gitlab.com” (ECDSA) to the list of known hosts.

remote:
remote: ========================================================================
remote:
remote: ERROR: Git access over SSH is not allowed

remote:
remote: ========================================================================
remote:
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
: exit status 128
2:09:36 PM: User git error while checking for ref refs/heads/main
2:09:36 PM: Failing build: Failed to prepare repo
2:09:36 PM: Finished processing build request in 1.122s

2

Hey there,

Thanks for reaching out! It sounds like some of the repository permission settings may have changed on the Gitlab end?

You mentioned that you’ve already created new secrets, but I’m wondering if you’ve followed the steps here, as they seem to be applicable to the specific error you’re hitting here.

3

Hi Marcus,
thanks for getting back to me. I initially believed that changes to the repository permissions would have been the cause, but no changes to repository permissions were made between our last successful deploy and the start of this trouble. I’ve also unlinked and relinked the repo several times, and the gitlab repository reflects the expected outcome of that process: new webhooks created, a new deploy key added to our repository. However, each time I attempt to trigger a new build, either from netlify or gitlab, I’m met with the same error.

I reviewed the documentation you linked; I’m attempting to apply it but am a bit pessimistic that it will wok given the above observation. Is there some way to force netlify to authenticate using HTTPS instead of ssh?

4

Does creating a new site from the same repo make any difference?

5

Hi @hrishikesh, I took your advice and created a new project from the same repo. the build failed exactly the same.

6

mind attaching a link to the new failed build log and the site ID? I’ll take a look on the backend.

7

@SamO for the new test project we created? Here are the details:
site id: 5c3f73a0-200c-4ac5-9463-8d1dd2d25fe4

thank you for investigating.

9

I’ve asked the devs to take a look.

10

Sorry for the delay on this one. Is it possible for you to recreate your GitLab SSH keys? The devs believe, the builds might be failing as GitLab’s SSH key might have expired after a year.