Codeberg/Community
54
325
Fork
You've already forked Community
12

Custom domain with Codeberg Pages causes 404 error #2028

Closed
opened 2025年07月18日 03:55:56 +02:00 by freyalin · 4 comments

Comment

Greetings,
I have the repository https://codeberg.org/freyalin/pages configured for serving pages and I added a .domains file at main branch's root

freyal.in
www.freyal.in
freyalin.org
www.freyalin.org
freyalin.codeberg.page
pages.freyalin.codeberg.page
pages.pages.freyalin.codeberg.page

I have checked the dns record, for freyal.in and freyalin.org

A 217.197.84.141
AAAA 2a0a:4580:103f:c0de::2
TXT pages.freyalin.codeberg.page
CNAME www freyalin.codeberg.page

I believe I'm not a noob and read all the manuals, but I still cant figure out why I keep getting Sorry, but this page couldn't be served: "Forge returned 404 Not Found" if I open the custom domain. It works under the default domain freyalin.codeberg.page tho... And redirection won't work.

The closest thing I've found is .domains file placing under pages branch instead of main fixes the redirection issue, but still doesn't fix 404...

I tried to create a minimum page under freyalin/pages-test/main/index.txt, and .domains file plus dns records, and it still returns 404 when I try to visit with custom domain.

Thanks!

### Comment Greetings, I have the repository https://codeberg.org/freyalin/pages configured for serving pages and I added a `.domains` file at main branch's root ``` freyal.in www.freyal.in freyalin.org www.freyalin.org freyalin.codeberg.page pages.freyalin.codeberg.page pages.pages.freyalin.codeberg.page ``` I have checked the dns record, for freyal.in and freyalin.org ``` A 217.197.84.141 AAAA 2a0a:4580:103f:c0de::2 TXT pages.freyalin.codeberg.page CNAME www freyalin.codeberg.page ``` I believe I'm not a noob and read all the manuals, but I still cant figure out why I keep getting `Sorry, but this page couldn't be served: "Forge returned 404 Not Found"` if I open the custom domain. It works under the default domain `freyalin.codeberg.page` tho... And redirection won't work. The closest thing I've found is `.domains` file placing under pages branch instead of main fixes the redirection issue, but still doesn't fix 404... I tried to create a minimum page under freyalin/pages-test/main/index.txt, and `.domains` file plus dns records, and it still returns 404 when I try to visit with custom domain. Thanks!

DNS is still propagating it seems, the pages server is still seeing pages.freyalin.codeberg.page (even after I flushed the DNS entry).

DNS is still propagating it seems, the pages server is still seeing `pages.freyalin.codeberg.page` (even after I flushed the DNS entry).

@Gusted wrote in #2028 (comment):

DNS is still propagating it seems, the pages server is still seeing pages.freyalin.codeberg.page (even after I flushed the DNS entry).

Isn't this supposed to be the correct txt record? ö

Should I use pages.pages.username.codeberg.page or username.codeberg.page instead? In my understanding of TXT [[branch.]repo.]user.codeberg.page and what is indicated here

otherwise, A/AAAA records must be used, together with one TXT record:
name myself.example.com, type A, data 217.197.84.141
name myself.example.com, type AAAA, data 2a0a:4580:103f:c0de::2
name myself.example.com, type TXT, data frida.codeberg.page

it seems that username.codeberg.page=pages.username.codeberg.page=pages.pages.username.codeberg.page,
Unless I specify the branch to main or something else.
Please correct me if Im wrong.

Also, should I place .domains file under the root directory of main branch or pages branch? Thanks

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2028#issuecomment-5872621: > DNS is still propagating it seems, the pages server is still seeing `pages.freyalin.codeberg.page` (even after I flushed the DNS entry). Isn't this supposed to be the correct txt record? ö Should I use `pages.pages.username.codeberg.page` or `username.codeberg.page` instead? In my understanding of `TXT [[branch.]repo.]user.codeberg.page` and what is indicated [here](https://docs.codeberg.org/codeberg-pages/using-custom-domain/) > otherwise, A/AAAA records must be used, together with one TXT record: > name myself.example.com, type A, data 217.197.84.141 > name myself.example.com, type AAAA, data 2a0a:4580:103f:c0de::2 > name myself.example.com, type TXT, data frida.codeberg.page it seems that username.codeberg.page=pages.username.codeberg.page=pages.pages.username.codeberg.page, Unless I specify the branch to main or something else. Please correct me if Im wrong. Also, should I place `.domains` file under the root directory of main branch or pages branch? Thanks

@freyalin wrote in #2028 (comment):

it seems that username.codeberg.page=pages.username.codeberg.page=pages.pages.username.codeberg.page,

Ah the latter is not correct, for historical reasons custom domains default to the main branch instead of pages branch, so in your case the TXT record should be pages.pages.freyalin.codeberg.page.

@freyalin wrote in https://codeberg.org/Codeberg/Community/issues/2028#issuecomment-5872627: > it seems that username.codeberg.page=pages.username.codeberg.page=pages.pages.username.codeberg.page, Ah the latter is not correct, for historical reasons custom domains default to the `main` branch instead of `pages` branch, so in your case the TXT record should be `pages.pages.freyalin.codeberg.page`.

Nice, it makes sense now! Thanks

Nice, it makes sense now! Thanks
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2028
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?