Anyone else having issues with FR24 feeding?

[jprochazka]

@abcd567

I never faced this issue

I have to agree with @abcd567. I rarely see any of my feeder clients including FR24 or any related applications go over 1% CPU utilization and if they do barely. Total system CPU utilization averages about 14% with a MySQL database getting wrote to continually on an RPi 4. @wiedehopf mentioned having issues with FR24 ran within a docker container? I am running things natively and not within containers. If you are using one, it might be the container orchestration system causing the spikes? Maybe try installing the FR24 package natively instead of using a container.

[abcd567]

@jprochazka

having issues with FR24 ran within a docker container? I am running things natively and not within containers. If you are using one, it might be the container orchestration system causing the spikes? Maybe try installing the FR24 package natively instead of using a container.

I have the same policy. I always install things natively, never through container (except for short trials). If an App is not available natively, and container is the only option, I simply dont install that App.

[tomvdhorst]

I don’t use containers, all systems have the feed client installed on top of Raspberry Pi OS or Armbian or Dietpi depending on the hardware.
Installations all have FA, FR24 and Graphs1090 as the installed software

[Jonseyt23]

Im not having feeding issues, but do have an issue trying to get a new feeder key as I just get the below

Validating email/location information…ERROR
Got no response or empty response from the server!

[tomvdhorst]

The best option is to mail support@fr24.com requesting a new key.

They will need the following:

• your email address you want to use to register the receiver.
• The exact location of the receiver
• The id of other receivers you already have.

Usually you will receive the new key within a day or so.

[tomvdhorst]

Well 14 days later, the confirmation that there is a limit on connections from the same IP address has arrived.
But when asking what the limit is they can’t tell, it’s somewhere in the code and they regard it as a very low priority issue and they don’t know if and when they might look it up.

I’m gonna wait a little bit more to see if they come up with the answer.

If not I’m gonna remove the FR24 feeding software from the 2 or 3 newest stations, I’ve got 3 stations in the meantime unable to report data to FR24, but it runs perfectly on here on FA.
They probably don’t care on missing out on the data I guess

[MC130E]

@tomvdhorst

Well 14 days later, the confirmation that there is a limit on connections from the same IP address has arrived.
But when asking what the limit is they can’t tell, it’s somewhere in the code and they regard it as a very low priority issue and they don’t know if and when they might look it up.

Hi,

Thanks for the update. It’s always interesting to hear how things work out.

Obviously your situation is low priority with them since all receivers are at the same location, but I can think of a couple examples that might cause issues for FR24.

1. They could have multiple sites connecting through CGNAT. This could make several appear from the same public IP when in fact there is zero connection between the locaions and even site owners.

2. They might have multiple sites uploading through mobile iOT type data plans. Often those are CGNAT based, and frequently the IP seems to change or “rotate” every few minutes. We have one user feeding from multiple sites. Most of those are on independent internet connections. The 3 or so all on iOT plans all appear from the same IP. Then a short time later, they all jump to another IP. That would have the same issue you are dealing with if he ever reached that limit.

Have fun with all those systems,
-Dan