There is an internal issue with your Cloudflare Pages Git installation (Gitlab)
I've been using CF Pages and workers linked to my Gitlab account, and previously had no issues.
The account is authorised; and when adding a pages instance I see three namespaces under my Gitlab account dropdown: the main Gitlab user, and two groups set up on that Gitlab account.
Selecting the user or one of the groups works fine, and shows me a list of available repos to choose from. But the other group gives me an error, saying:
There is an internal issue with your Cloudflare Pages Git installation. If this issue persists after reinstalling your installation, contact support: https://cfl.re/3WgEyrH
...and says "There are no repositories on this GitLab account to connect to."
Looking at the web request in dev tools shows I am getting a 401 response, and the error code in the reponse is 8000011
I have tried disconnecting and reconnecting CF from my Gitlab account, but no luck.
Can anyone help? This is getting frustrating, as I cannot deploy any new repos.
(Previously-linked repos still auto-deploy as expected, suggesting it's purely an issue with the Git repo selection mechanism)
The account is authorised; and when adding a pages instance I see three namespaces under my Gitlab account dropdown: the main Gitlab user, and two groups set up on that Gitlab account.
Selecting the user or one of the groups works fine, and shows me a list of available repos to choose from. But the other group gives me an error, saying:
There is an internal issue with your Cloudflare Pages Git installation. If this issue persists after reinstalling your installation, contact support: https://cfl.re/3WgEyrH
...and says "There are no repositories on this GitLab account to connect to."
Looking at the web request in dev tools shows I am getting a 401 response, and the error code in the reponse is 8000011
I have tried disconnecting and reconnecting CF from my Gitlab account, but no luck.
Can anyone help? This is getting frustrating, as I cannot deploy any new repos.
(Previously-linked repos still auto-deploy as expected, suggesting it's purely an issue with the Git repo selection mechanism)
