ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
@nickdavies07 - I'm going to help bump this as I've been having the same issue this week on Forge / Digital Ocean. I've tried all that suggestions that come up in searches - as you seem to have - but nothing gives .. I get the same error as you.
My work around at the moment is just to ssh into the server and do a https based git clone to set up the repo and then git pull to deploy. That works but it's a hassle
@SCREENBEETLE - I didn’t unfortunately. I re-tried the steps I mentioned above and got it to work but it seemed to work sporadically. Our end solution was to just create a single GitHub account for our workplace and use that. Would have loved a solution to this though.
For anyone still interested, I did get it working with the following steps. First explain what forge does when you connect your source control account (being github, bitbucket, etc).
I'll use github here as a demo. This is what forge does when you activate "Quick deploy" in a forge site:
Forge set up your server ssh public key in your github user, so your server has access to do pull request
Forge put a webhook in your github project with a specific forge URL that has a token, and that allow forge to run your deployment script when someone hit that url (that is github when detect a new commit)
So you need to manually do those 2 steps:
Log in through ssh into your serve using your forge user.
Get your public server ssh key with this command cat ~/.ssh/id_rsa.pub (your public key may be in other place if you do not create the server through forge, but that is a standard place)
In your new github account go and load that key as a deploy key in your repo config, or better as a user level key if you have more than one project in that server.