Git repo on branch master cannot be accessed (Works on Staging but not Production)

[SnazzyCreative]

I took a look through the other threads before posting but found that they were resolved with either ssh-add -K or specifying the correct branch. Both of which I am very well aware of.

As of today, upon deploying to production, I am getting the error that the repo on branch master cannot be accessed. This worked just last night. No changes have been made to my fork of trellis between then and now. I can, however, deploy the exact same repo to staging, which I believe to be confirming the correct setup of both the branch and the SSH Forwarding Agent.

Here are my verbose deployment logs for both the successful staging and unsuccessful production deployment attempts.

https://drive.google.com/file/d/1TiOgrsv1weaaHgkMQrqhIGnD1Wa-QtCZ/view?usp=sharing, https://drive.google.com/file/d/1p31fJBUwKXWdqVKMJqzJaqsEYKTONWO4/view?usp=sharing

Does anyone have an idea as to what is happening here?

Thanks so much.

[alwaysblank]

Are you certain the branch in question is called master? Many hosts, including BitBucket, have been moving away from that nomenclature, i.e. to main or something. BitBucket indicated they were doing so, but I can’t find any documentation on what they changed to, if anything.

fatal: [townie.snazzy.page]: FAILED! => {
  "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
  "changed": false
}

May not be related, but it might help to change no_log to false so you can see the git log output. Always helps to see log output when something’s wrong!

[SnazzyCreative]

Yes, it’s on the master branch. My server ran out of space and I feel silly. Hah!

Thanks for looking into it.