Troubleshooting

Getting 400 Bad Request Error

Getting 400 bad request error message means the Prolaborate config file was not updated with correct port number in Prolaborate Config file.

To avoid this, proper Port and Protocol details in Config file needs to be provided using Prolaborate service management. If the correct information is entered the by the user, then the Prolaborate engine should work fine.

Parallelly, IIS needs to be stopped which is already running behind the application. This may interrupt the V5 port execution which results in getting 400 bad requests from browser.

Error: “404 Back to the Repository”

This error typically occurs after a server migration when the Domain URL in the OIDC Applications table does not match the new or expected URL. Update the Post Logout Redirect URL and Redirect URL in the OIDC Applications table and save the changes. Restart the Prolaborate service to apply the updates.