HTTPS Requests Fail in n8n HTTP Request Node Behind Proxy

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I'm encountering an issue with the HTTP Request Node in n8n when using HTTPS URLs. While HTTP URLs work fine, HTTPS requests fail when triggered from the n8n web interface. I've seen similar topics in the community, but with the removal of N8N_USE_DEPRECATED_REQUEST_LIB, I'm looking for updated advice on this matter.

My Setup:

I have added the necessary certificates to the container's OS.
The container is running on Kubernetes and does not have direct internet access, so a proxy is being used.
Testing an HTTPS URL with curl inside the Kubernetes n8n pod works fine.
However, using the HTTPS URL in the n8n web interface (HTTP Request Node) and clicking “Test Workflow” fails.

What I’ve Tried:

Proxy Configuration: The proxy is properly configured and the HTTPS URL is whitelisted.
Certificates: All required certificates have been added to the trusted store.
Container Testing: Running curl inside the n8n container succeeds.
Error Message: The n8n web interface returns a default Nginx error:

PLAINTEXT
400 - "<HTML><HEAD>\r\n<TITLE>Request Error</TITLE>\r\n</HEAD>\r\n<BODY>\r\n<FONT face=\"Helvetica\">\r\n<big><strong></strong></big><BR>\r\n</FONT>\r\n<blockquote>\r\n<TABLE border=0 cellPadding=1 width=\"80%\">\r\n<TR><TD>\r\n<FONT face=\"Helvetica\">\r\n<big>Request Error (invalid_request)</big>\r\n<BR>\r\n<BR>\r\n</FONT>\r\n</TD></TR>\r\n<TR><TD>\r\n<FONT face=\"Helvetica\">\r\nYour request could not be processed. Request could not be handled\r\n</FONT>\r\n</TD></TR>\r\n<TR><TD>\r\n<FONT face=\"Helvetica\">\r\nThis could be caused by a misconfiguration, or possibly a malformed request.\r\n</FONT>\r\n</TD></TR>\r\n<TR><TD>\r\n<FONT face=\"Helvetica\" SIZE=2>\r\n<BR>\r\nFor assistance, contact your network support team.\r\n</FONT>\r\n</TD></TR>\r\n</TABLE>\r\n</blockquote>\r\n</FONT>\r\n</BODY></HTML>\r\n"

Question:

Why does the HTTPS request fail only in the n8n web interface while working via curl in the pod? What can be done to resolve this issue?

Additional Information:

n8n version: 1.68.0
Database: pgsql
n8n EXECUTIONS_PROCESS setting: default
Running n8n via: Docker
Operating system: Docker image on Alpine Linux

Please let me know if additional details are needed.

Comments 0

•

Answers 0

•

0 Answers

Discussion

No comments yet.