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

domain not specified in <code>.domains</code> file #873

Open
opened 2023年01月07日 11:21:14 +01:00 by jiacai2050 · 6 comments

Hi, I host my website via Codeberg Pages, it used to works as expected, but when I visit it today, it show

Misdirected Request!
Sorry, but this page couldn't be served.
We got an "domain not specified in <code>.domains</code> file"
We hope this isn't a problem on our end ;) - Make sure to check the troubleshooting section in the Docs!

I haven't updated our repo for a while, and I check .domains is still here:

Is there anything wrong with Pages service?

PS: This is my custom domain: https://en.liujiacai.net/

<!-- NOTE: If your issue is a security concern, please send an email to contact@codeberg.org (and if related to Gitea also to security@gitea.io) instead of opening a public issue. Thank you. Welcome to the Codeberg Community Tracker. This is the right place for bug reports, feature requests and feedback. It's the central place where we track progress and discuss, so please open issues here unless you are sure it's directly related to a specific Codeberg product and only some contributors there need to join the discussion. Easy rule: If you are unsure, report it here. When reporting bugs or asking for features in the software itself, please understand that Codeberg is a fork of Gitea. Please always check upstream (→ see FAQ) if your there is already an open issue. If not, you'd really help us if you could directly get in touch with the maintainers and open an issue here if you think a wider audience should know about that (e. g. when discussing hotfixes, backports or when discussing whether some feature should become part of Gitea or a Codeberg "add-on"). If you don't have a GitHub account, please mention this and we'll gladly forward your report to the Gitea maintainers. Thank you for reporting your findings and giving feedback on Codeberg. ## Some FAQ: ### What does upstream mean? Upstream refers to Gitea, the software Codeberg is built upon. If we ask you if you can report upstream, please visit https://github.com/go-gitea/gitea/issues and check for the bug there and report elsewise. It's usually good if the person interested in a feature or bugfix opens the request to react to questions and join the discussion. We would usually just fire the report, but won't find the time to properly react to that ... **If you do not have a GitHub account**, just tell us and we'll happily forward the report for you. ### I just noticed a typo in the sign_up / sing_up route when regis... No, this is not a typo, but intentional. It was a quick fix to avoid spammers targetting our instance and it actually worked out quite well to rename the route from sign_up to sing_up (few people notice, nice to see you have sharp eyes) ... we might have to take more effective countermeasures in the future, but for now we're actually quite good with that one ... ### How can I help? If you want to help improving Codeberg as a community home for software development, we'll gladly welcome your contribution. Check out the docs about improving Codeberg https://docs.codeberg.org/improving-codeberg/ and have a look at the open issues, especially those that are looking for contribution https://codeberg.org/Codeberg/Community/issues?state=open&labels=105 - some of them don't even require much coding knowledge. We are also happy if you forward bug reports to Gitea if the original author hasn't done that yet or hasn't got a GitHub account. --> Hi, I host my website via Codeberg Pages, it used to works as expected, but when I visit it today, it show ``` Misdirected Request! Sorry, but this page couldn't be served. We got an "domain not specified in <code>.domains</code> file" We hope this isn't a problem on our end ;) - Make sure to check the troubleshooting section in the Docs! ``` I haven't updated our repo for a while, and I check `.domains` is still here: - https://codeberg.org/jiacai2050/blog-en/src/branch/pages/.domains Is there anything wrong with Pages service? PS: This is my custom domain: https://en.liujiacai.net/

Seems like it's working again, Codeberg was having quite some troubles today. This could have been related to that. Feel free to re-open if this happens again.

Seems like it's working again, Codeberg was having quite some troubles today. This could have been related to that. Feel free to re-open if this happens again.

this is happening to me right now on pixouls.xyz. perhaps it will self resolve as well.

this is happening to me right now on pixouls.xyz. perhaps it will self resolve as well.

Today I have setup uptimerobot with my website, it seems Codeberg Pages is not very stable, I can't imagine it has been unavailable for over 1 hour....

image

Today I have setup [uptimerobot](https://uptimerobot.com/) with my website, it seems Codeberg Pages is not very stable, I can't imagine it has been unavailable for over 1 hour.... ![image](/attachments/131c6a1b-dfde-496c-a787-dbd09a422672)

only 86.58% Codeberg Pages -> https://status.codeberg.eu/status/codeberg

and on downtime there is a message to try https://pages.codeberg.org/something but with hsts turned on and no valid ssl cert for that subdomain.. this is just another error

and by the way no caching is set?! this would improve perf a lot, pls check:
Cache-Control HTTP response header

only 86.58% Codeberg Pages -> https://status.codeberg.eu/status/codeberg and on downtime there is a message to try https://pages.codeberg.org/something but with hsts turned on and no valid ssl cert for that subdomain.. this is just another error and by the way no caching is set?! this would improve perf a lot, pls check: `Cache-Control` HTTP response header

This happens with my site as well, though only sometimes, and at regular-ish intervals.

For a few hours I ran a script that, once per minute, would send a request to my site to see if it was online. A monitoring tool would've probably been more convenient, but oh well.

This resulted in the following timeline:

2023年02月02日 09:14:29 UTC Site goes offline.
2023年02月02日 09:29:42 UTC Site is back online.
2023年02月02日 10:15:28 UTC Site goes offline.
2023年02月02日 10:30:40 UTC Site is back online.
2023年02月02日 11:32:08 UTC Site goes offline.
2023年02月02日 12:02:38 UTC Site is back online.

Codeberg pages has 100% uptime on the status page though. And the DNS records were fine too.

This happens with my site as well, though only sometimes, and at regular-ish intervals. For a few hours I ran a script that, once per minute, would send a request to my site to see if it was online. A monitoring tool would've probably been more convenient, but oh well. This resulted in the following timeline: | 2023年02月02日 09:14:29 UTC | Site goes offline. | | ----------------------- | -------------------- | | 2023年02月02日 09:29:42 UTC | Site is back online. | | 2023年02月02日 10:15:28 UTC | Site goes offline. | | 2023年02月02日 10:30:40 UTC | Site is back online. | | 2023年02月02日 11:32:08 UTC | Site goes offline. | | 2023年02月02日 12:02:38 UTC | Site is back online. | Codeberg pages has 100% uptime on the status page though. And the DNS records were fine too.

Another victim here. Happens every one or two days. Typically resolved in 30min or so.

Another victim here. Happens every one or two days. Typically resolved in 30min or so.
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
6 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#873
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?