After the last update this format stop working with the AMC: 

/storage/{ anime ? 'Anime' : 'Serien' }/{ ~plex.id  sy.bounds().joining('-', ' [', ']') }

 

Under the WEBUI the same format works fine.

 

Any suggestions?

Anyone else have Filebot present only a blank black screen when opening the webgui? I had seen this in the past and it appeared to be cookie related as clearing cookies/cache for the unRAID server returned it to normal function. But this time clearing cookies/cache hasn't made a difference. Nor has using another browser.

 

Even more puzzling is my attempt to install it on one of my other unRAID servers that it's never been installed on. Just left everything on the defaults in the template except for the /storage mountpoint - mine has always been set to /mnt instead of /mnt/user. Alas just a blank black screen there too.

 

Any chance that it's a date related issue now that we're into 2025? It worked fine yesterday.

7 minutes ago, AgentXXL said:

Any chance that it's a date related issue now that we're into 2025? It worked fine yesterday.

and does here working fine un 2ß25

 

but im running filebot on a custom br0 with own IP as this cookie refreshing disturbed me already quite a while ago ...

so i guess its still some cookie, cached ... thing on your side.

 

6 minutes ago, alturismo said:

and does here working fine un 2ß25

 

but im running filebot on a custom br0 with own IP as this cookie refreshing disturbed me already quite a while ago ...

so i guess its still some cookie, cached ... thing on your side.

 

For 💩's and giggles I changed to a custom: br0 with a fixed IP and it still is showing a black screen. It's unlikely to be any cookies/cached content as it has the same behavior on another unRAID system that it had never been installed on.

On 1/1/2025 at 8:48 AM, AgentXXL said:

 

For 💩's and giggles I changed to a custom: br0 with a fixed IP and it still is showing a black screen. It's unlikely to be any cookies/cached content as it has the same behavior on another unRAID system that it had never been installed on.

Figured out my issue - FUSE had crashed so /mnt/user was inaccessible. Rebooted and all is good again, including Filebot.

 

EDIT: small update - I realized that while I resolved the issue on the main system that I normally use Filebot on, the 2nd unRAID that I installed the container on also had an issue. On both systems FUSE had crashed within a couple of hours of each other. Nothing in the logs that was common leading up to the crashes. I am running 7.0.0 rc2 on both so if it happens again, I'll make a bug report with the logs I captured this time and for the new occurrence.

Edited January 5, 20251 yr by AgentXXL
More details added

On 11/25/2024 at 12:39 PM, Djoss said:

The latest version of FileBot switched to the new OpenSubtitles REST API by default. You now need to provide credentials for opensubtitles.com instead of opensubtitles.org.

 

I'm having the same error as the others. Where do I change it?

I have the same PW on OS.com as I did on OS.org.

anyone?

 

You can edit the container settings to set the password. There is a "OpenSubtitles Password" field for that,

Edited January 10, 20251 yr by Djoss

Thanks but the password is the same.

So you are getting the following error ?

 

[cont-init   ] 55-filebot.sh: Checking... https://api.opensubtitles.com/api/v1/login [400 Bad Request]

 

Did you check that you can login with the same username/password on opensubtitles.com ?

 

I just tried on my side and it's working fine:

[cont-init   ] 55-filebot.sh: Enter OpenSubtitles username: Enter OpenSubtitles password: Store user preferences to [User Preferences: /config/prefs.properties at /config/prefs.properties]
[cont-init   ] 55-filebot.sh: Set OpenSubtitles login details
[cont-init   ] 55-filebot.sh: Checking... OK

 

Got it working, thanks!