In every request I’m making to an external domain, the error occurs (HTTP Code
ERR_INVALID_PROTOCOL) .
The error is occurring in Google authentication, in the HTTP Request node, Google Sheets node.
I updated to V1.0 and since then the error has been occurring.
Any solution?
Protocol “https:” not supported. Expected “undefined”
HTTP Code
ERR_INVALID_PROTOCOL
Stack
NodeApiError: Protocol "https:" not supported. Expected "undefined"
at Object.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/v1/GenericFunctions.js:39:15)
at GoogleSheet.getData (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/v1/GoogleSheet.js:38:26)
at GoogleSheet.convertStructuredDataToArray (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/v1/GoogleSheet.js:248:31)
at GoogleSheet.appendSheetData (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/v1/GoogleSheet.js:110:22)
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/v1/GoogleSheetsV1.node.js:84:35)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:646:28)
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:631:53
Can you confirm how exactly you have deployed n8n? Details like the docker compose file, environment variables you might have set (anything confidential can be redacted of course), whether you are using a proxy, reverse proxy, load balancer, etc? Essentially anything needed to reproduce your problem.
is HTTPS, but it has routines that have been working for months without any errors. However, I believe it is some configuration because every NODE that calls an external HTTPS URL is in error.
If you are not using docker, then it’s possible that the issue might be with the underlying root certificates on your OS, and switching to docker might fix the issue for you.
If anyone can share a URL with me that can reliable produce this error on a docker container, I can try to add some kind of fix. but so far, I’ve not been able to reproduce this error.
That said, can you please update the original post to include details like if you are using docker or npm. which operating system? without those critical details it’s difficult to figure out what might be happening here.
not just for n8n, but in general whenever opening a new issue, please always fill out the issue template to save everyone’s time .