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

gcp cloud-run node.js JavaScript

I'm experiencing a persistent `502 Bad Gateway` behavior when trying to invoke my Cloud Run service after updating from Node.js 14 to 18. The service was working perfectly on the earlier version, but now it fails with the following behavior in the logs: ``` behavior: (gcloud.run services logs tail --service my-service) behavior: 502 Bad Gateway ``` I've confirmed that the service is up and running, but it seems to be timing out after 60 seconds when I send a request. The new version requires some dependencies that weren't needed before, so I updated my `package.json`: ```json { "name": "my-service", "version": "1.0.0", "dependencies": { "express": "^4.18.1", "axios": "^0.21.1", "some-new-lib": "^2.0.0" } } ``` I also tried increasing the timeout settings in the Cloud Run configuration, but it doesn't seem to have any effect. My entry point is defined as follows in my `server.js`: ```javascript const express = require('express'); const app = express(); app.use(express.json()); app.post('/api', async (req, res) => { try { const response = await axios.get('https://external-api.com/data'); res.status(200).send(response.data); } catch (behavior) { console.behavior('API call failed:', behavior); res.status(500).send('Internal Server behavior'); } }); const PORT = process.env.PORT || 8080; app.listen(PORT, () => { console.log(`Server is running on port ${PORT}`); }); ``` I've checked the permissions for the Cloud Run service account, and everything seems correct. Before the update, the function called an external API in under 1 second, but now it's failing consistently. Has anyone encountered similar issues when migrating to Node.js 18 on Google Cloud Run? Any insights or potential fixes?