Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

APEX Service down with 403 Forbidden

Travis CaruthSep 4 2024

Upon attempting to login to the builder this morning on my APEX service instance in OCI, I'm getting met with this error message:

https://redacted.adb.us-ashburn-1.oraclecloudapps.com/ords/wwv_flow.accept?p_context=workspace-sign-in/select-workspace/1409505246503

This is also showing on a full ADB with APEX running in OCI:

Last I checked, both instances hadn't received the 24.1.1 patch, but this seems more like an ORDS issue to me. Regardless, it's blocking my work and preventing features from being shipped to clients.
This post has been answered by Travis Caruth on Sep 5 2024
Jump to Answer

Comments

Travis Caruth

The Oracle support portal is also down, so that's unfortunate. Checked multiple devices on different networks.

Travis Caruth

Miraculously APEX is available again and looking at the version we're now on 24.1.1.

Would love to know what the heck happened but until then I guess it's solved?

Travis Caruth

I've opened an SR to address this. This isn't the first time the OCI APEX instances have been unreachable, and I'm told the forums and folks here

have zero insight to such things

Travis Caruth
Answer

I filed a ticket with support and was told this behavior is expected while APEX is being upgraded. All my instances are in the same region, so the patch was being applied to all of them at the same time. Another patch is upcoming (24.1.3), so we might see another “outage” during that upgrade.

I've suggested they show something other than an error screen during the upgrade process.

FYI to Oracle Cloud Infrastructure APEX users

Marked as Answer by Travis Caruth · Sep 5 2024
InoL

This is totally expected to happen, and one of the reasons we don't use Autonomous Database.

With DB as a Service, you have full control over when to upgrade or patch, when to test etc.
For some of our bigger applications it is just impossible to keep up with two major APEX versions per year. And yes, almost every APEX version upgrade breaks something.

1 - 5

Post Details

Added on Sep 4 2024
#ap, #apex-discussions
5 comments
505 views