Feature #30284

Updated by Eric Helms about 2 years ago

Handle the following:


* Apache can be down
* Connection refused or connection timeout
* Foreman can be down
* HTTP 502 or 503
* Foreman can throw an error
* Does not always return a proper error message
* Need to check/fix Foreman to return a proper JSON structured error message
* Typically a 500
* Authorization error
* Show a proper invalid credentials error
* Instruct users where to look for error messages
* Include in error message to look in production.log when appropriate