Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Problem in Node [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28546•Fetched 2026-04-16 07:04:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
brendan616brendan616
Participants
brendan616brendan616n8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  1. The workflow "Send Dietaries Email From Booking View" is failing with a connection error when making HTTP Request calls to Supabase. Existing workflows on the same account hit the exact same domain successfully. The issue affects every new workflow I create, even when I copy working nodes directly from existing workflows that are proven to work.
  2. Error Message: "Problem in node 'Fetch Booking': The connection cannot be established, this usually occurs due to an incorrect host (domain) value"
  3. ERROR DETAILS
  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

  1. The workflow "Send Dietaries Email From Booking View" is failing with a connection error when making HTTP Request calls to Supabase. Existing workflows on the same account hit the exact same domain successfully. The issue affects every new workflow I create, even when I copy working nodes directly from existing workflows that are proven to work.

  2. Error Message: "Problem in node 'Fetch Booking': The connection cannot be established, this usually occurs due to an incorrect host (domain) value"

  3. ERROR DETAILS

ENOTFOUND

Full message

getaddrinfo ENOTFOUND rsvlqczrcvwwrytdrikyg.supabase.co Request

{ "headers": { "apikey": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6InJzdmxxY3pyY3Z3cnl0ZHJpa3lnIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImlhdCI6MTc3MzIwNDk5NiwiZXhwIjoyMDg4NzgwOTk2fQ.SyjFQTmieJrbIQ24g92Y9QpbiAzTlnklreJXB2dgmTQ", "authorization": "hidden", "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/;q=0.9, image/;q=0.8, /;q=0.7" }, "method": "GET", "uri": "https://rsvlqczrcvwwrytdrikyg.supabase.co/rest/v1/bookings?id=eq.69afbb5a-f2d5-4681-a1e4-b00ff1e73848&select=id,customer_name,customer_email,tour_date", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "sendCredentialsOnCrossOriginRedirect": false, "followAllRedirects": true, "timeout": 300000, "encoding": null, "json": false, "useStream": true }

Debug info

core

  • n8nVersion: 2.14.2
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-15T06:12:21.925Z

extent analysis

TL;DR

The issue is likely due to a DNS resolution failure for the Supabase domain, causing the connection to fail.

Guidance

  • Verify the DNS resolution of the Supabase domain rsvlqczrcvwwrytdrikyg.supabase.co to ensure it is correctly configured and resolvable.
  • Check the network configuration and DNS settings of the environment where the workflow is running to ensure they are correctly set up.
  • Compare the DNS resolution of the Supabase domain between the working and non-working workflows to identify any differences.
  • Consider using a tool like dig or nslookup to troubleshoot the DNS resolution issue.

Notes

The issue seems to be specific to new workflows, and the error message indicates a DNS resolution failure. The fact that existing workflows on the same account are working successfully suggests that the issue is not with the Supabase domain itself, but rather with the environment or configuration of the new workflows.

Recommendation

Apply workaround: Use a different DNS resolver or configure the environment to use a specific DNS server to resolve the Supabase domain, as the current DNS resolution is failing.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING