@jporter 

Is it just you who is encountering this error?

Did you ensure there is no scheduled maintenance activity for the environment? it seems to me like the environment is unavailable.

Myself and others.   

It varies on when/who the issue happens to.

Environment can be accessible when accessing main link, but adding /admin it is not responding

Hey @jporter,

Given that this is a IFS Managed Cloud environment, i believe that this is the expected behavior as the admin endpoint would be blocked in the proxy. Any changes that needs to be done in the admin portal would need to be requested through a service-now portal. 

Cheers

@Sajith D - that can’t be correct.  How are they supposed to access documentation and add ons?  Also, Active Directory is set up, so how to access as ifsadmin?

Hi @jporter ,

Documentation (<base_url>/documentation.html) and ad-ons (<base_url>/add-on.html) would still be accessible. add-ons would be available in the main page and doc access can be triggered by F1. 

It’s quite interesting what would happen to ifsadmin login as i would image that the admin gateway should also be blocked. Definitely something to check with cloud support i think.

cheers

FYI - I received the following explanation on the “Oops”message

Important:  The “Oops” message means you have Reached the IFS Reverse Proxy server, but are NOT ALLOWED in from your location.