FileBot will regularly activate and check your license during normal operation. However, in some badly designed automated setups, if FileBot application data and caches are not persistent and lost between each call, then some users may inadvertently end up activating their license hundreds of times per day, and thus get themselves auto-banned.

Since FileBot requires a file lock on the log file, this will conveniently ensure that only one filebot instance is running at a time, while other filebot instances spawned in the meanwhile have to wait for that lock. This will ensure optimal cache performance.

7.DO check your --log-file once in a while to see if everything is in order:

Activate License P1234567MUST NOT show up in your log for each and every filebot call. You will see this message once or twice per month during normal usage. If you see this message hundreds of times per day, then you need to fix your setup. (NOTE: Activate License logging requires FileBot 4.8.5 or higher)

The FileBot log file does not include system console output. Please read Shell Script Debugging for Beginners on how to collect complete console output including crash dumps and device errors. (NOTE: extremely useful for debugging strange issues)

The logs show 80 license activation requests (DEB package, so presumably on Linux, from the same IP) between 11 Feb and 13 Feb alone, noticeably 3 activations within seconds, every 10 minutes, on the hour exactly.

There's definitely an automated setup with a scheduler running filebot. That itself is perfectly fine, but it seems that application data / cache / etc is lost between each run, which is a problem in many ways.

(normal usage would show ~1 license activation per month at somewhat random times)

I've reinstated the license in the system on my end. You may need to run filebot -clear-cacheonce before you can reactivate your license on your end.

I followed your instructions and it seems to work.
I have activated the license in two users in the nas (root and normal user). Is there a problem if I do it? If so, how can I disassociate the license of one of them?
Is there any limit of use in renaming episodes and / or movies per day?

I have activated the license in two users in the nas (root and normal user). Is there a problem if I do it?

Not at all.

Although 2 users will have 2 different application data folders and that will result in 2 license activations per month, but that is still very much within reasonable bounds and no problem at all (100+ times per day for many days in a row might get you flagged though).

Is there any limit of use in renaming episodes and / or movies per day?

There is no limit.

Although 3rd party websites like AniDB / TheTVDB / TheMovieDB may ban your IP if you spam them with requests. FileBot caches everything with extreme prejudice, so that it'll only talk to the database once a week, even if you use the data thousands of time per second, so that you can't ban yourself accidentally (assuming everything is working correctly, and you're not manually deleting the cache every time).

Hello, I just discovered that my license was banned (PX6145606), I modified my setup to avoid excessive call
Previously I runned 3 instance in parallels every 20mn with docker and each have its own data folder.
I change it so they all have the same data folder and with a different output
Also i run them only twice a day with the same data folder
Could you please reactivate my license key?
Thank you

P4347467 has 500+ license activations, one every 3 seconds, between the dates of 2019-02-08 and 2019-02-12, every day for about an hour (not sure when, depends on your time zone). A normal rate would be 1 time per month.

Do you mind sharing your automated setup so we can have a look what's going awry there?

P4347467 has 500+ license activations, one every 3 seconds, between the dates of 2019-02-08 and 2019-02-12, every day for about an hour (not sure when, depends on your time zone). A normal rate would be 1 time per month.

Do you mind sharing your automated setup so we can have a look what's going awry there?

I'll reinstate your license, but please make sure to fix your setup, so the system doesn't ban you again right away.

Thanks for unbanning.
I had a cronjob that should have ran my script against a media folder once per day.
My old system is gone and am unable to recover everything from it. I do have backups of my filebot call script but it has no automation built into it.

Upon further investigation, I have discovered it may be a testing server i was learning to script on filebot with. I forgot to uninstall it from that machine. I've done so now. Do you have logs of the IPs? 1 should be my desired server and the second, a shared server for purposes other than filebot, may have been allowed to run unchecked. The IP beginning with 184 is my main server, the IP beginning with 205 is the test server. If the requests were coming from 205... then yeah, that might explain that.
If they were coming from 184, i have further investigating to do, but my CRON jobs are lost to the old system.

No worries. Using FileBot on a small number of different machines from different IPs is not a problem. It's the number of activations that's a problem, which indicates that caching is effectively disabled on at least one of your machines, which causes excessive unnecessarily load on the various web services.

I'm unable to send you a message due to being a noob. I followed the other link provided in your profile. I am trying to integrate my license into Deluge. I get an error message saying, "License Error." Will you let me know how to send my license to you?