N8N + SUPABASE (Self Hosted) - Interrupted connexions

[Contact_TC_Ltd]

Describe the problem/error/question

Since May 28, 2025, my Supabase node loses connection every other time.
When I check my credentials, it connects every other time, and the other time it gets stuck.

When I click on the Supabase node, the behavior is the same. It displays the tables, and the next time, it displays an error message: “Error fetching options from Supabase.”

No changes have been made to Supabase.
I have another VPS Hostinger with a N8N freshly preinstalled and the issue is the same.

Thank you for your help

What is the error message (if any)?

“Error fetching options from Supabase.”

Please share your workflow

## Share the output returned by the last node
No output


## Information on your n8n setup
- **n8n version:1.94.1 (N8N preinstalled on HOSTINGER VPS) 
- **Database (default: Supabase (directly from supabase.com: Free version):**
- **n8n EXECUTIONS_PROCESS setting (default:): Main
- **Running n8n via (Docker)
- **Operating system:Linux Ubuntu 24.02

[Erick_Torres]

1. Verifying Logs in Docker
   To inspect the n8n container logs and look for errors such as ETIMEDOUT, ECONNRESET, or DNS issues, you can run the following command:
   docker logs <n8n_container_name>

2. Connectivity Testing from the VPS
   To verify direct connectivity from your VPS to Supabase, you can use curl:
   curl https://<supabase_url>.supabase.co/rest/v1/

Supabase Free Plan Limits:
Although Supabase offers unlimited API requests on all plans, there are other limits on the free plan that may affect performance:
Data Transfer: Limit of 5 GB of bandwidth per month.
Supabase
Maximum File Size: Limit of 50 MB per file.
Supabase
Maximum Execution Time for Edge Functions: 150 seconds.
Email sending limits: 2 emails per hour for authentication-related endpoints.

It’s important to check if any of these limits are being reached, as they could cause intermittent errors.

[Contact_TC_Ltd]

Hi,

Thank you for your message.

None of these limits have been reached. Only one table with only 5 records.
And nothing else.

Nothiong special in the log.

I have created this connexion with dbeaver and no issue to connect.

In N8N, finally I created a Postgres node and it’s working very well.

I continue to try to understand for supabase node…

[Contact_TC_Ltd]

Hi,

Something very weird.

After I executed this commande : 1. curl https://xxxxxxx.supabase.co/rest/v1/
everything came back to a normal situation.

No interrupted connection anymore
supabase node works very well.

Any idea about this ?