[Bug report] Notify Emby at different port
Posted: 13 May 2020, 09:36
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).
Thanks and great software by the way. 
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