Public Address Stuck on "Pending" Status - n8n Application Unreachable in private

Viewed 9

Hi

I'm experiencing a critical issue with my n8n application deployment on ClawCloud Run. Despite the application running successfully, the Public Address remains stuck in "Pending" status indefinitely, making my application completely unreachable from the internet.

Application Details:

  • Application Name: n8n-cuawmton
  • Status: Running (Pod Active for 5+ minutes)
  • Image: n8nio/n8n:stable
  • Resources: 0.5 Core CPU, 1 Gi Memory
  • Port: 5678
  • Public Access: Enabled

Problem Description:

  1. Public Address Status: The public address shows as "Pending" (https://n8n-1nuoineg.eu-central-1.clawcloudrun.com) and never becomes active
  2. Connection Error: Attempting to access the URL results in "ERR_CONNECTION_CLOSED" - the site cannot be reached
  3. Application Health: Pod logs confirm n8n is running correctly and listening on port 5678. The log shows: "Editor is now accessible via: https://n8n-1nuoineg.eu-central-1.clawcloudrun.com"
  4. Resource Usage: Pod shows healthy resource consumption (CPU: 0.21%, Memory: 24.09%), confirming the application is active
  5. Private Address: Also not functioning properly

Troubleshooting Steps Already Taken:

  • Restarted the application multiple times
  • Toggled Public Access off and on
  • Deleted and recreated the entire application
  • Increased memory allocation from 64Mi to 1Gi
  • Verified n8n container is healthy via pod logs
  • All attempts resulted in the same "Pending" status

Suspected Issue:

This appears to be an Ingress Controller or Gateway routing issue on the ClawCloud infrastructure side, as:

  • The pod is running and healthy
  • The application is listening on the correct port
  • Public Access is enabled
  • Yet no route is being established to expose the service externally

Request:

Could you please investigate why the Ingress/Gateway is not properly routing traffic to my application? This issue is preventing me from using the deployed service entirely.

Additional Information:

  • Region: eu-central-1
  • Deployment Time: Multiple attempts over the past 24 hours
  • Same issue occurs with fresh deployments

Thank you for your assistance in resolving this issue.

0 Answers