Station 4924 (Wroclaw) — TCP/443 timeout to network.satnogs.org, ICMP OK

Generic
,
1

Hi everyone,

I’m having persistent connectivity problems between my ground station and SatNOGS Network. The SatNOGS client container runs fine locally, but without a workaround the station stays Offline because it cannot reach the Network API.

Station Name: Wroclaw Ground Station (#4924)
Client: satnogs-client 2.1.2 (Docker / satnogs-setup)
Hardware: Raspberry Pi 5, RTL-SDR Blog v3
Location: Wrocław, Poland

Public IPv4 (home connection): 185.72.184.10

Symptoms

  • Station shows Offline on the Network (is_connected: false).
  • satnogs-client logs repeat errors such as:
    • Fetching jobs from network failed
    • HTTPSConnectionPool(host='network.satnogs.org', port=443): ... Failed to establish a new connection (sometimes [Errno 101] Network is unreachable from inside the container).
  • Observations cannot be scheduled/uploaded while this persists.

What works / what doesn’t

From the same LAN (Pi and other devices):

Test Result
General internet (e.g. https://github.com) OK
DNS for network.satnogs.org → 94.130.162.100 OK
ping 94.130.162.100 OK (replies, low packet loss)
TCP 443 (and 80) to 94.130.162.100 / https://network.satnogs.org/ Timeout (no TCP handshake)

So: ICMP works, but HTTPS to the SatNOGS Network host does not from my home IP.

System time looks fine (timedatectl: clock synchronized, NTP active).

Workaround

If I enable Cloudflare WARP on the Pi (warp-cli connect, mode WARP), then:

  • curl https://network.satnogs.org/api/stations/4924/ succeeds,
  • the client can reach /api/jobs/...,
  • the station goes Online again.

That suggests the problem is specific to my source IP / path to srv01.libre.space (94.130.162.100), not a broken SatNOGS install.

Request

Could someone on the SatNOGS / Libre Space side please check whether 185.72.184.10 is blocked, rate-limited, or otherwise filtered (e.g. fail2ban) on the Network infrastructure?

I’m not aware of abusive API usage from this station; normal client polling plus my own scheduling/upload scripts. If something from this IP triggered a block, I’m happy to adjust rates or fix whatever caused it.

I’d prefer a proper fix (unblock or guidance) so I don’t have to rely on WARP long term.

Thanks in advance — happy to provide more logs or tests if needed.

73,
karlopalazzo / Station #4924

PS: Similar reports: 15455, 15327.

1 Like
2

Checking and I’ll reply you in pm

3

I acutally have a similar problem connecting to network.satnogs.org to access the API. It just runs into an timeout. Has worked month without problems until 2026-10-08 03:19:04.

Any idea what might be the problem?

The vserver seems to use 2a00:1c38:1:80:511c:e9a1:: as the outgoing IP.

Thanks a lot!

1 Like
4

Checking and I’ll reply you in pm