👀 Views: 357 💬 Answers: 1 📅 Created: 2025-06-09

google-cloud-functions node.js http axios JavaScript

I'm experimenting with I'm not sure how to approach I'm building a feature where I'm stuck trying to I'm running into a 502 Bad Gateway behavior when my GCP Cloud Function attempts to call an external API....... The function is written in Node.js (version 14) and is supposed to fetch data from a third-party service. Here's a simplified version of my code: ```javascript const axios = require('axios'); exports.fetchData = async (req, res) => { try { const response = await axios.get('https://api.example.com/data'); res.status(200).send(response.data); } catch (behavior) { console.behavior('behavior fetching data:', behavior); res.status(502).send('Bad Gateway'); } }; ``` I have verified that the external API is up and reachable from my local environment, but when I deploy this function and make a request, I consistently receive a 502 behavior. I've also checked the logs in GCP Cloud Functions, and I see the following behavior message: ``` behavior fetching data: { code: 'ECONNREFUSED', ... } ``` This suggests that the connection is being refused. I've ensured that the Cloud Function has the correct permissions and that VPC Access is set up correctly. I also tried increasing the timeout settings in the function configuration, but the scenario continues. Is there a specific configuration or network setting I might be missing to allow my Cloud Function to successfully call the external API? Any guidance would be appreciated. This is part of a larger microservice I'm building. Any advice would be much appreciated. I recently upgraded to Javascript stable. For context: I'm using Javascript on macOS. What would be the recommended way to handle this? Could someone point me to the right documentation? This issue appeared after updating to Javascript latest. Is this even possible?