FR24 feeder reported as online, no data uploaded

Specifications

Image hash or version: 1.32.0
Platform: Rocky Linux 9 + Docker CE 26.0.0
Subsystem: x86_64

Expected Behavior

When aircrafts are tracked from FR24 feeder, I should see some uploaded data in my FR24 feeder statistics.

Actual Behavior

I can see in local FR24 feeder Web UI the following information: Aircraft Tracked: 18 Aircraft Uploaded: 9

But no AC uploaded according to logs, and I can't figure out why. The feeder is reported as online on FR24 website, with no data uploaded. Capture d'écran 2024-04-09 103753

No issue on FlightAware feed, aircraft data is properly received by FlightAware. I also check my firewall and I don't see blocked traffic, I can see encrypted data sent to FR24, and replies received.

Some logs:

2024-04-09 08:31:42 | [mlat][i]Stats 5681/197
2024-04-09 08:31:42 | [mlat][i]Pinging the server
2024-04-09 08:31:22 | [mlat][i]Stats 5484/5484
2024-04-09 08:31:22 | [mlat][i]Pinging the server
2024-04-09 08:31:12 | [mlat][i] 3965A5
2024-04-09 08:31:12 | [mlat][i]Received ADS-B time references AC:
2024-04-09 08:30:39 | [mlat][i]Registering MLAT station: SUCCESS [TSync:true,ADSB-VF:true]
2024-04-09 08:30:39 | [mlat][i]Registering MLAT station
2024-04-09 08:30:39 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
2024-04-09 08:30:39 | [mlat][i]MLAT bandwidth reduction active, level 1
2024-04-09 08:30:39 | [mlat][i]Starting MLAT with preconfigured position: 48.90,2.50,194.0
2024-04-09 08:30:39 | [mlat][i]MLAT configuration received, service ENABLED
2024-04-09 08:30:38 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-VALIDATED
2024-04-09 08:30:37 | [reader][i]Configured, processing messages
2024-04-09 08:30:37 | [reader][i]Connected to the receiver, configuring
2024-04-09 08:30:37 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2024-04-09 08:30:33 | [feed][n]working
2024-04-09 08:30:33 | [feed][n]connected via UDP (fd 23)
2024-04-09 08:30:33 | [feed][n]connecting
2024-04-09 08:30:33 | [feed][n]LFPG3@185.218.24.22:8099/UDP
2024-04-09 08:30:33 | 24-04-09 08:31:02.352 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed LFPG3
2024-04-09 08:30:33 | 24-04-09 08:31:02.352 [I][crxstats.cpp:588] [stats]Stats thread started
2024-04-09 08:30:33 | 24-04-09 08:31:02.352 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: LFPG3, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
2024-04-09 08:30:33 | 24-04-09 08:31:02.352 [D][receiver_ac_sender.cpp:141] Stop called on non-running network thread for feed 
2024-04-09 08:30:33 | 24-04-09 08:31:02.352 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed 
2024-04-09 08:30:33 | [feed][c]Timestamps: optional
2024-04-09 08:30:33 | [feed][i]defined 3 servers
2024-04-09 08:30:33 | [feed][i]configuration changed
2024-04-09 08:30:33 | [feed][c]Max range GND: 80.0nm
2024-04-09 08:30:33 | [feed][c]Max range AIR: 350.0nm
2024-04-09 08:30:33 | [feed][i]configuring decoder
2024-04-09 08:30:33 | [feed][d]Fetching configuration
2024-04-09 08:30:33 | [feed][i]Downloading configuration
2024-04-09 08:30:33 | [main][i]Feed Network client started
2024-04-09 08:30:33 | [time][i]Time synchronized correctly, offset -28.436 seconds
2024-04-09 08:31:02 | [time][i]Synchronizing time via NTP
2024-04-09 08:31:01 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://127.0.0.1:30005
2024-04-09 08:31:01 | [mlat][i]Waiting for MLAT configuration
2024-04-09 08:31:01 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2024-04-09 08:31:01 | [reader][i]Initializing reader
2024-04-09 08:31:01 | [main][i]MLAT data feed started
2024-04-09 08:31:01 | [master][i]Starting processing thread
2024-04-09 08:31:01 | [main][i]Reader thread started
2024-04-09 08:31:01 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2024-04-09 08:31:01 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2024-04-09 08:31:00 | 24-04-09 08:31:00.937 [I][http-server.cpp:246] [httpd]Server started, listening on :::8754
2024-04-09 08:31:00 | [main][i]Automatic updates are DISABLED
2024-04-09 08:31:00 | [main][i]DNS mode: PING
2024-04-09 08:31:00 | [main][i]https://www.flightradar24.com
2024-04-09 08:31:00 | [main][i]Copyright 2012-2023 Flightradar24 AB
2024-04-09 08:31:00 | [main][i]Local IP(s): 172.19.0.19,fe80::42:acff:fe13:13
2024-04-09 08:31:00 | [main][i]Running on: debian="11"
2024-04-09 08:31:00 | [main][i]Built on Nov  6 2023 12:51:50 (T202311061248/Linux/static_amd64)
2024-04-09 08:31:00 | [main][i]Version: 1.0.44-0/generic
2024-04-09 08:31:00 | [main][i]FR24 Feeder/Decoder
2024-04-09 08:31:00 |               |___/                                                          
2024-04-09 08:31:00 |                __/ |                                                         
2024-04-09 08:31:00 | \_|    |_||_| \__, ||_| |_| \__||_|   \__,_| \__,_| \__,_||_|  \_____/    |_/
2024-04-09 08:31:00 | | |    | || || (_| || | | || |_ | |  | (_| || (_| || (_| || |  ./ /___\___  |
2024-04-09 08:31:00 | |  _|  | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / /  / /_| |
2024-04-09 08:31:00 | | |_   | | _   __ _ | |__  | |_  _ __  __ _   __| |  __ _  _ __`' / /' / /| |
2024-04-09 08:31:00 | |  ___|| |(_)       | |    | |                  | |            / __  \  /   |
2024-04-09 08:31:00 | ______  _  _         _      _                    _              _____    ___

Steps to Reproduce the Problem

I simply ran the container with FR24 enabled with or without MLAT enabled.

Thom-x / docker-fr24feed-piaware-dump1090