[Bug report] Notify Emby at different port

All your suggestions, requests and ideas for future development
Post Reply
spamtoaster
Posts: 3
Joined: 07 Aug 2017, 09:59

[Bug report] Notify Emby at different port

Post by spamtoaster »

Hi,

Could you provide a symbol to specify the port that filebot Node could use to notify Emby to refresh his database?

Here my log from my fileBot Node in my synology NAS:
At the field in fileBot node to Emby I need to put server:token

If I use server:port:token it does not work. An example at Emby field:
jelly.lan:38d4ae6f5FFFFFFFFFFFFFFFFF


jelly.lan is my server at my lan at a different port than 8920 ( I use 32001).

Code: Select all

Notify Emby: [host:jelly.lan, token:38d4ae6f5FFFFFFFFFFFFFFFFF ]
POST: https://jelly.lan:8920/Library/Refresh?api_key=38d4ae6f5FFFFFFFFFFFFFFFFF 
ConnectException: Connection refused
Thanks and great software by the way. ;)
User avatar
rednoah
The Source
Posts: 23930
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: [Bug report] Notify Emby at different port

Post by rednoah »

You'll need to do custom curl requests via --def exec if you have a custom setup.
:idea: Please read the FAQ and How to Request Help.
Post Reply