Messages

Heads up that Mono's update server is down for everyone, not just me.

opnsense.mono.si accepts TCP on 443 but answers every ClientHello with a fatal
TLS alert 80 (internal_error) before ServerHello — no certificate is ever
presented. Port 80 is fine and returns 308 -> https with "Server: Caddy", so the
web server is up and only TLS termination is broken.

Code Select Expand

# openssl s_client -connect opnsense.mono.si:443 -servername opnsense.mono.si </dev/null
...tlsv1 alert internal error...SSL alert number 80
---
no peer certificate available
---
SSL handshake has read 7 bytes and written 322 bytes
---
New, (NONE), Cipher is (NONE)

Effect on a Gateway DK running 26.1.10 (aarch64): the changelog fetch fails with
"Authentication error" and both the OPNsense and MonoGateway repo catalogues fail
with "An error occurred while fetching package: No error" (that string just means
no HTTP status was ever received - it died in TLS), so no updates at all.

Not client-specific: reproduced from FreeBSD 14/OpenSSL, macOS/LibreSSL, Chromium
and Python/OpenSSL, and an SSL Labs scan reports "No certificates found" with zero
supported protocols. IPv6 (2a01:4f8:1c1a:6d1c::1) is unreachable too.

First confirmed 2026-09-07 02:53 UTC in we-are-mono/docs issue #20, still failing
now. There's no user-side workaround - http:// just 308s back into the broken
listener, and no other mirror carries the mono flavour.

Maurice, since you maintain the Mono update server: could you take a look at the
Caddy cert / ACME state for that host?