I’ve not updated my static site in a while (haven’t needed to), but I did today, and while previously, it all worked fine, now the deployment fails.
In the logs, I see that while the deployment sees correctly the repository and the commit (on GitLab), it fails to clone the repository:
Cloning into '.'...
Nov 10 19:19:15
remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See https://gitlab.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied
Nov 10 19:19:15
fatal: Authentication failed for MY_REPO_URL
When I inspected my GitLab account, I saw that the MyKinsta app was only granted API access, notrepo_read or repo_write. This explains the immediate problem, but I see no way to actually get the deployment to work – there’s nowhere I can see to update an access token or change the permission level, either on Kinsta or on GitLab.
I’d really like to be able to deploy this update, and to know what to do if I encounter such a problem again.
As a test, can you please go to add a new static site and check whether you actually see your repo? You don’t have to add it, just check if it’s listed when trying to add a new site.
If not, please disconnect and reconnect your GitLab account and check if the repo is visible then. The deployments should go through after that.
OK, I’ve added a new website pulling from the same repo. The name is test-deploy and the URL is test-deploy-ob8o4.kinsta.page. The build there fetches the repo and runs the deploy script (it currently fails because of dependencies, but that’s something I can fix).
Why would the two static websites on the same kinsta account pulling from the same gitlab repo behave differently at build time?
@VladimirM Now something really strange is happening. I’ve disconnected my gitlab account and the deployment ran in the same manner as before – the test-deploy site cloned the repo and tried to build. How did that happen?
Yes, I did – and I even logged out after that and logged back in with my password instead of gitlab. The test-deploy site still is able to fetch the repo.
Welcome to Kinsta Community!