-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The user 'System:PublicAccess;aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' is not authorized to access this resource #236
Comments
I have a similar issue when running against gitenterprise 3.8. In the same context, I also observed the server returning status 500. |
I believe this issue may be caused by the branch name containing non-ASCII characters ( Update: it seems to be confirmed, I forked the project to a test one, then renamed the branch and the worklow branch name and now it deploys without errors: https://github.com/IDLFAC/test-github-pages/actions/runs/6617290103 |
en attendant la correction de actions/deploy-pages#236 et actions/deploy-pages#185 car actions/deploy-pages ne supporte que les noms de branche contenant uniquement des caractères ASCII
I appear to be having a similar issue except that when I tried to remove a non-ASCII character it did not resolve the issue. |
I'm going to close this as a duplicate of #185 but your mention of the Artifacts service error may prove to be useful. |
My workflow: https://github.com/IDLFAC/CyberMots/blob/d44c761d6c81c72ce60e32f1d4b43b25d9c15ff4/.github/workflows/ruby.yml
deploy job logs https://github.com/IDLFAC/CyberMots/actions/runs/6442789709/job/17493982576
The error itself is not helpful:
If I check the Artifact exchange URL:
I know the
permissions
is set globally and not on the deploy job directly but this is working on others workflows on other projects.When I check the API message:
But the repository does exists and is configured to use Github Pages with Github Actions (settings at https://github.com/IDLFAC/CyberMots/settings/pages).
Whatever the issue is, I think the error messages and error handling could be greatly improved.
The text was updated successfully, but these errors were encountered: