I can reproduce it on my M1 Macbook air using Safari, which might be relevant if you try to verify.
When I am on the ci.codeberg.org pages and click on "Docs" in the header, I get (correctly) sent to https://docs.codeberg.org/ci/ but that alwas comes back with
503 Service Unavailable
No server is available to handle this request.
After that I sometimes (not always) get extreme long reload times on other codeberg pages, forcing me to restart Safari. After that restart everything is fine again, until I do the same.
Could this be some sort of rate limiting on the codeberg side? Maybe caused by these Apple anti-tracking features that are enabled by default which could cause traffic to look suspicious to whatever network traffic checking is done?
I'm a bit at a loss because it's a rather weird problem. So if noone else can reproduce this behaviour, just file it as "hm, whatever" ;)
J
I can reproduce it on my M1 Macbook air using Safari, which might be relevant if you try to verify.
When I am on the ci.codeberg.org pages and click on "Docs" in the header, I get (correctly) sent to https://docs.codeberg.org/ci/ but that alwas comes back with
```
503 Service Unavailable
No server is available to handle this request.
```
After that I sometimes (not always) get extreme long reload times on other codeberg pages, forcing me to restart Safari. After that restart everything is fine again, until I do the same.
Could this be some sort of rate limiting on the codeberg side? Maybe caused by these Apple anti-tracking features that are enabled by default which *could* cause traffic to look suspicious to whatever network traffic checking is done?
I'm a bit at a loss because it's a rather weird problem. So if noone else can reproduce this behaviour, just file it as "hm, whatever" ;)
J