ERROR: Protocol "https:" not supported. Expected "undefined"

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?

############ ERROR MSG ##################
ERROR: Protocol “https:” not supported. Expected “undefined”

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

############ ERROR MSG ##################

Information on your n8n setup

  • **n8n version:**1.0.5
  • **Database default: ** SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

are your webhooks running over http or https?

Hi @rodrigonrs, I am so sorry for the trouble.

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.

@rodrigonrs Can you please check if the url that you are using in the HTTP Request node starts with https://?

Https, but not just webhook, even when a use Google Sheets node, i got the same error.

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.

Hey @rodrigonrs,

Can you share more information on your configuration? Are you using docker if you are can you share your run command or compose file?

We recently switched from nodejs 16 to 18, which ships with an updated version of OpenSSL, and drop some legacy SSL stuff by default. This is why you might see these issues on newer versions of n8n, but not on the older versions.
Switching back to nodejs 16 doesn’t make sense as it goes end-of-life in about 40 days..

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 :pray:.

3 Likes

@netroy Has there been any update on this? We are encountering the same issue.

Are you running n8n via docker or npm?
unfortunately @rodrigonrs hasn’t updated the original post with more info, and without that information we don’t even know where to start looking.

Is there a way to submit information privately. Due to security concerns I am weary of posting the details we are encountering.

Hey @jmullins

You can post here and replace any sensitive values with a similar data type, as a start though it would be good to know if you are using docker or npm, which version of n8n you are running, the node you are seeing this issue with and if you use a proxy.

You could also DM a member of the team but generally we advise against that as it can lead to a longer resolution time if they are away.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.