The following guide is for technical teams that manage their Blue Relay hosted environment.
When clients are utilizing Blue Relay configurations, they may sometimes end up in a situation where an external API or action results in an unhandled error.
To redirect all unhandled errors and invalid URLs to a more user-friendly error page in Blue Relay, make the following update. This can be done right before deploying a new build, to avoid having to perform multiple Blue Relay instance application restarts.
- Open httpd-bluerelay.conf in your apache conf folder (this may be located under under /usr/local/BlueRelay/apache/conf or C:/Program Files/BlueRelay/apache/conf)
- Open the file httpd-bluerelay.conf
- Delete the all ErrorDocument lines
- Copy and paste the following ErrorDocument lines under the line about virtualhost (contains your server URL),
ErrorDocument 400 http://yourapplication.bluerelay.com/#/error
ErrorDocument 404 http://yourapplication.bluerelay.com/#/error
ErrorDocument 500 http://yourapplication.bluerelay.com/#/error
ErrorDocument 501 http://yourapplication.bluerelay.com/#/error
ErrorDocument 502 http://yourapplication.bluerelay.com/#/error - Restart the apache service (or execute your Blue Relay upgrade deployment)