MLAT no connection | Official ADS-B Exchange Group | Page 1

teal wigeon Mar 21, 2025, 10:34 AM

#

Hi, is there a problem with MLAT servers at the moment? My receiver has been up for years, but in recent days MLAT won't connect any more:

Connected to multilateration server at feed.adsbexchange.com:64590, handshaking
Lost connection to feed.adsbexchange.com:64590
Reconnecting in 10.0 seconds

Normal Beast is fine, other ADS-B platforms (including MLAT there) are fine.

Is this a server issue?

void dove Mar 21, 2025, 11:03 AM

#

I've not heard of anyone else having issues. Just checked mine, and it's been stable other than when I had to reboot my firewall a few days ago.

teal wigeon Mar 21, 2025, 2:12 PM

#

Thank you.

rotund jasper Mar 21, 2025, 2:38 PM

#

teal wigeon Thank you.

i've seen this before, i'd assume server issue if the beast connection is working.

#

Dseven might be on another mlat server which works while your region is having issues.
or it's simply some weird server misconfiguration.

teal wigeon Mar 22, 2025, 10:32 AM

#

I just noticed something odd: There used to be a small number of other receivers close to me (< 10 km). They are no longer listed on ADSBx "MLAT Feeder Map" either. Other receivers that are a bit farther away (as in 50-100km, though still in the same region) do appear.

I am almost exactly on the border between regions "Europe - Western 2 (10)" and "Europe - Western 4 (11). I should be part of the latter.

Is there maybe a new "border corridor" where a receiver can't be placed by the system or something? Or a server name change?

void dove Mar 22, 2025, 10:42 AM

#

AFAIK the same front-end servers are used globally - I've checked various regions, and feed/feed1/feed2 always resolve to 34.218.254.209 and 54.244.22.71. I don't have any visibility into how regions are implemented behind that. Maybe it's possible that you're (now) falling into a gap between regions. Maybe @plucky barn could take a look (next week)...

teal wigeon Mar 22, 2025, 10:53 AM

#

Thanks, I appreciate it.

One more thing: In addition to the close receivers that used to be on the map and are now missing, a number of others still listed now show zero peers. This includes some that I seem to remember were well connected in the past.

@plucky barn Please feel free to DM me if you need any more information.

crisp tinsel Mar 22, 2025, 6:47 PM

#

A lack of peers would preclude you doing MLAT so it's probable that the nearby receivers that no longer exist are the cause of your issue.

void dove Mar 22, 2025, 6:51 PM

#

I wouldn't expect a lack of peers to cause failure to maintain a connection with the server.

teal wigeon Mar 22, 2025, 8:20 PM

#

Update: For the first time in a few days (at least since I noticed the issue) all my MLAT connections are now up again at this time. Did you change anything on the server side?

My "close neighbours" are still not there (who knows if they still exist in the first place), but my own receiver is back to its usual sync state (about 75 peers.)

teal wigeon Mar 23, 2025, 10:01 AM

#

Spoke too soon: Out again this morning. Other network's MLAT is still up.

silent eagle Mar 24, 2025, 4:22 PM

#

I highly doubt you can fall in a gap between MLAT servers unless something is really screwed up. I’m not aware of any server issues or changes.

flint bone Mar 24, 2025, 10:15 PM

#

For 2-3 days, my MLAT has been AWOL too. It will connect to a few people, but not enough to let is show as a good receiver. But, Status page show MLAT connected with green "Feed ok"

crisp tinsel Mar 25, 2025, 1:54 AM

#

flint bone For 2-3 days, my MLAT has been AWOL too. It will connect to a few people, but n...

You appear to have a timeout penalty on your feeder. This could be low voltage or incorrectly/inaccurately set lat/long/alt.

flint bone Mar 25, 2025, 2:19 AM

#

My loation entered has been exactly the same for 5 years, and voltage appears normal on config page

crisp tinsel Mar 25, 2025, 2:22 AM

#

It's still worth double checking your location, especially as from recent messages you seem to have set up a new feeder which was showing alongside an older one of the same name

#

You could easily have made a typo when configuring it

flint bone Mar 25, 2025, 2:28 AM

#

All good there, when I click on "Verify Coordinates", it puts the map right on my house and elevation is correct too

teal wigeon Mar 29, 2025, 7:57 PM

#

I still can't connect to ADSBx's MLAT server(s). Two other networks have no problem connecting to their servers (ADSB.fi and Airplanes.live). It's just ADSBx that's having issues. Is there anything else I (or you, Admins) could check?

#

Mar 29 20:58:25 adsbexchange-mlat[13960]: Connected to multilateration server at feed2.adsbexchange.com:64590, handshaking
Mar 29 20:58:27 adsbexchange-mlat[13960]: Receiver: disconnected 0.0 msg/s received 0.0 msg/s processed (0%)
Mar 29 20:58:27 adsbexchange-mlat[13960]: Server: handshaking 0.0 kB/s from server 0.0 kB/s to server
Mar 29 20:58:27 adsbexchange-mlat[13960]: Results: 0.0 positions/minute
Mar 29 20:58:27 adsbexchange-mlat[13960]: Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Mar 29 20:59:00 adsbexchange-mlat[13960]: Lost connection to feed2.adsbexchange.com:64590
Mar 29 20:59:00 adsbexchange-mlat[13960]: Reconnecting in 2.9 seconds
Mar 29 20:59:04 adsbexchange-mlat[13960]: Connected to multilateration server at feed1.adsbexchange.com:31090, handshaking
Mar 29 21:00:04 adsbexchange-mlat[13960]: Disconnecting from feed1.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds
Mar 29 21:00:04 adsbexchange-mlat[13960]: Connected to multilateration server at feed2.adsbexchange.com:64590, handshaking

... looks like the MLAT client lost the connection to readsb, is that possible?

teal wigeon Mar 29, 2025, 8:25 PM

#

More info: I believe the trouble started after I installed the airplanes.live client. Are there any known compatibility issues?

rotund jasper Mar 29, 2025, 11:02 PM

#

if there was an issue it would be a port that prevent mlat-client startup being used already.
but that would show in the log.
otherwise it's separate installs.

#

that's just adsbexchange server issues what you see.

teal wigeon Mar 30, 2025, 12:56 PM

#

Ok. Thank you; at least I know I don't need to search any further on my receiver then.

teal wigeon Apr 11, 2025, 7:30 PM

#

Could someone on the server side please look into this issue?
Over the last few days, my MLAT stayed connected. Just now it shows disconnected again.
If this can't be resolved I'm not sure if it's worth to continue feeding ADSBx. MLAT seems to be the main advantage of running a large number of nodes.

cold hemlock Apr 11, 2025, 10:33 PM

#

You might try posting this in tech-support and see if you get any better results.

teal wigeon Apr 12, 2025, 8:36 AM

#

Will do; thanks.

torpid field Apr 16, 2025, 9:55 PM

#

for what it is worth, i just updated my docker container for adsbx today, and have started having the same issue.

[mlat-client] Lost connection to feed.adsbexchange.com:31090
[mlat-client] Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
[mlat-client] Connection retries will continue, further messages about this connection will be suppressed for 15 minutes

#

its definitely not a feeder/signal issue, as i am feeding other destinations MLAT data just fine

torpid field Apr 17, 2025, 5:34 PM

#

this recovered on its own overnight for me

fiery schooner Apr 19, 2025, 4:30 PM

#

same problem today make new mlat and have same problem, can't connect to server

#MLAT no connection