<p>For me this is because I lacked admin perms. I read that as <em>&quot;if this, that; [<strong>BUT</strong>], if this, other thing&quot;</em>.  I should have read it as, <em>&quot;if this, that; [<strong>AND</strong>], if this, other thing&quot;</em>.</p>
<p>That is to say, someone still had to do</p>
<blockquote>
<p>Under &quot;Custom domain&quot;, type your custom domain, then click Save.</p>
</blockquote>
<ul>
<li><p>This is what I saw under the UI For <em>Code and automation → Pages</em></p>
<p><a href="https://i.sstatic.net/Z48UsMqmm.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Z48UsMqmm.png" alt="My interface" /></a></p>
</li>
<li><p>And this is what a coworker with different perms saw,</p>
<p><a href="https://i.sstatic.net/A2wONTl8l.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/A2wONTl8l.png" alt="Co-worker with proper perms" /></a></p>
</li>
</ul>
<p><a href="https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization" rel="nofollow noreferrer">In our case, I had the role &quot;maintain&quot; and my coworker had the role &quot;admin&quot;</a></p>

CC BY-SA 4.0
2024-11-13T16:39:53.780Z
2024-11-13T19:24:02.493Z
2024-11-13T19:24:02.493Z
Evan Carroll
<p>Per the instructions I've created the <a href="https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site" rel="nofollow noreferrer">CNAME file</a></p>
<blockquote>
<ol start="3">
<li><p>In the &quot;Code and automation&quot; section of the sidebar, click  Pages.</p>
</li>
<li><p>Under &quot;Custom domain&quot;, type your custom domain, then click Save. If you are publishing your site from a branch, this will create a commit that adds a CNAME file directly to the root of your source branch. <strong>If you are publishing your site with a custom GitHub Actions workflow, no CNAME file is created, so you need to create one manually (containing only a line of text with your custom domain).</strong> For more information about your publishing source, see &quot;Configuring a publishing source for your GitHub Pages site.&quot;</p>
</li>
</ol>
</blockquote>
<p>However, creating the CNAME file didn't seem to do it. It made no difference and I'm still getting the 404.</p>

<github><github-actions><github-pages>
After creating a CNAME file in the repo, GitHub Pages will still not serve on a custom domain
Evan Carroll
# After creating a CNAME file in the repo, GitHub Pages will still not serve on a custom domain

(Asked by: username_0 on 2024-11-13)

Per the instructions I've created the [CNAME file](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)

> 3. In the "Code and automation" section of the sidebar, click Pages.
> 4. Under "Custom domain", type your custom domain, then click Save. If you are publishing your site from a branch, this will create a commit that adds a CNAME file directly to the root of your source branch. **If you are publishing your site with a custom GitHub Actions workflow, no CNAME file is created, so you need to create one manually (containing only a line of text with your custom domain).** For more information about your publishing source, see "Configuring a publishing source for your GitHub Pages site."

However, creating the CNAME file didn't seem to do it. It made no difference and I'm still getting the 404.

**Tags:** github, github-actions, github-pages


---

## 1 answers

### Answer by username_0 on 2024-11-13. Score: 0 | Accepted answer

For me this is because I lacked admin perms. I read that as *"if this, that; [**BUT**], if this, other thing"*. I should have read it as, *"if this, that; [**AND**], if this, other thing"*.

That is to say, someone still had to do

> Under "Custom domain", type your custom domain, then click Save.

* This is what I saw under the UI For *Code and automation → Pages*

  [![My interface](https://i.sstatic.net/Z48UsMqmm.png)](https://i.sstatic.net/Z48UsMqmm.png)
* And this is what a coworker with different perms saw,

  [![Co-worker with proper perms](https://i.sstatic.net/A2wONTl8l.png)](https://i.sstatic.net/A2wONTl8l.png)

[In our case, I had the role "maintain" and my coworker had the role "admin"](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)


---

