Critical Network Error: Newly created n8n Spaces cannot resolve any external host

#6
by will168 - opened

Hello, I am experiencing a persistent, critical network issue with n8n on Hugging Face Spaces.

My Space ID: will168-n8n-free.hf.space (Please also list any new space names you created)

Problem:
Any n8n workflow fails to connect to any external service (like Telegram, Discord, etc.). The error is always The connection cannot be established, this usually occurs due to an incorrect host (domain) value.

Debugging steps I have already taken:

I used the "Execute Command" node to test connectivity.

ping api.telegram.org returns a bad address error, indicating a DNS resolution failure.

I have tried restarting the Space multiple times. The problem persists.

I have tried the "Factory Rebuild" option. The problem persists.

I have tried "Duplicate this Space". The new, duplicated Space has the exact same issue.

Finally, I have completely DELETED my old Space and created a brand new one from scratch. This new Space still has the exact same DNS failure from the moment it was created.

This proves the issue is not with my specific instance but likely with the underlying n8n template or network configuration on the Hugging Face platform. Could you please investigate this systemic issue? Thank you.

Sign up or log in to comment