Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

ORDS cannot be reached using public IP

edited Aug 12, 2024 9:56AM in Autonomous Database 1 comment

Summary:

We have several BIP reports where we have defined the data source for ORDS (see definition below) and they were working fine until around 19-Jul when the console was upgraded.


After the upgrade we cannot reach the REST APIs defined in ATP using that public IP (see result below) and always we get a 503 error for all our API calls.

But if we use OCID instead of the public IP it works.

Anyone knows why after the upgrade the ORDS IP does not work, is there anything we should do to make again working the APIs from ATP? We will use the OCID as a workaround but the idea is to use the data source defined from the beginning.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!