I don’t use that package but the text of the second error makes it sound like it could be caused by:
- Some sort of network error, like a timeout if the connection was supposed to be held open but wasn’t
- Network firewalls getting in the way
- Antivirus software deciding something is hinky
The first error could be a symptom of the second one; i.e. the plugin tries to do something and it fails because the connection has been closed, which causes it to notice the situation and report the second error in more detail.
Maybe tweaking the value of the
passive settings may make it act better.
Apart from that you may want to report an issue directly with the package author to see if they have more insight. At a minimum it would help user experience if there was a way to close and reopen the state of the connection manually without having to restart Sublime to clear the error.