Fix Firebase Deployment Error
Budget: ₹1,500 – ₹12,500 INR
I built a Node.js web app and pushed it through Firebase Hosting, which in turn triggers Cloud Build and deploys to Cloud Run. The build step completes, yet the revision never becomes ready. Cloud Run keeps throwing:
generic::internal: Provisioning revision instances to receive traffic. Resource readiness deadline exceeded.
The revision log echoes the same during “Assigning traffic to latest specified targets,” and both my default and custom domains stay unreachable.
The custom domain settings on Firebase Hosting are already verified and mapped, so the issue seems isolated to the Cloud Run rollout or its underlying configuration (service account, region-specific quota, container start-up timeouts, etc.).
I’m looking for someone who can:
• Diagnose the root cause behind the Resource readiness deadline exceeded error.
• Apply the necessary fixes (e.g., adjust Cloud Run startup probe, increase memory/CPU, service account permissions, VPC egress, IAM, or any overlooked Firebase project settings).
• Redeploy so traffic routes successfully and both domains respond with 200 status.
• Walk me through what was changed so I can avoid the snag next release.
You’ll get temporary console access (or screenshare if preferred) until the app is live. Once the service is reachable and stable, please provide a concise summary of steps taken and any config values altered.
generic::internal: Provisioning revision instances to receive traffic. Resource readiness deadline exceeded.
The revision log echoes the same during “Assigning traffic to latest specified targets,” and both my default and custom domains stay unreachable.
The custom domain settings on Firebase Hosting are already verified and mapped, so the issue seems isolated to the Cloud Run rollout or its underlying configuration (service account, region-specific quota, container start-up timeouts, etc.).
I’m looking for someone who can:
• Diagnose the root cause behind the Resource readiness deadline exceeded error.
• Apply the necessary fixes (e.g., adjust Cloud Run startup probe, increase memory/CPU, service account permissions, VPC egress, IAM, or any overlooked Firebase project settings).
• Redeploy so traffic routes successfully and both domains respond with 200 status.
• Walk me through what was changed so I can avoid the snag next release.
You’ll get temporary console access (or screenshare if preferred) until the app is live. Once the service is reachable and stable, please provide a concise summary of steps taken and any config values altered.
Related categories:
Linux
Education
NoSQL Couch & Mongo
Amazon Web Services
Node.js
Web Hosting
Google Cloud Platform
Web Application