Troubleshooting ENETUNREACH Error in n8n’s Supabase Postgres Chat Memory Node

Based on your description and error message, it seems that n8n is unable to reach your Supabase Postgres database from the Postgres Chat Memory node. Here are some steps and considerations to help troubleshoot the issue:

1. Check Network Connectivity & IP Restrictions

The error code ENETUNREACH indicates that the network is unreachable. Since you’re using Supabase, make sure that the public IP range from which n8n Cloud is trying to connect has been allowed in your project's Network Restrictions. Verify the following:

• That your Supabase project’s inbound IP restrictions (configured on the Database Settings) include the IP addresses or ranges used by n8n Cloud.
• If you don’t see the Network Restrictions section in your project’s settings, consider updating your Postgres version as described in the Supabase documentation.

2. Verify Your Connection Details

Ensure that the Postgres connection details (host, port, database name, user, and password) entered into the Postgres Chat Memory node are correct. In particular:

• Confirm that the Host or domain name provided matches the one in your Supabase connection string.
• Confirm that port 5432 is correct and that no firewall or other network rules are blocking it.
• Check if your connection string includes an IPv6 address (as seen in the error) and whether your network can properly route IPv6 traffic. If IPv6 connectivity is problematic, try using the IPv4 address if provided.

3. SSL & Connection Pooling Settings

If your Supabase connection string uses SSL or connection pooling settings, double-check these in your n8n credential configuration. For instance:

• If you’re using SSL, verify that the Ignore SSL Issues option is set appropriately if there are any certificate-related problems.
• If connection pooling is enabled in Supabase, make sure your n8n configuration is compatible.

4. Supabase-Specific Considerations

Supabase often provides an API settings page with the connection string. Make sure you have:

• Replaced any placeholder passwords in the connection string with your actual database password.
• Selected the proper settings for connection pooling and session mode.

5. n8n Credentials and Node Setup

Since the Postgres Chat Memory node relies on the Postgres credentials defined under /integrations/builtin/credentials/postgres/, review that the credential parameters (including optional SSH tunnel settings) are correctly configured. Note that the Agent node does not support SSH tunnels, so confirm that if you are using one, it’s only applied where supported.

---

By verifying network restrictions, ensuring correct connection details (possibly using the IPv4 address if needed), and confirming SSL/connection settings, you should be able to troubleshoot the ENETUNREACH error. If the issue persists, consider checking with your network administrator or Supabase support to ensure that incoming connections from n8n Cloud are permitted.