Closed Moswag closed 4 years ago
Hi!
"NO.AUTHORIZATION." — this is what the ISO host or some part of the networking infrastructure says. I have discussed the same case with other user before, and it was a problem on the network layer, that he solved successfuly. Nothing to do with SocketQueue here.
You may use --dangerous key to get the full message.
Connected to upstream 10.132.171.209:22000!
2019-12-30 10:07:53 - info: Processing queue [pending 0 / total 1]
2019-12-30 10:07:53 - verbose: Queue keys dump: 0
2019-12-30 10:07:53 - info: Got data from ISO-host (17b)
2019-12-30 10:07:53 - verbose: [NO.AUTHO...]
2019-12-30 10:07:53 - info: Processing queue [pending 0 / total 1]
2019-12-30 10:07:53 - verbose: Queue keys dump: 0
2019-12-30 10:07:53 - info: Upstream
2019-12-30 10:07:53 - info: Upstream
2019-12-30 10:07:53 - info: Dropping all active clients
this is what i am getting