- 4
- 0
Hello everyone.
I have been going in circles to try to resolve this but nothing seems to work. I've read all that I can find about people facing the same situation but none of the suggestions have worked for me. I've tried changing the DNS settings, NTP settings, I've tried resolving IPv4 first, disabling IPv6, I've tried regenerating the NAS certificate... I don't think there is anything I have not tried. I have even used a switch with port mirroring to capture the NAS network communication using Wireshark and what I realized is that... the problem is anything but connectivity!
On the TMDB API key form, the test function returns successful validation, and when I look at the Wireshark traffic there is indeed a DNS query and then active communication with api.themoviedb.org. Then I use the test function in the plugin list and the connection fails, moreover there is absolutely no communication with the internet, just an exchange between the NAS and the user browser saying that the test failed. The same case happened when I tried to install a 3rd-party metadata plugin in VideoStation, it says there is no internet connectivity... which is false, and again, Wireshark shows that there was no attempt to communicate outside the local network.
Taking this a bit further, using SSH to test either the default TMDB plugin (or a third-party plugin dropped through SCP) works fine in the terminal, meaning that a perfect JSON response is received with all the expected metadata. So, my question at the moment is why Synology's VideoStation seemingly invents connectivity issues where there are none, and if there is anything that can be done about it? I assume that the issue must be at the binary level of VideoStation itself so I'm not getting my hopes up.
I have been going in circles to try to resolve this but nothing seems to work. I've read all that I can find about people facing the same situation but none of the suggestions have worked for me. I've tried changing the DNS settings, NTP settings, I've tried resolving IPv4 first, disabling IPv6, I've tried regenerating the NAS certificate... I don't think there is anything I have not tried. I have even used a switch with port mirroring to capture the NAS network communication using Wireshark and what I realized is that... the problem is anything but connectivity!
On the TMDB API key form, the test function returns successful validation, and when I look at the Wireshark traffic there is indeed a DNS query and then active communication with api.themoviedb.org. Then I use the test function in the plugin list and the connection fails, moreover there is absolutely no communication with the internet, just an exchange between the NAS and the user browser saying that the test failed. The same case happened when I tried to install a 3rd-party metadata plugin in VideoStation, it says there is no internet connectivity... which is false, and again, Wireshark shows that there was no attempt to communicate outside the local network.
Taking this a bit further, using SSH to test either the default TMDB plugin (or a third-party plugin dropped through SCP) works fine in the terminal, meaning that a perfect JSON response is received with all the expected metadata. So, my question at the moment is why Synology's VideoStation seemingly invents connectivity issues where there are none, and if there is anything that can be done about it? I assume that the issue must be at the binary level of VideoStation itself so I'm not getting my hopes up.