Codeberg/changelog
Codeberg/changelog
Watch
92
44
Issues 6 Activity

Pages #3

New issue
Open
opened 2026-01-27 18:40:21 +01:00 by fnetX · 4 comments
fnetX commented 2026-01-27 18:40:21 +01:00
Owner
Copy link

Subscribe to this issue to receive notifications around Codeberg Pages (e.g. new functionality, scheduled maintenance).

Please keep in mind that posts affecting all or many services at Codeberg will be only made in #1. You might want to subscribe it as well.

Subscribe to this issue to receive notifications around Codeberg Pages (e.g. new functionality, scheduled maintenance). Please keep in mind that posts affecting all or many services at Codeberg will be only made in https://codeberg.org/Codeberg/changelog/issues/1. You might want to subscribe it as well.
fnetX locked and limited conversation to collaborators 2026-01-27 18:40:29 +01:00
fnetX commented 2026-01-30 16:20:28 +01:00
Author
Owner
Copy link
Legacy IP addresses unavailable

Due to a hardware outage, the legacy addresses of Codeberg Pages are currently not available. While the pages are served from another server, it is currently not possible to quickly restore access via the old IP addresses.

In June 2025, we announced that migrating to the new addresses with automatic failover would become mandatory (see the corresponding blog post), but we did not expect users to be forced to this migration without advance notice.

If your Codeberg Page is still unavailable and you haven't yet changed your DNS records accordingly, please adjust them now to restore access to your website.

We cannot yet provide any estimate on if and when we will be able to reactivate access via the previous IP addresses.

<details><summary>Legacy IP addresses unavailable</summary> Due to a hardware outage, the legacy addresses of Codeberg Pages are currently not available. While the pages are served from another server, it is currently not possible to quickly restore access via the old IP addresses. In June 2025, we announced that migrating to the new addresses with automatic failover would become mandatory (see [the corresponding blog post](https://blog.codeberg.org/letter-from-codeberg-we-love-our-new-infrastructure.html#:~:text=Codeberg%20Pages:,more)), but we did not expect users to be forced to this migration without advance notice. If your Codeberg Page is still unavailable and you haven't yet changed your DNS records accordingly, please adjust them now to restore access to your website. We cannot yet provide any estimate on if and when we will be able to reactivate access via the previous IP addresses.
👍 1
Gusted commented 2026-04-18 01:31:54 +02:00
Owner
Copy link

Git-pages rollout finished

https://codeberg.org/git-pages/git-pages/ is now handling all pages traffic, that effectively means you can use git-pages to serve custom domains and {user}.codeberg.page domains that you own. It's currently setup to fallback to the legacy method via https://codeberg.org/Codeberg/pages-server/ if the domain does not exist in git-pages. This rollout has no effect on existing deployments.

The documentation was already updated to show how to use git-pages to serve {user}.codeberg.page domains and we hope to soon update this for custom domains.

## Git-pages rollout finished https://codeberg.org/git-pages/git-pages/ is now handling all pages traffic, that effectively means you can use git-pages to serve custom domains and `{user}.codeberg.page` domains that you own. It's currently setup to fallback to the legacy method via https://codeberg.org/Codeberg/pages-server/ if the domain does not exist in git-pages. This rollout has no effect on existing deployments. The documentation was already updated to show [how to use git-pages](https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/) to serve `{user}.codeberg.page` domains and we hope to soon update this for custom domains.
🎉 13
ashimokawa commented 2026-06-24 17:41:59 +02:00
Owner
Copy link

Due to a very high amount of new abusive new users using the legacy pages server, we have disabled it for all new users who will register from now on.

Also for new organizations being created from now on that belong to even existing users, the old pages server will no longer work.

Due to a very high amount of new abusive new users using the legacy pages server, we have disabled it for all new users who will register from now on. Also for new organizations being created from now on that belong to even existing users, the old pages server will no longer work.
gedankenstuecke commented 2026-10-16 19:15:35 +02:00
Owner
Copy link

The legacy (Codeberg Pages v2) server will be shutdown on December 31.

Remaining users have until then to migrate over to git-pages.

A migration guide can be found here: https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/

A tool to check if your pages are still on the legacy server is here: https://codeberg.page/migration-check/

## The legacy (*Codeberg Pages v2*) server [will be shutdown on December 31](https://blog.codeberg.org/migrate-your-site-to-the-new-git-pages-backed-codeberg-pages-now-were-sunsetting-codeberg-pages-v2.html). Remaining users have until then to migrate over to git-pages. A migration guide can be found here: https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/ A tool to check if your pages are still on the legacy server is here: https://codeberg.page/migration-check/
This discussion has been locked. Commenting is limited to contributors.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
4 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/changelog#3
No description provided.