As you probably noticed, our domain codeberg.org is entirely unreachable. It was registered with namesilo and entirely disappeared from our account. We’re waiting for their customer support to investigate the situation. No, we didn’t forget to renew. There are no suspicious logins in the login history. There is no entry about the situation in the account’s domain history. We’ll try setting up a workaround on our codeberg.eu domain ASAP.

Update: We have received the confirmation that our domain was suspended and our case got forwarded to the abuse team. We’re still waiting for a final decision.

We decided not to enable codeberg.eu as a quick workaround: There are several technical difficulties (e.g. multi-domain support, SEO, Two-Factor-Authentication). The benefit of a temporary workaround compared to the effort is quite low (updating all the Git remotes and other references). We hear you about domain resiliency and independence from a single point of failure. However, activating a second domain is a long-term project and nothing we can pull of within a few hours.

https://social.anoxinon.de/@codebergstatus/117636437840688845

    • redjard@reddthat.com
      link
      fedilink
      arrow-up
      2
      ·
      7 hours ago

      That sounds reasonable. I checked some old backups and there’s not much else (at least in this location), but also services, protocols and networks, which are also shared with linux. (On linux, services lets you define the name given to certain ports, so e.g. when lsof -i :22000 would usually show entries with :22000, you could then add syncthing tcp/22000 \nsyncthing udp/22000 and hboth uselsof -i :syncthing or also with any lsof results see that port show up as :syncthing.
      Btw. the same is true with ips and names in hosts, so if you have local static ips it can be nice to give devices entries in hosts just for that, to make connections more readable.