Conversation

We are currently having network issues. We are able to connect to our server's onboard recovery system, but the access is slow and unreliable.

We'll keep you updated.

1
2
0

A quick glimpse at the monitoring (until network access went away) indicated that it's either a grave network misconfiguration or an active DDoS going on. It looked like an inrush of junk data at the maximum link speed of our server.

1
1
0

We are waiting for our provider to help us out with our current situation.

1
1
0

Our provider confirmed an incoming DDoS. We have got access to our systems and currently considering next steps.

4
4
0
@Codeberg Waves of support from fellow git server admins!
0
0
11
@Codeberg againë

Forgive me if I'm stating a commonly asked question but why don't you guys use cloud flare. You just host code
1
0
0

@kirby cloudFlare is a privacy nightmare for many. And it costs a lot of $$$, see https://fosstodon.org/@drewdevault/111739234229534233

0
0
0

@Codeberg Hi, is there any secondary registry that can be used?
Good luck!

0
0
0

For your convenience, we have temporarily established a way to access Codeberg. This is heavily constrained and might go back offline at any time.

mostly working:
codeberg.org HTTPS (Read/Write)

not working:
SSH, CI, Weblate, Pages and all the rest.

2
0
0

SSH is also back. We expect overall performance to be rather low, though.

Looks like some of you are already back. (At least the regular spam is, too)

1
0
0

Just for clarification: Due to our current networking constraints, there are no webhooks and email notifications at this time.

We are optimistic to have a plan to restore services early afternoon (European time).

We are also looking forward to restoring the Codeberg logo (it is currently missing in some places 😂)

3
1
0

@Codeberg I wonder why? thanks for the hard work!

0
0
0

We (partially) restored service for:

Fully working:
- E-Mail

IPv6-only:
- Webhooks
- Codeberg Pages
- Weblate https://translate.codeberg.org
- static pages (blog, docs, the Codeberg logo)

IPv6-only and limited functionality:
- Woodpecker CI (should accept Webhooks, but no actual builds are running: Due to IPv6-only, the builds will not connect to GitHub and other prominent sources for dependencies, there is likely no use in having most builds fail due to this)

1
2
0

In the past minutes, we alternately broke IPv4 and IPv6 support - for equality.

IPv4 access to all services is now proxied. This should bring most functionality back.

Still unavailable:
- CI builds
- Codeberg Pages for people who hardcoded the A records instead of using ALIAS/CNAME.

We are working on restoring the last pieces.

0
1
0