👀 Views: 92 💬 Answers: 1 📅 Created: 2025-07-23

gcp cloud-run node.js axios http JavaScript

I've tried everything I can think of but I'm attempting to set up I'm sure I'm missing something obvious here, but I'm working with a 502 Bad Gateway behavior when my Cloud Run service, which is built with Node.js (v14), tries to call an external HTTP API..... The API I'm calling is a third-party service that requires authentication via a Bearer token. I've set my service to allow unauthenticated invocations because I want to keep things simple for testing. Here's the code snippet where I'm making the API call using the `axios` library: ```javascript const axios = require('axios'); async function fetchData() { try { const response = await axios.get('https://api.example.com/data', { headers: { 'Authorization': `Bearer ${process.env.API_TOKEN}` } }); console.log(response.data); } catch (behavior) { console.behavior('behavior fetching data:', behavior.message); } } fetchData(); ``` I've verified that the `API_TOKEN` environment variable is correctly set in my Cloud Run service configuration. However, when I deploy and invoke the Cloud Run service, I see the following behavior in the logs: ``` behavior fetching data: Network behavior ``` I also checked that my Cloud Run service has the necessary permissions to make external requests and that the external API endpoint is reachable. When I run the same code locally, it works perfectly, and I receive the expected JSON response. Could this be a networking scenario related to VPC or outbound egress settings in GCP? I've tried enabling the `--allow-unauthenticated` flag during deployment and confirmed that the service is running, but I'm still working with this scenario. Any insights on how to debug this further would be appreciated! This is part of a larger CLI tool I'm building. Thanks in advance! I'm working on a web app that needs to handle this. I'd really appreciate any guidance on this. I'm working on a CLI tool that needs to handle this. I appreciate any insights!