shoginn / flightradar24

Docker container for ADS-B - This is the flightradar24.com component

About Me

I'm Scott, a technology enthusiast passionate about automation and making things easier. While I enjoy software development, my passion lies in using technology to streamline processes and improve efficiency. I have experience working with various programming languages and technologies and always look for new challenges and opportunities to grow my skills.

In addition to my interest in automation, I'm passionate about DevOps and its role in modern software development. DevOps is essential for building high-quality software quickly and efficiently, and I'm always looking for ways to improve my DevOps skills and knowledge.

Contact Me

If you'd like to get in touch, start a Discussion. I'm always happy to chat with other technology enthusiasts and discuss new ideas.

Clever Links

In my free time, I enjoy exploring new topics and learning about different areas of technology. You can check out my Wiki for some of my favorite resources and links.

My Certifications

I'm proud to have earned several certifications demonstrating my expertise in various technology areas. Here are a few of my most recent certifications:

My Certificates (Training)

Several training courses have helped me develop my skills and knowledge in various technology areas. Here are a few of my most recent training certificates, which can be found here

GitHub Stats

You can check out my GitHub stats below to see some of my recent work. These stats show the number of contributions I've made to my repositories and the top programming languages I've used in my projects.

Trophies

---

flightradar24's Issues

Docker container exits with code 139

On Unraid 6.8.0 using shoginn/flightradar24:latest (amd64) the container exits/stops with code 139 after startup, which I think is a segmentation fault. The log file for the container:

Waiting for dump1090 to start up
Waiting for dump1090 to start up
Creating the base ini file
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: feed.flightradar24.com
Address: 104.17.46.52
Name: feed.flightradar24.com
Address: 104.17.43.52
Name: feed.flightradar24.com
Address: 104.17.44.52
Name: feed.flightradar24.com
Address: 104.17.45.52
Name: feed.flightradar24.com
Address: 104.17.42.52

PING feed.flightradar24.com (104.17.42.52) 56(84) bytes of data.
64 bytes from 104.17.42.52 (104.17.42.52): icmp_seq=1 ttl=55 time=4.40 ms

--- feed.flightradar24.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 4.403/4.403/4.403/0.000 ms

19-12-17 09:36:46.824 [E] Local time: 2019-12-17 09:36:46 -0500
19-12-17 09:36:46.824 [E] GMT+0 time: 2019-12-17 14:36:46 -0500
19-12-17 09:36:46.824 [E] Your machine should be set as GMT+0 time zone!
warning | Time zone is not set to GMT+0

2019-12-17 09:36:46 | ______ _ _ _ _ _ _____ ___
2019-12-17 09:36:46 | | ___|| |(_) | | | | | | / __ \ / |
2019-12-17 09:36:46 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2019-12-17 09:36:46 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2019-12-17 09:36:46 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2019-12-17 09:36:46 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2019-12-17 09:36:46 | __/ |
2019-12-17 09:36:46 | |___/
2019-12-17 09:36:46 | [main][i]FR24 Feeder/Decoder
2019-12-17 09:36:46 | [main][i]Version: 1.0.24-5/generic

2019-12-17 09:36:46 | [main][i]Built on Oct 30 2019 07:23:36 (static-i386_amd64-builds-and-macos-dump1090-update-c308dae.git/Linux/amd64)
2019-12-17 09:36:46 | [main][i]Running on: debian9
2019-12-17 09:36:46 | [main][i]Local IP(s): 172.17.0.24
2019-12-17 09:36:46 | [main][i]Copyright 2012-2019 Flightradar24 AB
2019-12-17 09:36:46 | [main][i]https://www.flightradar24.com
2019-12-17 09:36:46 | [main][i]DNS mode: LIBC
2019-12-17 09:36:46 | [main][i]Automatic updates are DISABLED
2019-12-17 09:36:46 | info | [httpd]Server started, listening on 0.0.0.0:8754
2019-12-17 09:36:46 | [e]PacketSenderConfiguration::fetch_config(): Unable to fetch configuration for yoda receiver
2019-12-17 09:36:46 | TLSConnection: Error: No such file or directory. Is certificate present under:

