Commit 039a4af0 authored by Katrin Leinweber's avatar Katrin Leinweber Committed by Achilleas Pipinellis

Docs: Work-around missing wildcard DNS entry

parent f3c9c0e1
...@@ -811,3 +811,11 @@ Upgrading to an [officially supported operating system](https://about.gitlab.com ...@@ -811,3 +811,11 @@ Upgrading to an [officially supported operating system](https://about.gitlab.com
This problem comes from the permissions of the GitLab Pages OAuth application. To fix it, go to This problem comes from the permissions of the GitLab Pages OAuth application. To fix it, go to
**Admin > Applications > GitLab Pages** and edit the application. Under **Scopes**, ensure that the **Admin > Applications > GitLab Pages** and edit the application. Under **Scopes**, ensure that the
`api` scope is selected and save your changes. `api` scope is selected and save your changes.
### Workaround in case no wildcard DNS entry can be set
If the wildcard DNS [prerequisite](#prerequisites) can't be met, you can still use GitLab Pages in a limited fashion:
1. [Move](../../user/project/settings/index.md#transferring-an-existing-project-into-another-namespace)
all projects you need to use Pages with into a single group namespace, for example `pages`.
1. Configure a [DNS entry](#dns-configuration) without the `*.`-wildcard, for example `pages.example.io`.
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