TLEs/Sat Data Not Updating

[Craig]

Hello! Using ver. 1.50 but for some reason the TLEs and All Satellite Data are not updating. Nothing has changed in my setup and SkyRoof has internet access as always. Auto update at start isn't working and manual updating of TLEs and All Sat Data fail when using the "Tools" drop down. Tried multiple restarts of the program and my PC to no avail. I've never encountered this issue since my early adoption of this wonderful program. Thanks!

[Alex VE3NEA]

I have the same issue today. The problem is on the SatNOGS side, here is the error message in the log:

A connection attempt failed because the connected party did not properly respond after a period of time.

[Thomas Schuessler]

If Satnogs is changing to only making available new GP formats, it is possible that the URL that had been used no longer is available. I know CELESTRAK has been removing standard TLE element sets from availability. Another phone application of mine is no longer able to grab current data from them. 

On Aug 20, 2026, at 13:05, Alex VE3NEA <ve3...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "SkyRoof" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skyroof+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/skyroof/be95fb57-4642-4174-bbe5-301e0cf6cde8n%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marcus PY2PLL]

Tested now and worked both TLE only and All Sat Data.

73 Marcus PY2PLL

[Joe Spears AF1E]

I am unable to download TLE or All Satellite Data Skyroof 1.5

Joe AF1E

[Joe Spears AF1E]

SkyRoof / SatNOGS connectivity problem — what I have learned so far

I have been troubleshooting a problem where SkyRoof cannot download satellite data from SatNOGS when my Windows laptop is connected through my Synology RT6600ax router. But does if connected via cell phone.   I have now narrowed the problem down considerably.

Normal home network through Synology

My Synology WAN interface is eth0:

• Router WAN MAC: 90:09:D0:29:7B:45 — confirmed as the factory MAC printed on the router
• Spectrum-assigned public IPv4: 24.181.62.49
• Gateway: 24.181.60.1
• MTU: 1500

From a Windows PC behind the router:

Test-NetConnection 94.130.162.100 -Port 443

results in:

TcpTestSucceeded : False

Ping to 94.130.162.100 does work.

I then SSHed directly into the Synology router and tested from the router itself:

curl -4 -v --connect-timeout 10 https://94.130.162.100/

This also times out, so the problem is not Windows, Wi-Fi, or LAN NAT.

I ran tcpdump on the Synology WAN interface while attempting the connection:

sudo tcpdump -ni eth0 -nn 'host 94.130.162.100 and tcp port 443'

The capture showed the Synology sending repeated TCP SYN packets:

24.181.62.49 → 94.130.162.100:443 [SYN]

but no SYN-ACK or other reply ever returned.

So the Synology is definitely sending the connection attempt onto its WAN interface.

Direct Lenovo-to-Spectrum-modem test

I then disconnected the Synology and connected my Lenovo laptop directly to the Spectrum cable modem.

The Lenovo Ethernet adapter is:

• ASIX USB Gigabit Ethernet
• MAC: C8:A3:62:2C:52:C5

Spectrum gave the Lenovo:

• IPv4: 71.14.127.172
• Gateway: 71.14.120.1

Now:

Test-NetConnection 94.130.162.100 -Port 443

returned:

TcpTestSucceeded : True

And:

curl.exe -4 -v --connect-timeout 10 https://db.satnogs.org/

worked and downloaded the SatNOGS web page normally.

So at this point I have:

Synology / Spectrum address 24.181.62.49 → SatNOGS TCP 443 fails

Lenovo directly connected / Spectrum address 71.14.127.172 → SatNOGS TCP 443 works

This makes it look increasingly like the problem is associated with the Spectrum IP address/route being assigned when the Synology is connected, rather than with SkyRoof itself, DNS, Windows, or basic Synology LAN routing.

My next test will be to clone the Lenovo Ethernet MAC (C8:A3:62:2C:52:C5) onto the Synology WAN, power-cycle the Spectrum modem, and see whether Spectrum assigns the Synology the same 71.14.x.x address/route that works with the Lenovo.

If the Synology then receives the Lenovo's working address and SatNOGS starts working, that would be strong evidence of an ISP routing/filtering issue associated with the 24.181.62.x path.

I will post the results of that test when I have them.

I would also be interested to know if anyone else using SkyRoof/SatNOGS on Spectrum has seen a situation where 94.130.162.100 responds to ping but TCP port 443 silently times out from one Spectrum public-IP range while working normally from another.

Joe AF1E