Hi @peter-o-brien-oracle I'm currently facing an issue with ORDS and APEX setup behind the Load balancer that I believe requires your attention. Here's a summary of the problem:
Architecture Details:
VCN: Same VCN (Security Lists configured to allow traffic for LB)
Public Subnet: LoadBalancer
Private Subnet: DBCS (Oracle Base Database)
LoadBalancer Configuration:
Listener: Configured with domain and SSL for port 8443
Backend: DB node IP address with port 8182
Health Check: TCP port 8182 (Health Check Critical if provided HTTP 8182)
ORDS and APEX Configuration:
ORDS(23.2.2) running Standalone and Oracle APEX (22.1) are installed on the DB node of the Oracle Base Database.
Configured ORDS Standalone with HTTP port 8182.
Firewall Settings on DB Node:
- Updated iptables on the DB node with the following rules:
-
Outgoing HTTP: `-A OUTPUT -p tcp --sport 8182 -m state --state ESTABLISHED -j ACCEPT`
-
Incoming HTTP: `-A INPUT -p tcp --dport 8182 -m state --state NEW,ESTABLISHED -j ACCEPT`
-
Incoming TCP: `-A INPUT -p tcp -m tcp --dport 8182 -j ACCEPT`
Current Issue:
Testing access:
-
Accessing `http://loadb_ip:8443/ords` results in the ORDS landing page and APEX working correctly.
-
Accessing `[https://test.vpcy.co.uk:8443/ords](https://test.vpcy.co.uk:8443/ords) shows the ORDS landing page but encounters an APEX CORS error after logging into apex.
Possible Reason for the Issue:
I suspect that the CORS error may be due to the LoadBalancer allowing HTTPS traffic to reach the APEX without terminating it before when passed to the OCI region.
Your guidance and expertise in this matter would be highly valuable. Please let me know if there's any further information you require or any actions I should take in configuring LB/ORDS STANDALONE/APEX.
Thank you for your attention to this matter.