NameSilo suspends codeberg.org and delays a Forgejo update

NameSilo suspends codeberg.org and delays a Forgejo update

The domain codeberg.org was placed in clientHold on November 18, taking offline services associated with Codeberg, a nonprofit platform for hosting software projects. The outage also forced Forgejo to postpone a security update scheduled for that day; the following day, Altus Intel reported that the delegation had been restored, although the change was not yet visible to everyone.

The incident affected more than just the homepage. While the domain was not resolving, Git operations that used it failed, and other services hosted under codeberg.org became inaccessible. Codeberg opened an incident on its status page, published on its alternative domain, codeberg.eu.

The domain disappeared from Codeberg's account

Codeberg confirmed the problem on Mastodon on November 18: the domain had disappeared from its NameSilo account, the registrar responsible for codeberg.org. The team said it had not forgotten to renew it, found no suspicious logins in the account history, and saw no activity in the domain history either. According to PrivacyAffairs, Codeberg received no notification email.

The domain's public registry record changed to clientHold at 05:52 UTC, according to PrivacyAffairs. This status prevents the domain from being published in DNS; as a result, browsers and development tools cannot find the server through codeberg.org, even if the underlying infrastructure is still running. The first reports from users unable to resolve the domain arrived at around 07:20 UTC.

Codeberg initially ruled out nonpayment as the cause of an expiration. The domain is registered and paid through July 2028, according to PrivacyAffairs and Altus Intel. The registry also showed clientTransferProhibited, a restriction that prevents transferring the domain to another registrar while the issue remains unresolved.

The organization opened a case with NameSilo. The registrar acknowledged that it had suspended the domain and referred the inquiry to its abuse team, but the reason remained unknown in reports published on November 18. Altus Intel noted the following day that no official response about the cause had yet arrived.

What clientHold made inaccessible

The outage affected the website and Git operations that depend on codeberg.org: cloning repositories, downloading changes, and submitting contributions over HTTPS or SSH. PrivacyAffairs also listed continuous integration services, the container and package registry, documentation, the forum, and the translation service among the affected components.

Not all Codeberg domains stopped working. Codeberg Pages sites hosted at codeberg.page continued to load, because they use a different domain. This distinction did not restore access to repositories or the other services linked to codeberg.org.

The suspension affected projects that use Codeberg to host their development. Linuxiac and Altus Intel mentioned, among others, Forgejo, SysVinit, Genode, OpenRGB, Libreboot, Zig, GNU Guix, Toybox, River, and Gentoo. PrivacyAffairs noted that Zig had moved its project to Codeberg in November 2025 and that Gentoo was working to leave GitHub.

Codeberg considered using codeberg.eu as a temporary workaround, but decided against deploying a quick change. According to Linuxiac, maintaining two domains as a reliable alternative posed challenges involving multi-domain support, SEO, and two-factor authentication. Developers would also have to change their Git remote URLs and other references. Codeberg described this alternative as work that could not realistically be completed in just a few hours.

Forgejo's security update was put on hold

Forgejo is the free software on which Codeberg is built and also runs on self-hosted servers. It had planned to release a security update on November 18, but announced at 07:46 UTC that it could not complete the release because of Codeberg's problems.

“were temporarily publicly accessible as part of the release process”

— Forgejo

The phrase referred to the patches, which had been temporarily visible during the release process. Forgejo did not disclose which vulnerability they fixed or which versions were affected. The delay left administrators without the update while the changes could provide clues about the flaw.

While waiting for the release, Forgejo recommended that users of its built-in SSH server temporarily disable it or block access to it. The setting mentioned is START_SSH_SERVER = true in the [server] section; in Docker, it is usually set through an environment variable. The warning also applies to Forgejo's rootless Docker images, which include that server.

The recommendation does not apply to the system's OpenSSH, which is not covered by this advisory. Disabling the built-in server prevents users from pushing over SSH while the change is in effect, so Forgejo said they can use HTTPS in the meantime. When the update is released, its documentation identifies data.forgejo.org as a mirror for container images if codeberg.org is unavailable.

Partial restoration and a cause still pending

Availability reports changed over the course of the coverage. Linuxiac described the service as inaccessible on November 18 and reported that Codeberg was waiting to hear from NameSilo's abuse team. On November 19, Altus Intel added that the domain delegation had been restored, although DNS cache inertia meant that not all users could see it yet.

This restoration did not clarify why clientHold had been applied or how the domain disappeared from Codeberg's account. PrivacyAffairs noted that NameSilo's help page lists failure to confirm contact details within 15 days—a requirement from ICANN—or a spam, phishing, or malware complaint that results in a suspension during an investigation as common causes. Neither possibility was confirmed as the cause in this case.

The available information also points to no evidence of compromised repositories or an intrusion into Codeberg's infrastructure. The reported incident was the suspension of the domain delegation. At the time the cited reports were published, an explanation from NameSilo and confirmation that codeberg.org was resolving normally for all users were still pending.

Sources: Linuxiac, PrivacyAffairs, Altus Intel