Connect N8N to Oracle APEX ORDS REST API

Description:

I have an Oracle APEX Public Workspace with a RESTful API that retrieves data from a database table.
The REST API uses Basic Authentication and works perfectly when tested from Postman.

Scenario:

APEX environment: Oracle APEX 24.x (Public Workspace on oracleapex.com / or self-hosted on-premise)

API Example:https://oracleapex.com/ords//MASTERDATA/API/customer

Authentication: Basic Auth (username + password)

Testing: Works fine in Postman (returns JSON data)

n8n setup:

When I run n8n locally (on my laptop using Docker), the HTTP Request node connects successfully and retrieves data.

When I run from N8N Pro Account or n8n on Hostinger Cloud (n8n.io / VPS), the same HTTP Request node times out with error:
ERROR: The connection timed out
I have already:

Increased Timeout in node options (e.g., 120000 ms)

Enabled Retry on Fail

Verified API works from the same machine using Postman (so credentials and endpoint are fine)

Problem:

N8N Pro Account and Hostinger n8n instance cannot reach my Oracle APEX REST API endpoint — it always returns “Connection timed out”, while local n8n connects successfully.

What I suspect:

Network reach ability:
N8N Pro Account or The Hostinger n8n server might not be able to reach my on-premise Oracle APEX host (not publicly accessible or blocked by firewall).

HTTPS / TLS issue:
If the on-premise APEX server uses a self-signed SSL certificate, the cloud n8n server might reject the connection.

Outbound firewall or proxy restriction:
N8N Pro Account or Hostinger may restrict outgoing HTTP/HTTPS connections.

What I’ve Tried:

Verified endpoint with curl and Postman from different networks.

Increased timeout and retry count.

Checked ORDS and APEX access logs (no incoming requests from Hostinger server).

Confirmed same credentials and endpoint work from local Docker n8n.
Question:

How can I make N8N Pro Account or (hosted on Hostinger / n8n.io Cloud) successfully connect to my Oracle APEX REST API that works fine from Postman and local n8n?
Do I need to expose my on-prem APEX API differently (e.g., via HTTPS with public certificate, or ngrok tunnel)?

Could it be that Oracle is blocking the IP tables of the providers you use by default? Are you able to test adding an IP whitelist table?
n8n has one here for the cloud version: