Nodejs API not connecting to third-party API when hosted on spanel

[Twain97]

Nodejs web application on cpanel giving error 500 when trying to connect with third party API, works well on render.com.

Please help

[Yasir-Rafique]

Hey, I ran into something super similar a while back, so hopefully this helps!

When your Node.js app works fine on Render.com but throws a 500 error on cPanel (especially when it’s hitting a third-party API), it’s usually down to two things in my experience:

1. Outbound requests are blocked or restricted.
   A lot of cPanel hosts block outgoing HTTP/HTTPS requests by default, just to avoid abuse or spam. So when your app tries to reach out to another API, it gets blocked, and the server freaks out with a 500 error. You might want to ask your hosting provider if they allow outbound connections or if there’s a firewall rule you can tweak.

2. Environment or Node.js version mismatch.
   I have found that cPanel servers often run really old versions of Node, or don’t have your environment variables set the same way as your cloud host. That can mess with API requests especially if you’re using modern syntax or missing an API key. Double-check your Node version (node -v in SSH, if you have it) and make sure all your env vars are actually set.

If you can get your hands on the actual error log, it will probably point to which of these two is causing the mess. But yeah, 99% of the time for me, it’s been one of those!

Hope this helps. let me know what you find!

[Harrisbaig7]

This usually happens on cPanel due to outbound request restrictions or Node runtime differences. First check your server error logs to confirm if the request is actually reaching the third-party API. In many shared hosting setups, outgoing HTTPS requests are blocked or limited, which causes a 500 error even if the same code works on Render or other cloud platforms. Also verify that your Node version and environment variables on cPanel match your deployment on Render.