Announcement

Collapse
No announcement yet.

FR24 link: Disconnected ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • FR24 link: Disconnected ?

    Hi,
    I just setup the software on my raspberry and I get a message the link is disconnected.. does anyone have an idea what the problem could be?

    FR24 Link: Disconnected ()
    FR24 Radar Code: T-EHLE39
    Aircraft Tracked (ModeS & ADS-B): 3
    Aircraft Uploaded: N/A
    Receiver: dvbt, Connected
    MLAT running: YES

    I read that you get a premium account when you start feeding.. does FR24 send you this info once the feed is running or do you need to apply for it somewere?

    Cheers
    Alex

  • #2
    No connection to the server to be able to send data. Firewall or server down issue.

    Should mail you when finally online

    Sent from my GT-I9300 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      Originally posted by Oblivian View Post
      No connection to the server to be able to send data. Firewall or server down issue.

      Should mail you when finally online

      Sent from my GT-I9300 using Tapatalk
      Thanks.. i think the server was down because it suddenly showed connected now..

      Will wait and see about the mail.. cheers

      Comment


      • #4
        The other thing you could try...

        https://www.flightradar24.com/activate-raspberry-pi

        But I think thats for the packaged version
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          Actually that does part of the install script, which you would have done. I cant recall if it asks for a account PW, but your login will be your email address used at signup
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #6
            I've been getting this since this morning

            2016-05-05 08:19:31 | [feed][e]Could not connect!
            2016-05-05 08:19:31 | [feed][n]Error: Could not connect! (fd -1)
            2016-05-05 08:19:31 | [feed][n]waiting 8 seconds

            And so on... Is anything going on at FR24?
            Been feeding fine for months and have not made any changes

            Comment


            • #7
              I ran sudo apt-get update && sudo apt-get upgrade and my system was already up-to-date.
              I can see aircraft when looking at MY-IP:8080 so dump1090 is working OK

              It's just the feed that's not connecting...
              Tried rebooting, but no luck.
              Internet connectivity is working just fine.

              I've just emailed support to see if anything is going on at FR24, but if anyone has any idea please let me know!

              Comment


              • #8
                Getting the same "Could not connect" message here. Always reassuring to know that the problem is not mine alone!

                Comment


                • #9
                  Same here, feed_status_message="Could not connect!"

                  Comment


                  • #10
                    I have had the same problem since yesterday afternoon "Network error could not connect "

                    Comment


                    • #11
                      Originally posted by Ian Kirby View Post
                      I have had the same problem since yesterday afternoon "Network error could not connect "
                      Yep, my "last upload" time is showing as 1811 yesterday.

                      Comment


                      • #12
                        Quite a few members of my forum reported error messages yesterday evening. I reported it to FR24 via email at the time. So FR24 should be aware.

                        http://radarspotting.com/forum/index....html#msg29590
                        Mike


                        www.radarspotting.com

                        Radarspotting since 2005

                        Comment


                        • #13
                          Same here since 18.11 today

                          Comment


                          • #14
                            No one can identify what time was it occurred if you report with local time.
                            UTC is good way to share the information.


                            Sent using Tapatalk

                            Comment


                            • #15
                              I have the same problem since 2016-05-04 17:39:35.

                              Comment

                              Working...
                              X