Error message swallowed in webhook operation

[Militao36]

Describe the Bug

I'm having problems, I have a flow, which is called manually. After that I make an HTTP call, but it gives errors, the url used is public, in the browser it works.

URL: https://backend.bmspedidos.com.br/crash

To Reproduce

1. Create test flow
2. Linked flow, with call HTTP
3. Execute flow

Hosting Strategy

Self-Hosted (Custom)

[paescuj]

Props like error.response.status might not exist, in that case the actual error message is swallowed by the cannot read properties of undefined error.
First, we should do proper typing, e.g. by checking the error against isAxiosError and then handle properties which might be undefined accordingly.

directus/api/src/operations/request/index.ts

Lines 37 to 44 in b018963

	} catch (error: any) {
	throw JSON.stringify({
	status: error.response.status,
	statusText: error.response.statusText,
	headers: error.response.headers,
	data: error.response.data,
	});
	}

[paescuj]

/linear

[github-actions]

🤖 Linear issue created! Maintainers can access it here: ENG-879

[Militao36]

@paescuj I think you misunderstood, this url publishes, it should return success, accessing it directly works, however the flow doesn't.

[XanManZA]

I want to report in here that I can reproduce this exact error on Directus 9.24.0.

1. Create new Directus 9.24.0 project with CLI using Postgres as Database
2. Create a flow with a Webhook action calling just for example /users/me
3. Get the error Cannot read properties of undefined (reading 'status') in the Flow logs

Findings:

• This doesn't happen when calling /users/me directly at all through Postman and only happens in Flows.
• There are no errors in the Directus server logs.
• Strangely this is not happening on my Docker Compose cloud hosted version of Directus.

[XanManZA]

Ok am I reporting back here that 17906 lead me towards the right path. Setting IMPORT_IP_DENY_LIST to an empty string solved this.

[paescuj]

The problem is that the request is failing for some reason (e.g. server temporary unavailable or like Requested URL "https://localhost:8055/users/me" resolves to a denied IP address for the /users/me request) but this error isn't handled correctly at the moment thus it gets swallowed.

[Militao36]

@paescuj @XanManZA The server is always available. When running the flow the server is always available but it fails. Maybe it's because I use nginx reverse proxy, and it generates this error. But about 2 weeks ago it was working, I just updated directus.

Server framework description: I am using expressjs, along with nginx as reverse proxy. My app is always online, I've tested multiple endpoints and none of them work.

[Militao36]

I downloaded the directus source code and ran the whole flow on my machine, with the same URL it worked, but the directus call I'm using doesn't work. It is in the latest released version

Conditions: I'm using the same bank as my production app (directus).

[rijkvanzanten]

Fixed in #18080