More descriptive error than "Unable to Connect"

[dborg291]

Two days ago I was able to start my bot and have it connect it was acting completely as expected. Last night when trying to start, I am unable to connect. Therefore I am wondering if it possible to produce a more descriptive error than, "Unable to Connect"

Actual behaviour: Unable to connect

Expected behaviour: Connect and continue on.

Error log: [09:03] error: Reconnecting in 2 seconds.. (node:6348) UnhandledPromiseRejectionWarning: Unable to connect. (node:6348) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:6348) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Server configuration

• Operating system: Windows 10
• Node version (if applicable): 10.15.3
• NPM version (if applicable): 6.4.1
• tmi.js version: 1.4.5

[dborg291]

I believe issue was caused by a server and fixed on its own. Closing issue.