Did you purchase your license directly from this website? Did you share your license with someone on the internet, or did someone share the license with you on the internet?P4436750 is being used for Windows, macOS, Arch Linux, Debian Linux and Synology NAS platform packages:Maxim84 wrote: 02 Mar 2019, 04:08 It is installed on a single PC under WIN X but I use ExpressVPN which can explain the different countries.
Code: Select all
AUR DEB DOCKER MSI PKG SPK TAR ZIP
Your license has been shared and copied, either on purpose or accidentally, and so it has been banned. Please PM me for details and further steps.
Once you've identified and fixed the problem, I can re-instate your license number.Upgrade to 4.8.5 and the license reactivated successfully. Thanks a lot!rednoah wrote: 23 Apr 2019, 13:37 P7060103 has been unbanned. Just run filebot --license FileBot_License_P7060103.psm (ideally with the latest FileBot 4.8.5) once again and it should work again.
Code: Select all
P4241619 receiving LicenseError: Banned due to abuseCode: Select all
Activate License P4241619Code: Select all
filebot -script fn:amc --output /media/plexdrive --action move -non-strict /media/plexdrive/unsorted/ --log-file /media/plexdrive/amc.log --def excludeList=/media/plexdrive/amc.txt exec="chmod -R 777 '{output}/'" clean=yCode: Select all
DATA: /home/<user>/snap/filebot/24/dataCode: Select all
P5548530 4042 activations between 05-16 and 05-31
PX4417147 1272 activations between 05-14 and 05-30
P7015608 1214 activations between 05-14 and 06-10
PX5853842 183 activations between 05-22 and 06-11
PX4420907 117 activations between 05-22 and 05-31
P3986568 88 activations between 05-16 and 06-11
PX7096420 40 activations between 05-14 and 06-12
P6992216 37 activations between 05-14 and 06-11
P4093665 33 activations between 05-14 and 06-13
P4322897 25 activations between 05-15 and 06-10
Code: Select all
# to run use - screen -DmS filebot /home/dubstepninja/.filebot/autosort.sh
while true; do
echo "filebot Tv start less than 7 days"
/media/filebot/filebot.sh -script fn:amc --output "/media/Tv" "/media/UnsortedTv" --log-file "/media/filebot/amc1.log" --action copy --conflict override -non-strict --def music=y artwork=y --def clean=y --def unsorted=y --def
excludeList="/media/filebot/amc.txt" seriesFormat="/media/Tv/{n}/Season {s}/{s00e00} - {t}"
echo "Filebot tv complete"
echo "filebot Movie start"
/media/filebot/filebot.sh -script fn:amc --output "/media/Movie" "/media/UnsortedMovie" --log-file "/media/filebot/amc.log" --action copy --conflict override -non-strict --def music=y artwork=y --def clean=y --def unsorted=y --def excludeList="/media/filebot/amc.txt"
echo "Filebot Movies complete"
#echo "Start edit amc for Xxx"
#/home/dubstepninja/.config/.filebot/filebot.sh -script fn:amc "/home/dubstepninja/Media/XXX" --output "/home/dubstepninja/Sync/Xxx/Movies" --def excludeList=/home/dubstepninja/Sync/Xxx/Xxx.txt --def unsorted=y --def ut_label=other --def clean=y
#echo "unrar Xxx Complete"
find /home/dubstepninja/Sync/ -name .message -exec rm -f {} \;
echo "found and removed all '.message' from /sync/"
echo "deleting empty folders"
find /home/dubstepninja/. -type d -empty -delete
echo "finshed deleting empty folders"
echo "sleep 500 seconds"
sleep 500
echo "sleep 300 seconds"
sleep 300
done
Code: Select all
P6354964 31519 activations between 06-04 and 06-29
P4060954 13830 activations between 06-06 and 07-01
P7015608 3737 activations between 06-06 and 07-01
P7783954 923 activations between 06-14 and 07-03
P4125242 782 activations between 06-22 and 06-29
P8461367 635 activations between 06-30 and 07-02
PX5853842 182 activations between 06-04 and 06-26
P7609080 93 activations between 06-07 and 06-22
P6332261 47 activations between 06-11 and 06-29
P3986568 45 activations between 06-03 and 07-03
P7073986 43 activations between 06-13 and 07-02The OP explains in detail what's not working correctly (i.e. application state is lost) and likely culprits. It's gonna be something along those lines.CaptainEpix wrote: 04 Jul 2019, 18:15 Just making a post so I can send a PM. Also had this happen to me, not sure why.
viewtopic.php?f=4&t=9594
hola muy buen día,
disculpen intentando usar la licencia P6354964
me menciona que esta bloqueada, no sabia que se podía llegar a bloquear
asta que empece a leer sobre el problema aquí, utilizo filebot mediante docker (jlesage/filebot)
con los vps de google cloud como método de aprendizaje.
ase poco tuve problemas con el almacenamiento en el vps, para intentar solucionarlo montaba y desmontaba los contenedores
nose si eso llego a afectar
PD, me podrían decir o dar algún link para aprender bien sobre como funciona la licencia con filebot
Your license has been activated 31527 times. 2-3 times would be normal.Code: Select all
06-29 08:08:44 P6354964 US
06-29 08:08:57 P6354964 US
06-29 08:09:10 P6354964 US
06-29 08:09:23 P6354964 US
06-29 08:09:37 P6354964 US
06-29 08:09:50 P6354964 US
06-29 08:10:04 P6354964 US
06-29 08:10:17 P6354964 US
06-29 08:10:30 P6354964 US
06-29 08:10:43 P6354964 US
06-29 08:10:56 P6354964 US
06-29 08:11:09 P6354964 US
06-29 08:11:23 P6354964 US
06-29 08:11:35 P6354964 US
06-29 08:11:49 P6354964 US
06-29 08:12:02 P6354964 US
06-29 08:12:20 P6354964 US
06-29 08:12:33 P6354964 US
06-29 08:12:46 P6354964 US
06-29 08:12:59 P6354964 USNote that clearing the cache will not solve the problem. The problem is the cache being clear before each and every run, as if FileBot is running for the first time, every time.Chris wrote: Hi, I'm not sure why this is happening. I just tried clearing the filebot cache, so hopefully that will help. I'm running filebot with cron every half hour with the command (below) command, but I'm not seeing it doing anything at the link you provided that seems like it would cause this issue.
Code: Select all
0,30 * * * * filebot -script fn:amc --output "/media/datahaus/Video" --action move --conflict skip -non-strict "/home/ubuntu/Downloads/deluge/completed" --log-file amc.log --def seriesFormat="/media/datahaus/Video/TV/{plex.tail}" movieFormat="/media/datahaus/Video/Movies/{plex.name}" unsorted=y music=y artwork=y exludeList=amcExclude.txt -no-xattr
You'll want your tasks to be called with your user, and not as root. You'll want $HOME to point at your user home, and not / or /root or whatever it may be. Please share with us your findings, so that we can add possible cron related issues to the list.I hope I’ve already solved the problem,rednoah wrote: 08 Jul 2019, 02:14
Once you have identified and fixed the issue, then I can unban your license.
Espero haber resuelto ya el problema,
ya que estoy usando un método que se usa en el proyecto cloudbox, para instalar Docker y que funciona con el formato btrfs,
¿podría desbloquear la licencia p6354963 para poder utilizar filebot, y a su vez, saber si se resolvió el problema anterior?
Gracias por tu tiempo
Code: Select all
Activate License P7015608
Jul 14, 2019 4:51:04 AM net.sf.ehcache.store.disk.DiskStorageFactory$DiskWriteTask call
SEVERE: Disk Write of P7015608 failed:
java.io.IOException: No space left on device
at java.io.RandomAccessFile.writeBytes(Native Method)
at java.io.RandomAccessFile.write(RandomAccessFile.java:525)
at net.sf.ehcache.store.disk.DiskStorageFactory.write(DiskStorageFactory.java:393)
at net.sf.ehcache.store.disk.DiskStorageFactory$DiskWriteTask.call(DiskStorageFactory.java:477)
at net.sf.ehcache.store.disk.DiskStorageFactory$PersistentDiskWriteTask.call(DiskStorageFactory.java:1071)Note that this is not about the license, the license abuse is just a symptom, that tells us caching is disabled, which means instead of downloading ~10 MB per month (like everyone else) you are downloading 10 MB * 5.000 times per month, which costs me an extra 50 GB of traffic per month / 600 GB per year.P7015608 wrote: 16 Jul 2019, 12:48 the no space left on device errors are because filebot license gets banned and doesn't work. So my setup is getting stopped because filebot doesn't rename files
In the past, before knowing that filebot has a paid version, I was using the free one. Which used to work great.
However I wanted to support your work and this awesome program
Code: Select all
find . -name "*.sh*" -exec grep filebot {} ';'
export JAVA_OPTS="-Dnet.filebot.logging.debug=ALL -Dnet.filebot.logging.time=true -Dnet.filebot.web.WebRequest.log.response=true"
filebot -rename -non-strict --lang es --log ALL -no-xattr --conflict auto --db TheMovieDB --format "$(pwd)/{n} ({y})/{n} ({y}) {vf} {hdr} {bitdepth}bits {vc} {ac} {aco} {channels} {audioLanguages}" "$FILE"
export JAVA_OPTS="-Dnet.filebot.logging.debug=ALL -Dnet.filebot.logging.time=true -Dnet.filebot.web.WebRequest.log.response=true"
filebot -rename -non-strict --lang es --log ALL -no-xattr --conflict auto --db TheMovieDB --format "$(pwd)/{n} ({y})/{n} ({y}) {vf} {hdr} {bitdepth}bits {vc} {ac} {aco} {channels} {audioLanguages}" "$FILE"
export JAVA_OPTS="-Dnet.filebot.logging.debug=ALL -Dnet.filebot.logging.time=true -Dnet.filebot.web.WebRequest.log.response=true"
filebot -rename -non-strict --lang es --log ALL -no-xattr --conflict auto --db TheMovieDB --format "$pwd/{n} ({y})/{n} ({y}) {vf} {hdr} {bitdepth}bits {vc} {ac} {aco} {channels} {audioLanguages}" "$FILE"
export JAVA_OPTS="-Dnet.filebot.logging.debug=ALL -Dnet.filebot.logging.time=true -Dnet.filebot.web.WebRequest.log.response=true"
filebot -rename -non-strict --lang es --log ALL -no-xattr --conflict auto --db TheMovieDB --format "$pwd/{n} ({y})/{n} ({y}) {vf} {hdr} {bitdepth}bits {vc} {ac} {aco} {channels} {audioLanguages}" "$FILE"
Code: Select all
find . -name "*.sh*" -exec grep filebot {} ';'Code: Select all
grep "Activate License" /path/my/amc.logYou've somehow effectively disabled application state and caching, leading filebot to believe it's running for the first time each and every time, leading to unnecessary abuse of online resources (license abuse warnings usually being the first symptom, though 3rd party services may also auto-ban you eventually).keteflips wrote: 28 Sep 2019, 14:21 I will modify my scripts , no problem. But I don't understand why filebot its validating licence itself.
I don't parse the license command in my scripts...
Thanks I will add the --log-file to monit whats happend.rednoah wrote: 28 Sep 2019, 08:47
The warning email you have received should include detailed activation logs. If you're not seeing corresponding log records on your end, then you're not collecting logs, or not looking at the logs.
What are you trying to do here? You're simply searching *.sh shell scripts for the keyword filebot which definitely won't ever yield any log records of any kind...If you were to check for license activation events, the corresponding grep command would look more like this:Code: Select all
find . -name "*.sh*" -exec grep filebot {} ';'Code: Select all
grep "Activate License" /path/my/amc.log
Code: Select all
WARNING: The index for data file /home/keteflips/.filebot/cache/0/data_0.data is out of date, probably due to an unclean shutdown. Deleting index file /home/keteflips/.filebot/cache/0/data_0.index
Sep 28, 2019 10:29:18 PM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /home/keteflips/.filebot/cache/0/themoviedb_es-es_1.data is out of date, probably due to an unclean shutdown. Deleting index file /home/keteflips/.filebot/cache/0/themoviedb_es-es_1.index
Sep 28, 2019 10:29:19 PM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /home/keteflips/.filebot/cache/0/themoviedb_es-es_1_etag_1.data is out of date, probably due to an unclean shutdown. Deleting index file /home/keteflips/.filebot/cache/0/themoviedb_es-es_1_etag_1.index
Activate License P9384858
Code: Select all
2019-09-28 21:07:47 P9384858What was the source of the issue?
rednoah wrote: 04 Oct 2019, 03:13 Yep. Looks good. Last activation is from a few days ago, so it seems to be working correctly now:Code: Select all
2019-09-28 21:07:47 P9384858What was the source of the issue?
That's an interesting one! Wouldn't have thought of that. That could cause a problem if it's killed suddenly at an inconvenient time.keteflips wrote: 22 Oct 2019, 10:56 Ubuntu Server when its out of memory kills the daemon that causes the problem, and this daemon its my script XD
Please read this post thoroughly as it will give you a very good idea what's going on and a general reason why your license may have been flagged:aaseef021 wrote:27 Dec 2019, 03:38 Hi
I keep getting emails about FileBot License P9982009 has been activated 98 times
Not sure what I am doing wrong, I have have crontab setup to run every 5 minutes for exact and ever 17 minutes for copy to a folder.
I really got no clue why I am being flagged can you please assist I want to solve this. I never had this issue before when using this same exact process
The reason is always that FileBot believes it's running for the very first time, each and every time, meaning persistent storage is somehow disabled. A nonexhaustive list of possible reasons for this is given in the post above. Perhaps the logs will give some indication as to why. Please read (6.) and (7.) for details on logging, and things you might want to look out for.Code: Select all
/filebot-portable/data/root/logs# ls
amc.log filebot.log filebot.txt log.txtCode: Select all
filebot --log-file log.txtWell, logs are logs, and I can't tell you what to do since it's definitely a client-side problem. You could check your logs, and see if you get the corresponding "Activate License" entires.I don't have an automated setup, I just click on the exe to open Filebot, so I don't know how it possibly could be activated multiple times.....
Note that fixing (2.) will also alleviate (1.) as less activations means less activations from different countries. Some users may have genuine use cases, that are unfortunately virtual indistinguishable for abuse, in which case I'm happy to just offer a refund.Well, now is probably the time to learn how to get into the logs and have a look. See FAQ for details.jdcox215 wrote: 17 Jan 2020, 20:07 I don’t even know how to get into the logs, and I only use a vpn for watching other country’s Netflix so I never use filebot while I’m on it.
You will have received this weeks "Activate License" logs for your license via email. You can cross-reference that with your local logs and see if it matches up. If it does not match up, then unauthorized 3rd parties may indeed have had access to your license file one way or another, which would be disturbing to say the least.At first glance. You're not (6.) using a log file, so you won't be able to (7.) check the log to check if everything is in order. Those would be the first steps so you yourself can confirm that things are working correctly / are not working correctly.My script runs the following on a scheduled task every 30 minutes.I cannot see anything wrong with that script based on your linked forum thread.Code: Select all
filebot -script fn:amc --output "\\192.168.1.1\data\media\movies" --action move -non-strict "\\192.168.1.1\data\media\moviestobeprocessed" --def movieFormat="\\192.168.1.1\data\media\{plex}" exit
Among things listed in the OP, it could be running out of disk space, running things as temporary user each time, having 3rd party tools that regularly delete %APP_DATA% files, etc. Anything that could lead to FileBot not being able to remember things. On Windows this is extremely rare, but it's your machine, so you have, directly or indirectly, absolute control over FileBot's memory / persistent storage and something is off in this regard.That would explain why you didn't get any of the automated warning emails. Please PM me your correct email address.selfm4n wrote: 07 Mar 2020, 17:35 Could you reinstate the license? Also, I noticed that the email address associated with my license is an old one that I deleted. Is this likely to be a problem in the future? If yes, could you update it to ".com"?
What does the log say? How many Activate License lines did you find?rednoah wrote: 29 Dec 2018, 06:21 7.
DO check your --log-file once in a while to see if everything is in order:Code: Select all
grep "Activate License" /path/to/logCode: Select all
Activate License P1234567
Nevertheless. Your setup is broken now, and has been for the last ~4 weeks, because you have been receiving warning emails every week for the last ~3 weeks with detailed logs about your license activations.mulderonline wrote: 01 Apr 2020, 09:08 I have no change on my setup since one year i have install new realase please unban my licence: P8498486
Code: Select all
Banned due to abuse. Please read https://www.filebot.net/error/429.html for details."banned due to abuse" is preceded by no less than 3 warning emails with detailed license activation logs, so you can review what you're doing, and check that against frequent user errors:GoT2020 wrote: 10 May 2020, 10:52 My PX7006317 license shows a "banned due to abuse" error. Can you review what happens? Thank you
Since it's your machine(s), only you can figure out what's going on your machine(s) specifically. The activation logs will help you narrow down on the issue though.I have not received any email detailing inappropriate use.rednoah wrote: 10 May 2020, 12:08"banned due to abuse" is preceded by no less than 3 warning emails with detailed license activation logs, so you can review what you're doing, and check that against frequent user errors:GoT2020 wrote: 10 May 2020, 10:52 My PX7006317 license shows a "banned due to abuse" error. Can you review what happens? Thank you
viewtopic.php?t=9594
I have checked the email account and I do not have any email from Filebot, except for the license fee. In SPAM I don't have anything either.rednoah wrote: 10 May 2020, 12:42 Please check your spam folder. The email will have been sent to the one on your license. A license can be unblocked, but it'd be best to first figure out why it might have been banned in the first place, because it'll likely get auto-banned again the root cause is not fixed.
Email were sent on 10 Apr, 17 Apr and 24 Apr. Gmail will keep Spam for a month, but if you're using other providers, and don't regularly check your Spam, then you might have missed them. I'll see if I can forward you the most recent one again.GoT2020 wrote: 10 May 2020, 12:53 I have checked the email account and I do not have any email from Filebot, except for the license fee. In SPAM I don't have anything either.
Could those emails not have been sent?
The first step is to check your local logs as explained in (6.) and (7.) and to confirm the number of licence activations based on your own local log files. What were your findings?Thanks rednoah, I just received the emails you have sent me now.rednoah wrote: 10 May 2020, 13:03Email were sent on 10 Apr, 17 Apr and 24 Apr. Gmail will keep Spam for a month, but if you're using other providers, and don't regularly check your Spam, then you might have missed them. I'll see if I can forward you the most recent one again.GoT2020 wrote: 10 May 2020, 12:53 I have checked the email account and I do not have any email from Filebot, except for the license fee. In SPAM I don't have anything either.
Could those emails not have been sent?
Re: License Error: Banned due to abuse
If your license has been banned, then you will have received multiple warning emails with more detailed information.
Please check your logs against common issues: On Synology NAS, each $USER will has it's own FileBot application data folder and caches and so filebot --license and -clear-cache work only within the context of the current calling $USER, and thus can only fix license activation status for the current calling $USER due to file permissions. On Synology NAS, the easiest way to reset everything is to just uninstall the FileBot package completely via Synology DSM. That will clear all FileBot application data for all users. If you see license activations multiple times per day, then you're likely accidentally deleting application state: