How to find differences betweent command curl and HTTP Request

[JulienDelRio]

Hi,

I am back with our proxy issues…

You :

I am trying to call Microsoft Graph API.
I tought I should do like Teams Webhook : a simple Node HTTP Request with proxy set. (working well)
Sadly, it’s not working.

If i do the same with Microsoft Graph, the proxy answer this :

The following error was encountered while trying to retrieve the URL:
https://graph.microsoft.com/beta/users/$count

\n\n
\n
Connection to 2603:1026:3000:118::80 failed.

\n
\n\n
The system returned: (101) Network is unreachable

\n\n
The remote host or network may be down. Please try the request again.

\n\n
Your cache administrator is webmaster.

But if I try a curl directly from the server (by ssh) or via Node Command, it’s working.

Here the example :

I don’t understand why the behavior is different.

Can you help my to find the differences ?

Thank you

Information on your n8n setup

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

[pemontto]

Had maybe a similar problem recently. Are you using OAuth2 authentication in the http node?

Pre 0.230.0 the OAuth authentication requests wouldn’t respect the system wide proxy settings and would time out.

Slightly different scenario but if you have no internet without the proxy it could be the cause

[JulienDelRio]

I think it’s similar to this : Add support for CONNECT method on HTTP Request Node

It seems to be an issue in axios used by n8n…

I will follow the issue in axios github project.

[pemontto]

Good luck! I’ve been waiting on them for a year