Hi There,
I know this has probably been hashed a bit, but I have created a new google cloud project and follow the steps this link Google Cloud Run | n8n Docs
and get this error
No network connection. Workflow changes will be saved once the connection is restored.
literally exactly the same steps, any ideas how to solve this?
Hi @Chris_Bradley this always happens due to either starting fresh n8n instance when things are still booting up or sometimes with not configuring the instance correctly, i recommend reading some of these:
thanks @Anshul_Namdev
I agree completely, i have literally following this guide exactly.
I followed the guide step by step for Durable mode and have this issue? Fresh GCP Project
@Chris_Bradley Maybe checking logs of the cloud and debugging it that way is the only thing we can do here. This is strange although but lets do the next best thing by seeing any unusual thing in the logs, meanwhile you can try n8n cloud for backup it is really stable!
I kind of thought the same, that it was super odd it didnt work I just reinstalled it.
havent seen any errors in the logs as of yet
YALM seem pretty reasonable.
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
name: n8n
namespace: '327606339108'
selfLink: /apis/serving.knative.dev/v1/namespaces/327606339108/services/n8n
uid: e618ea5c-355d-4ed5-ba33-c8093ed546a6
resourceVersion: AAZKm069SE8
generation: 1
creationTimestamp: '2026-02-12T07:18:39.383861Z'
labels:
cloud.googleapis.com/location: us-central1
annotations:
run.googleapis.com/client-name: gcloud
run.googleapis.com/client-version: 551.0.0
serving.knative.dev/creator: [email protected]
serving.knative.dev/lastModifier: [email protected]
run.googleapis.com/operation-id: 1ca7dc98-33b5-4cbd-86f9-02d7db8c2a8c
run.googleapis.com/ingress: all
run.googleapis.com/ingress-status: all
run.googleapis.com/maxScale: '100'
run.googleapis.com/urls: '["https://n8n-327606339108.us-central1.run.app","https://n8n-7aiy6rqk6q-uc.a.run.app"]'
spec:
template:
metadata:
labels:
client.knative.dev/nonce: kusoopfkiq
run.googleapis.com/startupProbeType: Default
annotations:
run.googleapis.com/client-name: gcloud
run.googleapis.com/client-version: 551.0.0
run.googleapis.com/cloudsql-instances: services-487203:us-central1:n8n-db
run.googleapis.com/cpu-throttling: 'false'
run.googleapis.com/startup-cpu-boost: 'true'
spec:
containerConcurrency: 80
timeoutSeconds: 300
serviceAccountName: [email protected]
containers:
- image: n8nio/n8n:latest
command:
- /bin/sh
args:
- -c
- sleep 5;n8n start
ports:
- name: http1
containerPort: 5678
env:
- name: N8N_PORT
value: '5678'
- name: N8N_PROTOCOL
value: https
- name: DB_TYPE
value: postgresdb
- name: DB_POSTGRESDB_DATABASE
value: n8n
- name: DB_POSTGRESDB_USER
value: n8n-user
- name: DB_POSTGRESDB_HOST
value: /cloudsql/services-487203:us-central1:n8n-db
- name: DB_POSTGRESDB_PORT
value: '5432'
- name: DB_POSTGRESDB_SCHEMA
value: public
- name: GENERIC_TIMEZONE
value: UTC
- name: QUEUE_HEALTH_CHECK_ACTIVE
value: 'true'
- name: DB_POSTGRESDB_PASSWORD
valueFrom:
secretKeyRef:
key: latest
name: n8n-db-password
- name: N8N_ENCRYPTION_KEY
valueFrom:
secretKeyRef:
key: latest
name: n8n-encryption-key
resources:
limits:
cpu: 1000m
memory: 2Gi
startupProbe:
timeoutSeconds: 240
periodSeconds: 240
failureThreshold: 1
tcpSocket:
port: 5678
traffic:
- percent: 100
latestRevision: true
status:
observedGeneration: 1
conditions:
- type: Ready
status: 'True'
lastTransitionTime: '2026-02-12T07:19:21.677903Z'
- type: ConfigurationsReady
status: 'True'
lastTransitionTime: '2026-02-12T07:18:40.058509Z'
- type: RoutesReady
status: 'True'
lastTransitionTime: '2026-02-12T07:19:21.645485Z'
latestReadyRevisionName: n8n-00001-qst
latestCreatedRevisionName: n8n-00001-qst
traffic:
- revisionName: n8n-00001-qst
percent: 100
latestRevision: true
url: https://n8n-7aiy6rqk6q-uc.a.run.app
address:
url: https://n8n-7aiy6rqk6q-uc.a.run.app
@Chris_Bradley I cannot see any unusual thing here all pretty standard statements, have you tried posting this on cloud forum?
I think it looks pretty vanilla to me as well, I will try the other forum as well but i guess i figured this was the right place given i was following the n8n guide.
I do normally see this with nginx, so know how to fix it when there is a reverse proxy, but cant see what i am missing.
I think it would work without postgresql so it feels like a setup issue, just cant see it.
@Chris_Bradley Maybe this would bring some help:
Hey,
looks like it is an update from 2.7.x that causing it, due to the breaking change for healthz
@Chris_Bradley That as effected some instance as other instances are working just fine, i am also on the latest stable version i have not felt anything like that, although i still recommend down grading your version to the v2.6.x as it has fixed a lot of issues people were facing after using the latest stable version.
Have just done this and it has resolved the issue on deployment.
I think this is specifically a googleCloud issue.
Glad it fixed the issue! I would say that I have never seen that although if this works for you then cheers! Happy to help! Also let other’s know what is the right solution too by marking that up!
yeah super weird, there is a case raised on github for this so I will put it down to an issue with the version not the deployment setup.
indeed, primary fix with the latest version of n8n with google cloud setup is the one i have suggested. You should raise this on Google Dev forum also. Happy to solve this issue for you.
its really a n8n issue, it has been raised in github on the release by another users so i will just follow that.
the alternative would be to rewrite the healthz setup in n8n 2.7.X, but as this is a wider issue with GR i assume this will get fixed on a later stable release.
Hi @Chris_Bradley That “No network connection” error in n8n usually means the frontend can’t communicate with the backend API.
1. Check Your Webhook URL Configuration
Make sure you’ve set the WEBHOOK_URL environment variable correctly:
It should be your Cloud Run service URL
Don’t include a trailing slash
2. Verify N8N_HOST Environment Variable
Set N8N_HOST to match your Cloud Run URL:
3. Check Authentication Settings
If you’re using basic auth, ensure these are set:
N8N_BASIC_AUTH_ACTIVE=true
N8N_BASIC_AUTH_USER=your-username
N8N_BASIC_AUTH_PASSWORD=your-password
4. CORS Issues
Sometimes Cloud Run needs explicit CORS configuration. Try adding:
N8N_CORS_ORIGIN=* (or your specific domain)5. Port Configuration
Cloud Run expects port 8080 by default. Make sure:
Your container exposes port 5678 (n8n default)
Cloud Run is configured to route to the correct port
Can you share what environment variables you’ve configured?
UPDATE:
after adding N8N_ENDPOINT_HEALTH with value health it seems to work well with v2.9.0
Described here:
Hi,
We are experiencing the same issue after upgrading to 2.7.x, I have tried also latest version - 2.9.0 and the problem still exists.
Similar setup:
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.