Deployment Troubleshooting
Resolve common deployment, infrastructure, and cloud provider errors when using Zynnode.
Overview
This guide covers common configuration mistakes and troubleshooting steps when deploying your applications to the cloud via Zynnode. Because Zynnode operates within your own cloud environments, certain external cloud settings must be configured properly in your provider dashboard.
Connecting Your Cloud Accounts
Zynnode connects to your cloud providers securely through official integrations. You do not need to use a terminal or command-line setup flow to link your accounts.
Amazon Web Services
To connect AWS, use the CloudFormation flow provided by the Zynnode dashboard.
- In your Zynnode dashboard, click Connect AWS.
- You will be redirected to the AWS Management Console with a pre-filled CloudFormation stack.
- Select the checkbox labeled I acknowledge that AWS CloudFormation might create IAM resources.
- Click Create stack.
- After AWS finishes creating the stack, Zynnode will verify the connection automatically.
Google Cloud Platform
To connect GCP, link your Google account directly from the dashboard.
- In your Zynnode dashboard, click Connect GCP.
- A secure Google authorization window will open.
- Select the Google account associated with your GCP billing setup.
- Grant Zynnode the required permissions to manage Cloud Run and Compute Engine resources on your behalf.
| Connection Error | Cause and Resolution |
|---|---|
Connection timed out or Access Denied | Your cloud user account does not have administrator-level privileges. Sign in with an account that can approve integrations and grant the required access. |
Google Cloud Platform Troubleshooting
Cloud Run
| Error Message | Meaning | Resolution |
|---|---|---|
The caller does not have permission | The cloud connection is incomplete or linked to the wrong project. | Reconnect your GCP account in the Zynnode dashboard and make sure you selected the correct GCP project during setup. |
Unauthenticated Invocation | Public access is disabled. | In Google Cloud Console, open Cloud Run, select the service, go to Security, and ensure the allUsers principal has the Cloud Run Invoker role. |
Revision failed to route traffic | The application crashed during startup. | Check whether required environment variables are missing in the Zynnode dashboard and make sure the app listens on the PORT value provided by Cloud Run. |
Compute Engine
App deployed successfully but the website will not load
Your VM firewall rules are likely blocking traffic.
Check the following:
- In Google Cloud Console, ensure Allow HTTP traffic and Allow HTTPS traffic are enabled for the VM
- Confirm the application listens on
0.0.0.0instead of127.0.0.1orlocalhost
Amazon Web Services Troubleshooting
ECS and Fargate
| Error Message | Meaning | Resolution |
|---|---|---|
ResourceInitializationError | The container has no internet access. | If you deployed into a public subnet, enable Assign Public IP. If you deployed into a private subnet, ensure the VPC has a working NAT Gateway. |
Target group failed health checks | The app does not return a successful response for the load balancer health check. | Make sure your application returns 200 OK on /, or change the AWS target group health check path to a route that does. |
EC2
Website not reachable on port 80 or 443
The security group attached to the EC2 instance is blocking inbound web traffic.
Open the AWS Console, find the instance, open its security group, and add inbound rules allowing:
- HTTP on port
80 - HTTPS on port
443
For public sites, these rules typically allow traffic from 0.0.0.0/0.
Cloudflare Troubleshooting
Cloudflare provides global proxying and SSL protection, but domain routing can fail if its SSL or API settings are misconfigured.
| Error Message | Meaning | Resolution |
|---|---|---|
ERR_TOO_MANY_REDIRECTS | Cloudflare is creating an SSL redirect loop. | In the Cloudflare dashboard, open SSL/TLS and change the encryption mode from Flexible to Full (Strict). |
Error 521: Web Server is Down | Cloudflare reached the origin, but the app is down or crashed. | Check your application logs in the Zynnode dashboard to see why the process stopped running. |
| Zynnode cannot add your domain | The wrong Cloudflare credential type was provided. | Use an API token with Zone Edit permissions instead of a global API key. |
Common Application Mistakes
If the deployment succeeds in Zynnode but the website is still broken, the issue is often in the application configuration.
- Host Binding: If the app listens on
localhostor127.0.0.1, it will reject external traffic. Fix: listen on0.0.0.0or::instead. - Missing Environment Variables: If your code depends on secrets such as a Stripe key or database URL, those values must be configured in the Zynnode environment variable manager before deployment.
- Hardcoded Ports: Do not hardcode a port such as
3000. Always read the assigned runtime port from the environment, such asprocess.env.PORTin Node.js.
If a deployment finishes but the application never becomes healthy, check host binding, required environment variables, firewall rules, and runtime port usage before assuming the platform failed.