Announcement

Collapse
No announcement yet.

FR24 Windows - can't connect to local 8754

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

  • FR24 Windows - can't connect to local 8754

    As title says, with Windows app running and sending data, I can't connect to localhost:8754
    Any suggestions?
    Last edited by SoNic67; 2018-03-11, 00:37.

  • #2
    Go to folder where fr24feed.exe is located. In my case it is the folder "C:\Users\abcd\Desktop\fr24feed_win32_1.0.19-15\fr24feed_win32"
    You will see a file "fr24feed.ini"
    Open file fr24feed.ini in text editor like Notepad, and add following new line
    procargs="--net"
    Save the file.
    Exit fr24feed, and then restart it.
    Now you can connect to ip-of-pi:8754

    FR24 ini -1.png . FR24 ini -2.png

    Comment


    • #3
      Thanks for the reply. Nope, didn't help.

      I am in Windows, feeding the FR24 from RTL1090 (127.0.0.1:31001) as "beast-tcp" and that works.

      PS: I have a bridged connection with another virtual one using ZeroTier. Shutting that off didn't help either and... everything else works normally though.
      Last edited by SoNic67; 2018-03-10, 20:42.

      Comment


      • #4
        You mean adding the line
        procargs = "--net"
        in file fr24feed.ini did not help? Very strange.
        It works for me in WINDOWS for both mr-dump1090 and RTL1090.

        The line procargs = "--net" is applicable irrespective how you feed.
        The difference for feeding from mr-dump1090 and RTL1090, is in receiver and path / host settings only.

        For feeding by mr-dump1090
        receiver="dvbt"
        fr24key="CENSORED"
        path="mr-dump1090.exe"
        bs="no"
        raw="no"
        logmode="1"
        procargs="--net"
        windowmode="0"
        mpx="no"
        mlat="yes"
        mlat-without-gps="yes"

        For feeding by RTL1090
        receiver="beast-tcp"
        fr24key="CENSORED"
        host="127.0.0.1:31001"
        bs="no"
        raw="no"
        logmode="1"
        procargs="--net"
        windowmode="0"
        mpx="no"
        mlat="yes"
        mlat-without-gps="yes"
        Last edited by abcd567; 2018-03-10, 23:59.

        Comment


        • #5
          Maybe my ini file will help as I'm running 'beast-tcp' as well? Note my localhost port is different.

          receiver="beast-tcp"
          fr24key=
          host="localhost:30033"
          bs="no"
          raw="no"
          logmode="2"
          windowmode="0"
          mpx="no"
          mlat="no"
          mlat-without-gps="no"

          Comment


          • #6
            I am puzzled, because this is what I have in my .ini:

            receiver="beast-tcp"
            fr24key="xxxxxxxxxx"
            host="127.0.0.1:31001"
            bs="no"
            raw="no"
            logmode="1"
            mlat="yes"
            mlat-without-gps="yes"
            procargs="--net"
            windowmode="0"

            Tried with Firefox, IE and Chrome.
            "This site can’t be reached
            localhost refused to connect."
            Last edited by SoNic67; 2018-03-11, 00:18.

            Comment


            • #7
              Originally posted by Stealth View Post
              I am puzzled, because this is what I have in my .ini:
              RTL1090 by default outputs Beast data on port 31001
              ALL IN YOUR FILE IS OK.
              JUST ADD THE LINE SHOWN IN RED
              receiver="beast-tcp"
              fr24key="xxxxxxxxxx"
              host="127.0.0.1:31001"
              bs="no"
              raw="no"
              logmode="1"
              mlat="yes"
              mlat-without-gps="yes"
              procargs="--net"
              windowmode="0"
              procargs="--net"
              Last edited by abcd567; 2018-03-11, 00:13.

              Comment


              • #8
                I have added that line, it's the second from last.
                I have noticed something. My RAID configuration page is on https://localhost:888/ and it works fine.
                Is there any setting in OS that would REQUIRE localhost connections only to a https?

                Comment


                • #9
                  Fixed, thanks all.

                  I am getting old, I forgot the first rule in Windows troubleshooting: When in doubt, Restart the damn box.


                  PS: I also remembered that MLAT works only on the Pi box, in Windows has no effect.
                  Last edited by SoNic67; 2018-03-11, 00:40.

                  Comment

                  Working...
                  X