Hello, I just switched to the 1.98.0 version and I would like to say there is a problem with the Supabase credentials when you use an internal host (like http://supabase-kong:8000).
{
“errorMessage”: “Protocol "http:" not supported. Expected "https:"”,
“errorDetails”: {
“rawErrorMessage”: [
“Protocol "http:" not supported. Expected "https:"”
],
“httpCode”: “ERR_INVALID_PROTOCOL”
},
“n8nDetails”: {
“nodeName”: “Supabase”,
“nodeType”: “n8n-nodes-base.supabase”,
“nodeVersion”: 1,
“resource”: “row”,
“operation”: “get”,
“time”: “11/06/2025 14:07:02”,
“n8nVersion”: “1.98.0 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: Protocol "http:" not supported. Expected "https:"”,
" at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1477:10)“,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)”,
" at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1763:11)“,
" at ExecuteContext.supabaseApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Supabase/GenericFunctions.ts:56:10)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Supabase/Supabase.node.ts:279:14)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1185:9)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1534:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2098:11"
]
}
}
Could it be that your supabase project was paused and restored recently? This announcement says that: “Projects restored from 1st May 2025 will no longer be restored with the legacy API keys.” This might not be a change in how n8n works, but a new restriction on how API keys work in Supabase. At least that’s the first thing I would try to check. Edit: This wouldn’t apply to a self-hosted, non-https Supabase host.
I didn’t change anything at all and did not restore anything. It just worked with the local http address in 1.94.1, and not in 1.95.0. I changed to an https address
Your last message sounded like you have the issue resolved (or at least worked-around) by changing your Supabase host to https. Did I understand that correctly?
The error message suggests n8n’s Supabase node is, in recent releases, no longer correctly observing the protocol portion of the URL and may now be using the incorrect client type (https client when the URL is http://...) It’s possible this was a side effect of a recent change related to the use of schemas.
@Joe_Peres The Ignore SSL Issues (insecure) option on an HTTP Request node only affects SSL/https certificate related errors. The connect URL in the original post was http://supabase-kong:8000, which should not involve https at all. Also, BTW, there is no “Ignore SSL” option on the Supabase node or its corresponding credential type.
Hello hubschrauber , I use the external address in Supabase. I would prefer to use an internal one (http://supabase-kong:8000) which will be in http.
Do you know why something has changed in the 1.98.0 ?
@hubschrauber my mistake. I’ve found the Postgres node works much better with supabase and with my local instance I use the Postgres node with ignore ssl.
No, I don’t know why the connection logic would have changed. The link I included to the changes in the Supabase node’s GenericFunctions.ts was just a guess. I’m not exactly sure how the change from the || operator to the ?? operator on that line might affect the connections, but it’s the only thing I saw that seemed like it might be related.
n8n’s developers will probably have to do some testing to see if the http vs https handling got broken somehow. I’ll flag your original message as a potential bug report in hopes they’ll capture some of this conversation and track it internally.