2019-12-17 09:36:46 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2019-12-17 09:36:46 | [main][i]Reader thread started
2019-12-17 09:36:46 | [master][i]Starting processing thread
2019-12-17 09:36:46 | [reader][i]Initializing reader
2019-12-17 09:36:46 | [reader][i]Connecting to unknown receiver via (tcp://192.168.0.xxx:30005)
2019-12-17 09:36:46 | [main][i]MLAT data feed started
2019-12-17 09:36:46 | [mlat][i]Waiting for MLAT configuration
2019-12-17 09:36:46 | [reader][i]Connected to the receiver, configuring
2019-12-17 09:36:46 | [reader][i]Configured, processing messages
2019-12-17 09:36:47 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
2019-12-17 09:36:47 | [time][i]Synchronizing time via NTP
2019-12-17 09:36:48 | [time][i]Time synchronized correctly, offset +0.002 seconds
2019-12-17 09:36:48 | [main][i]Feed Network client started
2019-12-17 09:36:48 | [feed][i]Downloading configuration
2019-12-17 09:36:48 | [feed][d]fetching configuration
2019-12-17 09:36:48 | [reader][i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
2019-12-17 09:36:48 | [time][i]Time synchronized correctly, offset +0.002 seconds
2019-12-17 09:36:48 | [main][i]Feed Network client started
2019-12-17 09:36:48 | [feed][i]Downloading configuration
2019-12-17 09:36:48 | [feed][d]fetching configuration
2019-12-17 09:36:48 | [reader][i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
2019-12-17 09:36:48 | [feed][i]configuring decoder
2019-12-17 09:36:48 | [feed][c]Max range AIR: 350.0nm
2019-12-17 09:36:48 | [feed][c]Max range GND: 100.0nm
2019-12-17 09:36:48 | [feed][i]configuration changed
2019-12-17 09:36:48 | [feed][i]defined 3 servers
2019-12-17 09:36:48 | [feed][c]Timestamps: optional
2019-12-17 09:36:48 | info | [stats]Stats thread started
2019-12-17 09:36:48 | info | Stopping ReceiverACSender threads for feed
2019-12-17 09:36:48 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: KPDK39, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
2019-12-17 09:36:48 | info | Network thread connecting to 185.218.24.22:8099 for feed KPDK39
2019-12-17 09:36:48 | [feed][n][email protected]:8099/UDP
2019-12-17 09:36:48 | [feed][n]connecting
2019-12-17 09:36:48 | [feed][n]connected via UDP (fd 26)
2019-12-17 09:36:48 | [feed][i]Feed connected
2019-12-17 09:36:48 | [feed][n]working
2019-12-17 09:36:48 | [mlat][i]MLAT configuration received, service ENABLED
2019-12-17 09:36:48 | [mlat][i]Starting MLAT with preconfigured position: xx.xx,-xx.xx,1026.0
2019-12-17 09:36:48 | [mlat][i]MLAT bandwidth reduction active, level 1
2019-12-17 09:36:48 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788

I have replaced my ip address, feeder key, and mlat coordinates with with x's.

The run command executed by unraid:

docker run -d --name='shoginn-flightradar24' --net='bridge' --log-opt max-size='10m' --log-opt max-file='3' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'FR24FEED_KEY'='xxxxxxxxxxx' -e 'DUMP1090_SERVER'='192.168.0.xxx' -p '8775:8754/tcp' 'shoginn/flightradar24:latest' 
ac524abcfb9e0a32b5aa937026e4eb2f5f3980b5becc3086f829ab7b7b410707

FYI I have no issues running the dump1090 docker as well as the flightaware docker, which connects without problem.

I will attempt to replicate this on another machine today, hopefully.

dump1090 container variables for server/port should be user-defined

When they are hardcoded it requires the user to setup a DNS entry on the host machine in order for dump1090:30005 to point to whatever IP they are using for the dump1090 container

No Connection To dump1090

I have your dump1090 container running with port 30005 exposed. The logs show that it does find my RTL-SDR device.

I am using your containers on Unraid and my problem is that both the flightaware and flightradar24 containers are unable to connect to the dump1090 container. the logs show that they are unable to resolve dump1090. I verified that it is the correct name of my container.

I'm not sure where to begin troubleshooting from here. I tried adding an entry to my /etc/hosts file for dump1090 to the LAN IP of the server, but that did not help.

Any guidance would be appreciated.

Here is the relevant log for flightradar24:

2019-10-02 09:30:33 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:33 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:38 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:38 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:43 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:43 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:43 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:43 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:48 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:48 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:53 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:53 | [reader][e]Could not connect to tcp://dump1090:30005
2019-10-02 09:30:58 | [reader][i]Connecting to Beast receiver via (tcp://dump1090:30005)
2019-10-02 09:30:58 | [reader][e]Could not connect to tcp://dump1090:30005

Here it is for flightaware:

mlat-client(25): Reconnecting in 30.0 seconds
Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr dump1090 --net-bo-port 30005 --stdout --lat 28.043 --lon -97.226
Started faup1090 (pid 32) to connect to the ADS-B data program at dump1090/30005
faup1090(32): faup1090: failed to connect to dump1090:30005 (is dump1090 running?): can't resolve dump1090: Name or service not known

lost connection to the ADS-B data program at dump1090/30005 via faup1090
faup1090 exited with EXIT 1
will reconnect to the ADS-B data program at dump1090/30005 in 30 seconds
mlat-client(25): Connection to dump1090:30005 failed: [Errno -2] Name or service not known

flightradar24 container not starting up / crashing

Hi,

first of all: thanks for maintaining these projects, they are pretty much exactly what i am looking for.

I'd like to use dump1090, flightradar24 and flightaware. While flightaware works fine (and therefore I assume dump1090 also works correctly), the log of flightradar24 just shows:

...
PING feed.flightradar24.com(2606:4700::6811:2d34 (2606:4700::6811:2d34)) 56 data bytes
--- feed.flightradar24.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
Waiting for dump1090 to start up
eating the base ini file
Server:		192.168.1.2
Address:	192.168.1.2#53
Non-authoritative answer:
Name:	feed.flightradar24.com
Address: 104.17.44.52
Name:	feed.flightradar24.com
Address: 104.17.43.52
Name:	feed.flightradar24.com
Address: 104.17.42.52
Name:	feed.flightradar24.com
Address: 104.17.46.52
Name:	feed.flightradar24.com
Address: 104.17.45.52
PING feed.flightradar24.com(2606:4700::6811:2e34 (2606:4700::6811:2e34)) 56 data bytes
--- feed.flightradar24.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
Waiting for dump1090 to start up
eating the base ini file
Server:		192.168.1.2
Address:	192.168.1.2#53
Non-authoritative answer:
Name:	feed.flightradar24.com
Address: 104.17.46.52
Name:	feed.flightradar24.com
Address: 104.17.45.52
Name:	feed.flightradar24.com
Address: 104.17.44.52
Name:	feed.flightradar24.com
Address: 104.17.43.52
Name:	feed.flightradar24.com
Address: 104.17.42.52
PING feed.flightradar24.com(2606:4700::6811:2a34 (2606:4700::6811:2a34)) 56 data bytes
--- feed.flightradar24.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
Waiting for dump1090 to start up
eating the base ini file
Server:		192.168.1.2
Address:	192.168.1.2#53

... and so on ...

Any hints where to look at? It seems the flightradar ping goes wrong, however that's before the actual FR24 banner from the feeder.

Thanks for any ideas.

Kind regards
Christian

TLSConnection: Error: No such file or directory. Is certificate present under:

Hi current version keeps crashing

ErrorWarningSystemArrayLogin

Waiting for dump1090 to start up
Creating the base ini file
Server: 192.168.1.254
Address: 192.168.1.254#53

Non-authoritative answer:
Name: feed.flightradar24.com
Address: 104.17.44.52
Name: feed.flightradar24.com
Address: 104.17.45.52
Name: feed.flightradar24.com
Address: 104.17.43.52
Name: feed.flightradar24.com
Address: 104.17.46.52
Name: feed.flightradar24.com
Address: 104.17.42.52

PING feed.flightradar24.com (104.17.42.52) 56(84) bytes of data.
64 bytes from 104.17.42.52 (104.17.42.52): icmp_seq=1 ttl=58 time=41.5 ms

--- feed.flightradar24.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 41.522/41.522/41.522/0.000 ms

2020-02-06 22:40:56 | ______ _ _ _ _ _ _____ ___
2020-02-06 22:40:56 | | || |() | | | | | | / __ \ / |
2020-02-06 22:40:56 | | | | | _ __ _ | |_ | |_ _ __ __ _ | | __ _ _ ' / /' / /| | 2020-02-06 22:40:56 | | _| | || | / _ || ' \ | || '|/ _ | / _ | / _` || '| / / / /| |
2020-02-06 22:40:56 | | | | || || (| || | | || |_ | | | (| || (| || (| || | ./ /__ |
2020-02-06 22:40:56 | _| |||| _, ||| || _||| _,| _,| _,||| ___/ |/
2020-02-06 22:40:56 | / |
2020-02-06 22:40:56 | |/
2020-02-06 22:40:56 | [main][i]FR24 Feeder/Decoder
2020-02-06 22:40:56 | [main][i]Version: 1.0.24-5/generic

2020-02-06 22:40:56 | [main][i]Built on Oct 30 2019 07:23:36 (static-i386_amd64-builds-and-macos-dump1090-update-c308dae.git/Linux/amd64)
2020-02-06 22:40:56 | [main][i]Running on: debian9
2020-02-06 22:40:56 | [main][i]Local IP(s): 192.168.1.12 192.168.122.1 172.17.0.1
2020-02-06 22:40:56 | [main][i]Copyright 2012-2019 Flightradar24 AB
2020-02-06 22:40:56 | [main][i]https://www.flightradar24.com
2020-02-06 22:40:56 | [main][i]DNS mode: LIBC
2020-02-06 22:40:56 | [main][i]Automatic updates are DISABLED
2020-02-06 22:40:56 | info | [httpd]Server started, listening on 0.0.0.0:8754
2020-02-06 22:40:56 | [e]PacketSenderConfiguration::fetch_config(): Unable to fetch configuration for yoda receiver
2020-02-06 22:40:56 | TLSConnection: Error: No such file or directory. Is certificate present under:

2020-02-06 22:40:56 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2020-02-06 22:40:56 | [master][i]Starting processing thread
2020-02-06 22:40:56 | [main][i]Reader thread started
2020-02-06 22:40:56 | [main][i]MLAT data feed started
2020-02-06 22:40:56 | [reader][i]Initializing reader
2020-02-06 22:40:56 | [mlat][i]Waiting for MLAT configuration
2020-02-06 22:40:56 | [reader][i]Connecting to unknown receiver via (tcp://192.168.1.12:30005)
2020-02-06 22:40:56 | [reader][i]Connected to the receiver, configuring
2020-02-06 22:40:56 | [reader][i]Configured, processing messages
2020-02-06 22:40:56 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-UNCERTAIN
2020-02-06 22:40:57 | [time][i]Synchronizing time via NTP
2020-02-06 22:40:57 | [time][i]Time synchronized correctly, offset +0.003 seconds
2020-02-06 22:40:57 | [main][i]Feed Network client started
2020-02-06 22:40:57 | [feed][i]Downloading configuration
2020-02-06 22:40:57 | [feed][d]fetching configuration
2020-02-06 22:40:57 | [reader][i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
2020-02-06 22:40:58 | [feed][i]configuring decoder
2020-02-06 22:40:58 | [feed][c]Max range AIR: 350.0nm
2020-02-06 22:40:58 | [feed][c]Max range GND: 100.0nm
2020-02-06 22:40:58 | [feed][i]configuration changed
2020-02-06 22:40:58 | [feed][i]defined 3 servers
2020-02-06 22:40:58 | [feed][c]Timestamps: optional
2020-02-06 22:40:58 | info | Stopping ReceiverACSender threads for feed
2020-02-06 22:40:58 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: EGNM191, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
2020-02-06 22:40:58 | [feed][n][email protected]:8099/UDP
2020-02-06 22:40:58 | info | [stats]Stats thread started
2020-02-06 22:40:58 | info | Network thread connecting to 185.218.24.22:8099 for feed EGNM191
2020-02-06 22:40:58 | [feed][n]connecting
2020-02-06 22:40:58 | [feed][n]connected via UDP (fd 27)
2020-02-06 22:40:58 | [feed][i]Feed connected
2020-02-06 22:40:58 | [feed][n]working
2020-02-06 22:40:58 | [mlat][i]MLAT configuration received, service ENABLED
2020-02-06 22:40:58 | [mlat][i]Starting MLAT with preconfigured position: 53.73,-1.69,505.0
2020-02-06 22:40:58 | [mlat][i]MLAT bandwidth reduction active, level 1
2020-02-06 22:40:58 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788