@levialex said:
Port(s) required by API in order to communicate with themovidb.org servers
Information regarding the issue:
I have worked with Synology support for several weeks on this issue, and the conclusion is that, due to the settings on my internet router, the TheMovieDB API does not manage to correctly connect to the TheMovieDB server(s) in order to download the information.
I was therefore advised to contact TheMovieDB support and enquire as to which communication ports need to be open/forwarded to my Synology NAS device, from my router, so that the API key may manage to finally properly connect to the TheMovieDB server(s).

We have already received several questions regarding Synology NAS here on the forum.
This explanation that was given by their support is new here.
As far as I remember, when you enter the TMDb API Key you can do a test.
And it seems to me that for all Sinology users the test works correctly.
Didn't this test work for you?
As far as I know the TMDb Server does not require any specific port.
One test you can do is send an API Request directly from your browser which must be using the same internet router.
https://api.tmdb.org/3/movie/550?api_key=THE_KEY
If you get the correct answer with the movie data then the problem shouldn't be with your router.

Is there anyone who might be able to point out which communication ports need to be open/forwarded?

But I know little. Travis Bell, the admin should have a more accurate answer.

Anyway, I think it would be interesting for you to post this answer from Sinology support in the other threads that deal with this issue.
I believe that other users will be interested in this new diagnosis.

Some Synology NAS/DS Video users have appeared reporting problems.
One of them said there was an update from Synology.
We don't know yet but it looks like this update came with this issue.
So I suggest getting help from Synology's website.

See if any of these threads can help solve your problem.

Synology NAS/DS Video Reports

07/21 https://www.themoviedb.org/talk/60f89a1b07e281007d7f3ffe
04/10 https://www.themoviedb.org/talk/60716402dfaae9002b30b85c
02/23 https://www.themoviedb.org/talk/6035201c0d294400405ab8a0
02/17 https://www.themoviedb.org/talk/602ca712db4ed600406bb052
09/01 https://www.themoviedb.org/talk/5f4f012b47c9fb0037742b1c

On the topic
https://www.themoviedb.org/talk/60f89a1b07e281007d7f3ffe#60fd75a9c439c00029f370d5
https://www.themoviedb.org/talk/60716402dfaae9002b30b85c#613c26ecdbf1440062fd16c3
the user got some responses from Synology.

@ticao2 said:

@levialex said:
Port(s) required by API in order to communicate with themovidb.org servers
Information regarding the issue:
I have worked with Synology support for several weeks on this issue, and the conclusion is that, due to the settings on my internet router, the TheMovieDB API does not manage to correctly connect to the TheMovieDB server(s) in order to download the information.
I was therefore advised to contact TheMovieDB support and enquire as to which communication ports need to be open/forwarded to my Synology NAS device, from my router, so that the API key may manage to finally properly connect to the TheMovieDB server(s).

We have already received several questions regarding Synology NAS here on the forum.
This explanation that was given by their support is new here.
As far as I remember, when you enter the TMDb API Key you can do a test.
And it seems to me that for all Sinology users the test works correctly.
Didn't this test work for you?
As far as I know the TMDb Server does not require any specific port.
One test you can do is send an API Request directly from your browser which must be using the same internet router.
https://api.tmdb.org/3/movie/550?api_key=THE_KEY
If you get the correct answer with the movie data then the problem shouldn't be with your router.

Is there anyone who might be able to point out which communication ports need to be open/forwarded?

But I know little. Travis Bell, the admin should have a more accurate answer.

Anyway, I think it would be interesting for you to post this answer from Sinology support in the other threads that deal with this issue.
I believe that other users will be interested in this new diagnosis.

Some Synology NAS/DS Video users have appeared reporting problems.
One of them said there was an update from Synology.
We don't know yet but it looks like this update came with this issue.
So I suggest getting help from Synology's website.

See if any of these threads can help solve your problem.

Synology NAS/DS Video Reports

07/21 https://www.themoviedb.org/talk/60f89a1b07e281007d7f3ffe
04/10 https://www.themoviedb.org/talk/60716402dfaae9002b30b85c
02/23 https://www.themoviedb.org/talk/6035201c0d294400405ab8a0
02/17 https://www.themoviedb.org/talk/602ca712db4ed600406bb052
09/01 https://www.themoviedb.org/talk/5f4f012b47c9fb0037742b1c

On the topic
https://www.themoviedb.org/talk/60f89a1b07e281007d7f3ffe#60fd75a9c439c00029f370d5
https://www.themoviedb.org/talk/60716402dfaae9002b30b85c#613c26ecdbf1440062fd16c3
the user got some responses from Synology.

Good evening,

Thank you very much for the extraordinarily quick reply. It is very much appreciated!

I can confirm that the test I ran on the connection, within the testframe that was set in place within Video Station/DS Video, for when one adds the TheMovieDB API Key to the application for the first time, showed as successful for me as well.

Alas, the system still did not function as it should afterwards. I created a support ticket with Synology, for this exact reason, on the 20th of October 2021, and after quite a lot back-and-forth messages, and Synology even connecting to my NAS device with an Administrator account they requested I create for them, I got the message that can be seen in the following screenshot, on the 8th of November 2021.

Afterwards, I naturally attempted to seek support for the issue here, as directed by them. If their assessment of the issue and of my NAS device was honest or not, that I cannot personally say.

