Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Mobile app fails to connect in Staging environment in OSCO



Mobile application users are encountering HTTP 500 "Internal server error" messages on their devices. This issue appears to impact Online as a Special Case of Offline (OSCO) mobile functionality.

Error Messages

"HTTP 500 Internal Server error"

Steps to Reproduce

This issue only occurs when the device is connected to WiFi / network:

Run an application on the mobile client with a breakout call to access the server and execute an activity there.

Root Cause

A defect in Pegasystems’ code or rules. 

The working server is configured to answer requests for both the following URLs.

Notice the additional PRServlet in the second URL.

On the malfunctioning system, any request to:
(without the PRServlet) is generating the 500 server errors (even in desktop browser).


Perform the following local-change: 

Configure the application server on the staging system, to answer both the requests (with and without PRServlet) as it is in the working system.


Published March 12, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us