Hi guys,
I have a problem with the FileBot CLI, I'll explain it better.
I use CLI along with another application, that is Lingon X. I've made sure that when I copy content within a specific folder, this content is automatically scanned, renamed, and sorted by Filebot.
I've been using this "workflow" for a year and a half. Until June 17, 2017 everything worked perfectly. After June 17, however, I realized that the files in the folder were no longer organized.
So I consulted the log file that brings me this error:

FileNotFoundException: https://raw.githubusercontent.com/filebot/scripts/m1/amc.groovy
java.io.FileNotFoundException: https://raw.githubusercontent.com/filebot/scripts/m1/amc.groovy
at net.filebot.web.WebRequest.fetch(WebRequest.java:123)
at net.filebot.web.WebRequest.fetchIfModified(WebRequest.java:101)
at net.filebot.web.CachedResource.fetchData(CachedResource.java:28)
at net.filebot.web.CachedResource.fetchData(CachedResource.java:11)
at net.filebot.web.AbstractCachedResource.fetch(AbstractCachedResource.java:137)
at net.filebot.web.AbstractCachedResource.get(AbstractCachedResource.java:82)
at net.filebot.cli.ArgumentProcessor$DefaultScriptProvider.fetchScript(ArgumentProcessor.java:210)
at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:82)
at net.filebot.cli.ArgumentProcessor.process(ArgumentProcessor.java:116)
at net.filebot.Main.main(Main.java:169)
Failure (°_°)

This issue was not caused by updates because I did not. I also tried to create a virtual machine for the occasion, with only FileBot CLI (this time with the updated version) and Lingon X installed, but I'm getting the same error unfortunately.
Finally I tried to use the script directly via terminal but nothing, it returns the same log.

Support is only available to paying customers or contributors. Did you purchase FileBot on the Mac App Store or make a contribution of equivalent value?

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

You can either purchase FileBot for $20 on the Store to get customer status, or donate $20 to get customer status. The App Store route makes more sense obviously.

If FileBot isn't worth $20 to you after using it for 1.5 years, then you either don't really have a use for FileBot, or you value my time (and your own time) a lot less than I do.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

I'm getting this same error on Windows. I've also done a bit of searching around on these forums, and it seems that starting sometime last week, there have been a lot of errors referencing files under the path "https://raw.githubusercontent.com/filebot/scripts/m1/"

I actually opened filebot when I saw that I was having issues (I use CLI 100% of the time) and it prompted me to update. I was happy to see this, and assumed that whatever issue I was having was probably fixed by an update, since I am pretty out of date. However, I was confused upon reaching the download page. I hadn't realized that Filebot was no longer free on Windows/Mac and now you must buy it. I did some research/googling and learned that you are now requiring customers to purchase for the platforms that offer convenient ways to do so.

Ok, cool, that's actually understandable. The product is amazing; honestly, I must have missed the "donation" option when I originally downloaded it because I usually choose to do that. And it's totally worth my $20 to support the great work you've done. But it's been a long time since then and I really can't remember.

However, I then did a bit more research about my specific issue and it brought me to this thread, and a few others referencing those "/m1/" paths. All responses from you regarding these issues have either been "Support is only available to paying customers" or "Have you updated to the latest version of filebot?"

I really don't want to be rude, and I hope I'm not out of line, but these types of responses make it seem like you have intentionally crippled older versions using remote scripts for the purpose of requiring updates, which would directly cause users to have to pay to upgrade.

Can you confirm or deny that this is the case? Have you removed support for remote scripts (such as amc) from older versions of filebot? (Regardless of the intention, I believe having this question answered would, at the very least, be useful to users coming here for more information on why their scripts fail now.)

Either way, I appreciate filebot and I am literally headed to the windows store now to buy it, since that appears to be my only recourse. So perhaps your "dastardly plan" is indeed working. Still, I can't help but feel a bit upset about being coerced into updating in this way. I would have gladly paid for the latest version of the software had it been suggested to me in a more passive way, with incentives, etc.

Of course, I hope I'm wrong. I hope you can clear this up and perhaps fix the core issue for older versions of filebot using remote scripts. Thanks again for your very hard work.

I do not support old versions. Never have. Never will. It's just not feasible. I can't spend time on testing any and all changes for backwards compatibility. It's always been that way, but now that upgrading involves purchasing FileBot, it's suddenly a big conspiracy.

