Hi all,
Reaching out because my Hetzner server (IP 168.119.175.82, IPv6
2a01:4f8:1c1c:ff7::1) is being refused TCP connections to
apps.nextcloud.com on both v4 and v6, while every other Nextcloud-related
host works fine. The pattern strongly suggests a fail2ban-style IP block.
I run five production Nextcloud instances on this server (NC 31.0.14, all
patched). Today’s planned NC 31 → 32 major upgrade had to be aborted
because the upgrader cannot determine app compatibility without
apps.nextcloud.com.
Reachability test from the server, all over IPv4:
github.com HTTP 200 in 0.109s
nextcloud.com HTTP 200 in 0.096s
mirror.hetzner.com HTTP 200 in 0.128s
download.nextcloud.com HTTP 200 in 0.082s
docs.nextcloud.com HTTP 200 in 0.135s
apps.nextcloud.com HTTP 000 in 0.025s ← TCP refused
Verbose curl confirms TCP RST, not DNS or routing:
- Trying 65.21.231.50:443…
- connect to 65.21.231.50 port 443 failed: Connection refused
- Failed to connect to apps.nextcloud.com port 443 after 25 ms
Same behaviour on IPv6 (2a01:4f9:6a:1de8::2).
Likely cause: opening Admin/Overview a few times, plus regular update
checks from five instances on one IP, plus a single one-off pre-flight
script run today (~70 API calls within ~2 minutes). Similar reports:
Open `serverinfo` tab provokes ip ban by apps.nextcloud.com and /t/203184 describe the same trigger.
Mitigation already in place on my side:
- appstoreenabled = false on all five instances
- No further automated requests to apps.nextcloud.com
Could a moderator please verify whether 168.119.175.82 (and the v6 prefix
2a01:4f8:1c1c:ff7::/64) is currently blocked and, if so, request an
unban? I’m happy to keep the appstore disabled for now and only re-enable
once cleared.
Thanks for your time,
Thomas