Link result in url when using pages in CE.
Summary
When I'm trying to use pages to build a page in a project in CE, the setting-pages shows the link successfully but always result in 404 The page you're looking for could not be found.
Even the exactly the same files in another User pages(not CE) works accurately. I use the simple plain html text to test this problem, but still, result in 404.
Steps to reproduce
-
ask the administration to config the pages url
-
Add a html file:index.html
<html>
<head>
<title>hello</title>
</head>
<body>
hello world
</body>
</html>
* add a .gitlab-ci.yml file:
This file is a template, and might need editing before it works on your project.
https://gitlab.com/pages/plain-html
Full project:pages: stage: deploy script:
- mkdir .public
- cp -r * .public
- mv .public public
artifacts:
paths:
- public only:
- master
* configure the runner follow official document
### What is the current *bug* behavior?
in the setting-pages shows `Congratulations! Your pages are served under:****`
but open the link, it's 404 not found
### What is the expected *correct* behavior?
shows a helloworld html
### Output of checks
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)