Hi rednoah, yes, that's covered (the input / output folders) ,thanks for the heads up! What fixed it for me was changing from dev to fn filebot -script fn:amc --output "F:\Shares" --action duplicate --conflict skip -non-strict --log-file=amc.log --def kodi=172.168.15.41:80 --def excludeList=amc ...

Never mind, changed the script from dev to fn and now it works just fine. Apologies for the false alarm! I remember I changed it to dev long time ago for a different problem. filebot -script dev:amc --output "F:\Shares" --action duplicate --conflict skip -non-strict --log-file=amc.log --def kodi=172 ...

Up to a few days ago amc script was working fine with qBitTorrent. Since today, I get the following error: This is using latest Filebot (4.9.2) on Windows server. This is the line I have for qBitTorrent on download: filebot -script dev:amc --output "F:\Shares" --action duplicate --conflict skip -non ...

rednoah wrote:The stable release channel is updated once or twice a month. Using dev:amc is encouraged because it'll help us (i.e. me and you) find and fix issues before they make it into the fn:amc channel.

Cool, thanks again rednoah. I will keep using dev:amc.

Cheers!

Alright, so 8080 is the default port for HTTP (makes sense) and 9090 is the default port for TCP connections. FileBot no longer uses TCP though because HTTP is easier to debug and test for users. Thanks for the clarification and for your guidance. Being able to notify kodi directly is really ...

What is the default port number in Kodi? I doubt that port 80 is default for an API. Does it provide a browser-based web interface at the same time as well? I am using osmc (which is Kodi in the end), just in case it makes a difference. Web Server listens in 8080 (I changed it to port 80) by ...

The latest revision of the script uses the HTTP API instead of the TCP API. Default port is 8080 but if you have changed it then you can pass it along: --def kodi=localhost:8080 WOW! That was a fast reply :) This is indeed very excellent support. I can confirm it is working with the dev:amc switch ...

Hello :) For me it is not working anymore as well. I can update via curl commands through the 9090 port without issues and can telnet to 9090. I get the following in the logs: Notify Kodi: 192.168.178.41 GET: http://192.168.178.41:9090/jsonrpc?request=%7B%22jsonrpc%22%3A%222.0%22%2C%22method%22%3A ...