Hi Evan, sorry to hear you're having these issues! Did you just upgrade this environment, or has it experience a power failure, anything like that recently? This error means our web interface is having trouble communicating with the service we run as well, and usually means something is holding up startup. 

Sometimes this may also appear with IIS configuration issues due to communication being blocked. Have you recently made any changes to the IIS bindings or application pool settings? Added a new firewall recently? One good way to check that is to log on to the server directly via remote desktop and try connecting to the web interface from there using the http://localhost:9998 binding. You may need to confirm you HAVE that binding in place before testing it though since its not always present in all environments depending on deployment. 

I hope that helps!