Closed chen01 closed 8 years ago
Am I interpreting this correctly? when it is trying to download pipeline history, the default port it is using 8153 here?
changing that port has fixed the connection issue but brought about another problem. I'm going to close this issue for now until I figure out what is going on now.
I continue to hit this error
java.net.ConnectException: Connection refused
with the plugin, and I'm not sure what I'm missing here, would you happen to know what is going on? The log shows that the websocket server has started on the expected port. This is the error in the log when go events occur: