Good call. I don't typically use the dev version, but I had while testing. Clearing solved that issue. However, here's the error I see:
SSLHandshakeException: java.security.cert.CertificateException: No name matching {emby server} found
My assumption is that this is a certificate trust issue. It ...
Search found 3 matches
- 19 Mar 2018, 17:28
- Forum: Scripting and Automation
- Topic: AMC: Emby refresh calls to SSL on wrong port
- Replies: 4
- Views: 3426
- 19 Mar 2018, 13:40
- Forum: Scripting and Automation
- Topic: AMC: Emby refresh calls to SSL on wrong port
- Replies: 4
- Views: 3426
Re: AMC: Emby refresh calls to SSL on wrong port
I'm doing something wrong (or things are still askew). Here's what I did:
C:\filebot -script dev:amc "e:/watch" --output "{mediastore}" --action move --conflict auto -non-strict --log-file e:/amc.log --def seriesFormat="{mediastore}\tv\{n}\Season{s}\{n}.S{s.pad(2)}E{e.pad(2)}.{t}" subtitles=en ...
C:\filebot -script dev:amc "e:/watch" --output "{mediastore}" --action move --conflict auto -non-strict --log-file e:/amc.log --def seriesFormat="{mediastore}\tv\{n}\Season{s}\{n}.S{s.pad(2)}E{e.pad(2)}.{t}" subtitles=en ...
- 18 Mar 2018, 21:10
- Forum: Scripting and Automation
- Topic: AMC: Emby refresh calls to SSL on wrong port
- Replies: 4
- Views: 3426
AMC: Emby refresh calls to SSL on wrong port
I've recently set up filebot using the AMC script. I'm trying to automate the Emby refresh after the sorting, however Emby wasn't receiving the API Post. I dug into the amc.log, and found the following:
Notify Emby: [{emby.server.com}, token:{super-secret-key}]
POST: https://{emby.server.com}:8096 ...
Notify Emby: [{emby.server.com}, token:{super-secret-key}]
POST: https://{emby.server.com}:8096 ...