Based on the feedback, it seems that 4.7.2 and older is partially broken. Anything newer is fine. Older versions generally keep working because the necessary data files just happen to still be on the server, next to newer ones. If the server changes, then the next upload will only contain the newer ones and the old ones will be gone. The last few releases of the "free" version of FileBot probably work just fine to this day.

FileBot caches resources for up to 6 months, so if I accidentally break things for older versions, then I won't know until long after the fact, at which point I will have already forgotten what I did and why. It's like you delete some file you no longer need someday, and then 6 months later somebody comes along and says they need that file.

I'm honestly shocked when I hear people still using 3-4 year old versions of FileBot complaining about it no longer working. I'm perplexed how these older versions only broke now, and not 1-2 years ago.

The GitHub branch used by some older versions of FileBot has been deleted in favour of GPG signed script jars. That is an important security measure, because otherwise anybody could just log in or hack into my GitHub, modify the script, and deploy code to thousands of machines. Also, in this case, only fn:name scripts would break, but you could always run your own local scripts. Actually, all the "you broke filebot" issues refer to some very specific advanced feature, and not all of FileBot.

PS: I'm the accused, so you shouldn't trust my word on any of this. Instead you should check the code and commit history, to see exactly what I did and when, and then make your own judgement based on that.

PS2: I see that "You need to pay for support" is not a reply you wanna hear. I agree. I wonder whether to reply or just ignore the post every single time. It seems that the less offending solution is to simply not reply at all if I don't have an answer the OP wants to hear. But that's not exactly a solution either. Helping right away and then asking for a donation afterwards generally does not result in a donation.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

I can't help but feel a bit upset about being coerced into updating in this way.

Based on your post, I presume that you never update software unless coerced, so coerced it is.

Fortunately, this is the last time. The Windows Store will take care of updates for you from now on. So you'll always be running the latest version, and it'll always just work, and I need to worry about backwards compatibility even less.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

I have now read comments on my post.
I did not want to generate controversy, I hope you understand that mine was really a simple question.
We users who, even just a few times, use a program like FileBot, created by developers such as rednoah, that also make users available to their work on GitHub, we should only thank.
So, thank you for your work.

That reminds me, on Mac, if you only use the filebot command-line tool, and not the GUI app, then you can (and should) use brew to install and update the command:https://www.filebot.net/mac/brew.html

The Mac App Store doesn't support command-line tools, so the command-line tools for Mac are available based on the honour system for the time being. Note that the brew cask is not "free of charge" even though I have no way of charging you.

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.

Hello. I have the same problem of Alevi with the command line tool starting exactly 17 June 2017.
I use the command line tool but I also purchased the App Store version that is not installed on the Mac I use with the command line tool. I had the same filebot version of alevi. I recently tried to update filebot and java with cask. Didn't work.... Please help

FileNotFoundException: https://raw.githubusercontent.com/filebot/scripts/m1/amc.groovy
java.io.FileNotFoundException: https://raw.githubusercontent.com/filebot/scripts/m1/amc.groovy
at net.filebot.web.WebRequest.fetch(WebRequest.java:123)
at net.filebot.web.WebRequest.fetchIfModified(WebRequest.java:101)
at net.filebot.web.CachedResource.fetchData(CachedResource.java:32)
at net.filebot.web.CachedResource.fetchData(CachedResource.java:11)
at net.filebot.web.AbstractCachedResource.fetch(AbstractCachedResource.java:137)
at net.filebot.web.AbstractCachedResource.get(AbstractCachedResource.java:82)
at net.filebot.cli.ArgumentProcessor$DefaultScriptProvider.fetchScript(ArgumentProcessor.java:210)
at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:82)
at net.filebot.cli.ArgumentProcessor.process(ArgumentProcessor.java:116)
at net.filebot.Main.main(Main.java:168)

Problem solved. Sorry I found out I was still using the 4.6 version. cause my script started like that: "
/opt/homebrew-cask/Caskroom/filebot/4.6/FileBot.app/Contents/MacOS/filebot.sh
"
with the 4.7.9 I have no problem. thanks!

My (very excellent) support depends on Windows Store and Mac App Store sales and PayPal donations. Paying users, donors and everyone who contributes to FileBot in one way or another will get the very best support.