N8n on Google Cloud Run - Deploys Successfully but "Cannot GET /

Hello,

I have successfully deployed n8n on Google Cloud Run with a Cloud SQL (PostgreSQL) database, but I am stuck at the “Cannot GET /” error page. The application starts successfully, the health checks pass, and the logs show that the database connection is established, but I cannot access the UI.

I have tried both the latest tag and a specific version (n8nio/n8n:1.41.0) with the same result.

Here is my full configuration, which seems correct:

  • Platform: Google Cloud Run
  • Database: Google Cloud SQL (PostgreSQL 14) connected via the secure Cloud SQL Connector (Unix socket).
  • Deployment Status: Successful (Green checkmark, container passes TCP probe on port 8080).
  • IAM Permissions: The Cloud Run service account has the “Cloud SQL Client” role.
  • Error: Browser shows “Cannot GET /” and logs show a 404 error for the GET request to the root (/).

Environment Variables:

DB_TYPE=postgresdb DB_POSTGRESDB_HOST=/cloudsql/my-gcp-project-id:us-central1:my-n8n-db-instance DB_POSTGRESDB_DATABASE=n8ndb DB_POSTGRESDB_USER=n8n DB_POSTGRESDB_PASSWORD=[SET VIA SECRET] N8N_HOST=https://n8n-my-service-url.us-central1.run.app N8N_EDITOR_BASE_URL=https://n8n-my-service-url.us-central1.run.app/ WEBHOOK_URL=https://n8n-my-service-url.us-central1.run.app/ N8N_RUNNERS_ENABLED=true N8N_BASIC_AUTH_ACTIVE=true

I have tried N8N_HOST with and without a trailing slash. I have confirmed all permissions and connection details. The application is definitely running, but the internal routing seems to be failing.

Could this be a bug or is there a configuration variable I am missing?

Thank you for your help.

Same issue. Following….

Any updates on this? I am having exactly the same issue.

Any news? stuck on the same thing.

I’ve deployed the application on the same cluster few months back and it works, now i’m using the same configuration and deployed another n8n setup on the same k8s cluster and I get the same issue.

I’ve just upgraded and have this issue.

I am experiencing the same issue and realised it’s attempting to log in via port 3307 instead of 5432, which is specified in the ENV. Could someone from n8n investigate this?