Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
omarchy-network-speedtest fails with 403: fast.com API is geo-blocked outside US
Reported by Dxraka · filed Sep 14, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #11166 (R-725). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Bug
omarchy-network-speedtest down (invoked from the launcher's "Тест скорости сети" / network speed test menu item) always fails. The panel shows "Failed to fetch speed test endpoints" and the test never runs.
Root cause
/usr/share/omarchy/bin/omarchy-network-speedtest depends on the Netflix fast.com API:
fast_api_url="https://api.fast.com/netflix/speedtest/v2?https=true&token=$fast_token&urlCount=$url_count"The fast.com API returns HTTP 403 for users outside the US (confirmed from Russia). Netflix no longer operates its Open Connect CDN / fast.com in many regions, so the endpoint is permanently unreachable there regardless of the token. This makes the built-in speed test unusable for a large share of non-US users.
Repro
$ curl -s -o /dev/null -w "%{http_code}" "https://api.fast.com/netflix/speedtest/v2?https=true&token=YXNkZmFzZGxmbnNkYWZoYXNkZmhrYWxm&urlCount=3"
403
$ omarchy-network-speedtest down
Failed to fetch speed test endpoints (exit 1)Expected: speed test runs.
Suggested fix
Fall back to a geo-neutral speed test backend, e.g. Cloudflare https://speed.cloudflare.com/__down?bytes=N (download) + POST /__up (upload), which returns HTTP 200 from blocked regions and supports both directions. Prefer one backend, fall back to another if the first fails (e.g. try fast.com first, then Cloudflare).
Environment
- Omarchy: 4.0.3-1
- Arch Linux
- Task can reproduce. System diagnostics: n/a (no
omarchy debugcommand in 4.0.3)
View raw text
## Bug
`omarchy-network-speedtest down` (invoked from the launcher's "Тест скорости сети" / network speed test menu item) always fails. The panel shows "Failed to fetch speed test endpoints" and the test never runs.
## Root cause
`/usr/share/omarchy/bin/omarchy-network-speedtest` depends on the Netflix fast.com API:
```
fast_api_url="https://api.fast.com/netflix/speedtest/v2?https=true&token=$fast_token&urlCount=$url_count"
```
The fast.com API returns **HTTP 403** for users outside the US (confirmed from Russia). Netflix no longer operates its Open Connect CDN / fast.com in many regions, so the endpoint is permanently unreachable there regardless of the token. This makes the built-in speed test unusable for a large share of non-US users.
## Repro
```
$ curl -s -o /dev/null -w "%{http_code}" "https://api.fast.com/netflix/speedtest/v2?https=true&token=YXNkZmFzZGxmbnNkYWZoYXNkZmhrYWxm&urlCount=3"
403
$ omarchy-network-speedtest down
Failed to fetch speed test endpoints (exit 1)
```
Expected: speed test runs.
## Suggested fix
Fall back to a geo-neutral speed test backend, e.g. Cloudflare `https://speed.cloudflare.com/__down?bytes=N` (download) + `POST /__up` (upload), which returns HTTP 200 from blocked regions and supports both directions. Prefer one backend, fall back to another if the first fails (e.g. try fast.com first, then Cloudflare).
## Environment
- Omarchy: 4.0.3-1
- Arch Linux
- Task can reproduce. System diagnostics: n/a (no `omarchy debug` command in 4.0.3)Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.