2021-03-20, 17:47
I've started experimenting with the Mediaimporter again after quite some time and experience the following problem:
My Emby Server runs in Docker on my NAS and is discovered correctly, but authentification requests keep failing. Examining the logs, the problem is obvious: The authentification requests are sent to the wrong IP address, i.e. the add-on is trying to address my Emby Server via the IP it has on the bridge network within docker, and not via the IP address of my server itself. In the network settings of my Emby Server there is an option to override the local IP address of the server. I've put my NAS IP in there. But it doesn't help. It seems the mediaimport.emby addon is trying to evaluate the IP address itself, rather than taking the "overridden" one from the Emby server settings.
Is this a known problem? Is there a workaround? Or am I doing something wrong?
My Emby Server runs in Docker on my NAS and is discovered correctly, but authentification requests keep failing. Examining the logs, the problem is obvious: The authentification requests are sent to the wrong IP address, i.e. the add-on is trying to address my Emby Server via the IP it has on the bridge network within docker, and not via the IP address of my server itself. In the network settings of my Emby Server there is an option to override the local IP address of the server. I've put my NAS IP in there. But it doesn't help. It seems the mediaimport.emby addon is trying to evaluate the IP address itself, rather than taking the "overridden" one from the Emby server settings.
Is this a known problem? Is there a workaround? Or am I doing something wrong?
