Telegram ERROR: Bad request - please check your parameters

browse · June 26, 2023, 3:18pm

Describe the problem/error/question

My n8n instance run in a isolated network and I need to use proxy.
I set http_proxy and https_proxy in Docker container and I can see logs in the proxy.
When I use Telegram I got some errors and no idea how to solve it.

What is the error message (if any)?

ERROR: Bad request - please check your parameters
400 The plain HTTP request was sent to HTTPS port 400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.18.0

NodeApiError: Bad request - please check your parameters
    at Object.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/GenericFunctions.js:82:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/Telegram.node.js:1677:36)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:652:28)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:596:53

Please share your workflow

Share the output returned by the last node

The output is the error I paste above.

Information on your n8n setup

n8n version: 0.231.3
Database (default: SQLite): PostgreSQL
n8n EXECUTIONS_PROCESS setting (default: own, main): not set, use the default settings
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: NixOS

mcnaveen · June 27, 2023, 6:53am

Hi @browse

I suspect you’re setting the wrong Chat ID

Here is a quick overview:

Chat ID of the Person starts with number (All Numbers)
Chat ID for the Group or Channel starts with - (hypen)

I think you’re setting @username instead of Chat ID.

I might be wrong, Just saying based on the workflow you shared.

browse · June 27, 2023, 7:21am

@mcnaveen Thanks for you reply.
I’ve also tried NocoDB and it’s the same error.

My proxy works fine and was online almost 3 years. It’s was used in various other tools.
I deploy n8n in another environment without proxy. It works well.
But if n8n+proxy, it crashes.

It’s weird that I can see the request is https in the proxy,but the server respond “400 The plain HTTP request was sent to HTTPS port”.

I need to know what happend between the proxy and the Telegram/NocoDB server.
I should dig deeper with some mitm tools such as mitmproxy or burpsuite.

browse · June 27, 2023, 8:06am

After doing some mitm work, I’ve found the bug.It’s n8n’s fault.

Here is the http request from n8n:

GET http://n8n.example.com:443/api/v1/db/meta/projects/db/tables HTTP/1.1
Accept: application/json
xc-token: my_token
User-Agent: axios/0.21.4
host: n8n.example.com
Connection: close

The host in the credential is https://n8n.example.com.Why n8n send http request to 443 port?

Jon · June 27, 2023, 2:43pm

Hey @browse,

That doesn’t look right to me, Is your https proxy using an https value for https_proxy or http? When I did some testing recently I was using Squid and my env options were…

http_proxy=http://172.19.0.2:3128
https_proxy=https://172.19.0.2:3129

Has your n8n installation ever worked with your proxy or has it always failed?

Jon · June 27, 2023, 2:53pm

Just done a very quick test and in my proxy access log when testing a telegram credential I can see…

1687877459.749 2349 172.19.0.4 TCP_MISS/200 682 GET https://api.telegram.org/bot[REMOVED]/getMe - HIER_DIRECT/149.154.167.220 application/json

The request is also acknowledged in the n8n interface with a successful connection test so it looks like the http_proxy and https_proxy settings are working as expected at the moment.

browse · June 27, 2023, 2:55pm

@Jon My proxy is an http proxy. I set the env like:

http_proxy=http://192.168.1.1:1081
https_proxy=http://192.168.1.1:1081

So the https_proxy should have a proxy start with https?
I just think it’s like the environment in linux env.

browse · June 27, 2023, 3:03pm

I don’t know how n8n concatenate the request url and how axios use the proxy.
But I think the request url scheme shouldn’t be obtained from the proxy scheme.

Jon · June 27, 2023, 3:06pm

Hey @browse,

The underlying issue comes from Axios and they have many issues opened about it…

github.com/axios/axios

HTTPS over HTTP Proxy Fails

opened 04:28AM - 05 Nov 20 UTC

closed 05:34PM - 12 Jun 22 UTC

sidharthv96

#### Describe the bug HTTPS over HTTP Proxy Fails with 500 handshakefailed on mcafee proxy. `mcafee initialize server context:handshakefailed:server state 1:state 9:Application response 500 handshakefailed` With HTTP_PROXY and HTTPS_PROXY set, curl works but axios.get fails. #### To Reproduce ```ts import axios from 'axios'; (async () => { try { console.log(await axios.get('https://github.com/')); } catch (e) { console.log(e); } })(); ``` #### Expected behavior Request should succeed. #### Environment - Axios Version [0.21.0] - Node.js Version [v12.18.3] - OS: [OSX 10.15.7] #### Additional context/Screenshots N/A #### Current workaround Install `global-agent`, remove the HTTP_PROXY env vars and set GLOBAL_AGENT_HTTP_PROXY. Add `import 'global-agent/bootstrap';` to index.

github.com/axios/axios

Proxy support does not work properly with CONNECT on https requests

opened 06:31PM - 16 Mar 22 UTC

gm-ghanover

#### Describe the bug Using Axios 0.26.1 behind a corporate HTTP tunneling prox…y to an HTTPS destination, once the proxy connection is made, a POST method is issued, rather than a CONNECT to establish the TLS tunnel to the destination host where the POST should be sent. Result is **Error: socket hang up**, as the proxy expects a CONNECT to be issued and drops the connection Specifically, using wireshark to monitor the activity of the script goes as follow: > TCP SYN < TCP SYN, ACK > TCP ACK > HTTP POST < TCP FIN, ACK > TCP ACK ![axios_pcap](https://user-images.githubusercontent.com/15218042/158659772-3d084e3b-8ab1-4f99-8c4d-0a54ed697ed4.png) If you use curl with the same environment, the packets are as follows: > TCP SYN < TCP SYN, ACK > TCP ACK > HTTP CONNECT < HTTP Connection established > TCP ACK > TLS Client Hello < TLS Server Hello ... encrypted POST and response follows ![curl_pcap](https://user-images.githubusercontent.com/15218042/158659774-5c84d76a-3370-4acb-9a5d-f9270de12bf7.png) #### To Reproduce ```bash export http_proxy="http://user:[email protected]:80" export https_proxy="http://user:[email protected]:80" ``` ```js http.post('https://api.github.com/user/repos', {}); ``` #### Expected behavior When connecting to an HTTPS server through a tunneling HTTP proxy, the CONNECT method should be used to establish the TLS handshake before issuing the POST #### Environment - Axios Version 0.26.1 - Adapter HTTP - Node.js Version 14.8.0 - OS: Windows 10 (10.0.19042.1526)

At the moment the best option is to configure the proxy to have an HTTPS listener.

browse · June 27, 2023, 3:10pm

@Jon So it’s axios’s fault. I’ll subscribe this issue Proxy support does not work properly with CONNECT on https requests · Issue #4531 · axios/axios · GitHub.
Thanks for your help.

Jon · June 27, 2023, 3:11pm

@browse not really a big fan of the blame game, I believe there could be things we can do to work around this limitation but at the same time the proxy could also be configured for it as well

browse · June 27, 2023, 3:30pm

Sorry, I mean the origin cause of the bug is from axios.
Thanks for your hard work and patience.

Jon · June 27, 2023, 3:36pm

In that case… yes

system · July 4, 2023, 3:37pm

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