rednoah wrote: ↑24 May 2023, 21:52 Press WIN+R and then run the following command to configure FileBot to use the legacy HTTP/1 API:

Code: Select all

setx FILEBOT_OPTS "-Dnet.filebot.web.WebRequest.v1=true"

Thank you, confirmed working

is the one that works

There must be some form of persistence because it continues to work even if I delete system.properties, I'll try rebooting between changes and let you know

Working now, thank you

You can further set net.filebot.web.WebRequest.v1 to configure FileBot to use the same HTTP/1 code used by default in previous FileBot 4.* releases: filebot -script fn:properties --def net.filebot.web.WebRequest.v1=true Unfortunately same error D:\Kodi Holding>filebot -script fn:properties --def ...

Thanks for your prompt response and suggestion, MS Store App, forcing IPv4 connections results in the same error D:\Kodi Holding>filebot -script fn:properties --def java.net.preferIPv4Stack=true script_bundle_0_0: compute: fn: net.sf.ehcache.CacheException: java.io.StreamCorruptedException: invalid ...

Hello, I'll be grateful for assistance please. The MS Store Filebot app was updated to v5.0.3 (r9760) today and when using the following from a windows batch file, filebot -script fn:amc "D:/Kodi Holding/Incoming/" --output "D:/Kodi Holding/Processed/" --conflict override -non-strict --def clean=y ...

Clear cache, try again. Should be fixed now.

thanks for the quick support, it's working now

rednoah wrote:It's funny how you don't even mention that you're using the latest test jar...

I did use it but reinstalled using the installer...

[update] I see now, the installer doesn't overwrite even though it says "removing previous version"

Hi, I've been using FileBot for some time without any problems using AMC on Win10 x64 but I today I get the following error in the log and no files are renamed BAD certificate: [[ [ Version: V3 Subject: CN=rednoah, O=FileBot Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11 Key: Sun ...