Commit d7670c66 authored by Russell Dickenson's avatar Russell Dickenson

Merge branch 'asmaa.hassan-master-patch-86583' into 'master'

Add another error message and the fix in the pages troubleshooting section

See merge request gitlab-org/gitlab!79228
parents c7c5c096 e2c8b713
...@@ -1511,3 +1511,20 @@ behavior: ...@@ -1511,3 +1511,20 @@ behavior:
NOTE: NOTE:
`inplace_chroot` option might not work with the other features, such as [Pages Access Control](#access-control). `inplace_chroot` option might not work with the other features, such as [Pages Access Control](#access-control).
The [GitLab Pages README](https://gitlab.com/gitlab-org/gitlab-pages#caveats) has more information about caveats and workarounds. The [GitLab Pages README](https://gitlab.com/gitlab-org/gitlab-pages#caveats) has more information about caveats and workarounds.
### GitLab Pages deploy job fails with error "is not a recognized provider"
If the **pages** job succeeds but the **deploy** job gives the error "is not a recognized provider":
![Pages Deploy Failure](img/pages_deploy_failure_v14_8.png)
The error message `is not a recognized provider` could be coming from the `fog` gem that GitLab uses to connect to cloud providers for object storage.
To fix that:
1. Check your `gitlab.rb` file. If you have `gitlab_rails['pages_object_store_enabled']` enabled, but no bucket details have been configured, either:
- Configure object storage for your Pages deployments, following the [S3-compatible connection settings](#s3-compatible-connection-settings) guide.
- Store your deployments locally, by commenting out that line.
1. Save the changes you made to your `gitlab.rb` file, then [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment