
I can connect a session to serial port 2 for windows (supposedly an interactive session).I have followed the guidelines religiously to get a serial port session (not my forte - noob.).Of course now we can do nothing on the server, because we cannot access it.Everything has been setup as far as I know on both the Google Console and the server.This was functioning fine until a week or so ago.RDP either return 0x104 or 0x204 (using the latest macOS BETA of MS RDP).We have our own Directory Service (Apache-DS) that does account validation for an internal system NOT FUNCTIONING.PIAB (a project management system using MySQL) functioning (ie, can get to it with http//address:port).

JIRA (using MySQL) functioning (ie, can get to it with http//address:port).


Based on logs from users experiencing these error codes on 10.8.0, the issue seems to be happening during WebSocket connection where the client did not fallback properly to https channel and instead thows the error. If the gateway doesn’t support WebSocket then the client will fall back to using plain https channel. We have triaged an issue and working on a fix! When connecting to an on-prem deployment gateway, the client by default will try to connect via WebSocket first.