Logically though, the TheMovieDB API Key should require a certain communication port to be open, in order to be able to properly communicate with the TheMovieDB server(s). More than this, I am afraid I would not be able to say.

Unfortunately, I cannot perform the test you suggested as my computer as well as my other smart devices are set under the DMZ protocol within my router so that they may have full access to the internet, no matter what. My Synology NAS device, on the other hand, is not set up to be able to be accessed from outside my personal network and thus has all non-vital communication ports (outside those required for software updates and so on) closed within my router. I had to edit this already so that the Synology Support employee could connect to the unit himself, in order to run tests. This unfortunately did not prove to fix the problem either but, then again, only ports 22, 5000 and 5001 had been opened. If it so happens that the TheMovieDB API Key requires a different port than those in order to communicate with the TheMovieDB server(s), it is more than likely that the port in question remained closed for the duration of the tests.

I believe that only Travis Bell, the Administrator, can contribute to solving this problem.
If you took a look at the links I posted, you can see that this problem has been going on for a long time.
I'll send word to Travis Bell to take a look at your explanation here.

EDIT
And I'm going to add Sinology NAS in the title of this conversation.

I would hate to make anyone feel pressured over this, but are there, by any chance, any updates in regards to the question connected to communication ports?

It has been quite some time, and I have not heard back from anyone.

Thank you in advance!

I didn't hear of any news.
I confess that I still find it strange that the test is successful but the other API Requests do not.
This is because I assume testing should be done by sending an API Request.
If other Requests are not successful, it is strange that only the test works.

@levialex said:

Is there anyone who might be able to point out which communication ports need to be open/forwarded?

Hi @levialex, there's only 2 ports that can be used to communicate with TMDB's HTTP service and those are ports: 80 and 443. These are your standard HTTP and HTTPS ports.

@travisbell said:

@levialex said:

Is there anyone who might be able to point out which communication ports need to be open/forwarded?

Hi @levialex, there's only 2 ports that can be used to communicate with TMDB's HTTP service and those are ports: 80 and 443. These are your standard HTTP and HTTPS ports.

Hello,

Thank you very much for your reply! I really do appreciate you taking the time for this, and I am sorry I pushed a little.

I have forwarded the two ports to my Synology Unit and will now run a full restart. I will update this thread as soon as possible to let you guys know if this has fixed the issue or not.

Hey guys!

Okay! After some rigurous testing, I can now confidently say that forwarding ports 80 and 443 in my router, for the Synology unit HAS FIXED ALL THE ISSUES FOR ME.

What I can recommend for all the others encountering these issues is the following:

1. Make sure your DSM is completely up to date.
2. Make sure you forward the above mentioned ports.
3. Make sure you have no services that are used by Video Station turned off.
4. Enjoy the use of the feature.

Many thanks for all the help!

i have this same issue i will try to figure out how to fix with my att dsl router thanks fred

hello i want to my router and need to know how you determined what to enter in the fields. Service name, global port range, base host port? thanks fred

ok turns out i did not have a port issue. my system was working but after the update it stopped connecting to tmdb turns out some setting changed on the nas drive this is from the synology tech

The Movie Database API can now connect _after IPv6 was disabled in Control Panel > Network > Network Interface > Edit._ IPv6 is generally recommended to be disabled, since it can sometimes cause application problems such as this. what can i do to make it easer for others to find this post?? *API *IPV6 * Synology *nas *Movie station *metadata *dsvideo

@gromit95 said:

ok turn out i did not have a port issue. my system was working but after the update it stoped conecting to tmdb turns out some setting changed on the nas drive this is from the synology tech

The Movie Database API can now connect _after IPv6 was disabled in Control Panel > Network > Network Interface > Edit._ IPv6 is generally recommended to be disabled, since it can sometimes cause application problems such as this.

It has solved the issue for me. Thanks a lot !!!

@Radwulf said:

@gromit95 said:

ok turn out i did not have a port issue. my system was working but after the update it stoped conecting to tmdb turns out some setting changed on the nas drive this is from the synology tech

The Movie Database API can now connect _after IPv6 was disabled in Control Panel > Network > Network Interface > Edit._ IPv6 is generally recommended to be disabled, since it can sometimes cause application problems such as this.

It has solved the issue for me. Thanks a lot !!!

I'm glad it worked for you , it took me 6weeks of emails to synology to get it figured out. fred

@gromit95 said:

ok turns out i did not have a port issue. my system was working but after the update it stopped connecting to tmdb turns out some setting changed on the nas drive this is from the synology tech

The Movie Database API can now connect _after IPv6 was disabled in Control Panel > Network > Network Interface > Edit._ IPv6 is generally recommended to be disabled, since it can sometimes cause application problems such as this. what can i do to make it easer for others to find this post?? *API *IPV6 * Synology *nas *Movie station *metadata *dsvideo

Turning off IPV6 worked for me.

@levialex said:

Hey guys!

Okay! After some rigurous testing, I can now confidently say that forwarding ports 80 and 443 in my router, for the Synology unit HAS FIXED ALL THE ISSUES FOR ME.

What I can recommend for all the others encountering these issues is the following:

1. Make sure your DSM is completely up to date.
2. Make sure you forward the above mentioned ports.
3. Make sure you have no services that are used by Video Station turned off.
4. Enjoy the use of the feature.

Many thanks for all the help!

Thanks so much! It solved my problem <3