I observed that some individuals become confused when encountering an error page, primarily due to the lack of specific error messages. While it is generally recommended for front-end (FE) developers not to provide technical details in error messages, our situation is somewhat unique because: a) We cannot directly debug logs for other companies, and b) The users themselves are experts.

To address these concerns, I add these improvements:

1. For HTTP errors: Include descriptions derived from the corresponding exceptions to provide more clarity regarding the nature of the error.

1. When encountering 'connection refused' errors, we currently do not receive specific descriptions about the error. In this case, it would be helpful to guide users towards performing a more in-depth debugging process. For instance, we can suggest that they provide us with additional information from a devtool browser to aid in troubleshooting the issue.