Hi @FriiZoLoGYy,

Unfortunately I've never seen or heard of such an error. Where are you seeing this? On what platform? Doing what exactly?

I'm using it in my application to get information on movies & tv shows. its in a node.js express environment using node-fetch to make the request to the api. I've spoken to my hosting provider and they have triple checked their side and have found nothing and confirmed that its something on the apis end. obviously its not on the apis end.

another error i have been get a lot lately as well is

FetchError: request to https://api.themoviedb.org/3/search/movie?api_key=MYAPIKEY&language=en-US&query=Transporter%202&year=2005&page=1&include_adult=false failed, reason: connect ETIMEDOUT 2600:9000:2137:2a00:c:174a:c400:93a1:443
at ClientRequest.<anonymous> (/var/www/html/phantommovies.com/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:514:28)
at TLSSocket.socketErrorListener (node:_http_client:501:9)
at TLSSocket.emit (node:events:514:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'
 }

Hi @FriiZoLoGYy, I am wondering if you mistyped the first error EHOSTREACH instead of EHOSTUNREACH, the latter is a known error. Here is a short article that explains some of the common node.js errors.

It appears that maybe you might have a problem with routing to the tmdb server, that is, a problem on your system or in the network between your system and tmdb. I see you are running on linux so you might want to experiment with "traceroute" and see if you can find out where things are going wrong.

@robbie3999 said:

Hi @FriiZoLoGYy, I am wondering if you mistyped the first error EHOSTREACH instead of EHOSTUNREACH, the latter is a known error. Here is a short article that explains some of the common node.js errors.

It appears that maybe you might have a problem with routing to the tmdb server, that is, a problem on your system or in the network between your system and tmdb. I see you are running on linux so you might want to experiment with "traceroute" and see if you can find out where things are going wrong.

You are correct definitely miss typed first error, I think I'm just ganna end up rewriting the application and seeing if that does the fix

Update: I believe I have solved this issue (lets hope) After many weeks of troubleshooting & reconfiguring cloudflare to have the same issue keep happening I realized some of the error had deal with node.js. With that in mind I started checking node versions on all systems and had learned my VPS was not running the same node version as my local system. VPS was running node v18 latest while my local runs v16, so I downgraded the VPS to node v16 and as of now the error has not happened at all.