The debugger should be getting invoked if the Gateway is indeed being hit.
It sounds like the DNS is only an issue for outbound, so if this is a cluster you may want to check that the inbound connection targets a specific node. It's possible if you are using a cluster name another node is being hit.
You can also check the ssg log : /opt/SecureSpan/Gateway/node/default/var/logs/ssg_0_0.log
or through policy manager: VIEW -> VIEW LOGS
You should see some entries like this:
OUTBOUND
com.l7tech.external.assertions.websocket.server.WebSocketOutboundHandler: Attempting to create WebSocket connection to: ws://win10.com:8888
2019-03-08T07:54:04.010-0500 INFO 107686 com.l7tech.external.assertions.websocket.server.WebSocketOutboundHandler: Successfully created WebSocket connection to: ws://win10.com:8888
Additionally, you can add an audit to the inbound policy, say something like "** WEBSOCKET INBOUND ESTABLISHED **
You can then see the corresponding message in the SSG log and audits. This will confirm that the Gateway received the message and processed at least up to the point of the connection and inbound policies. The above will show the outbound connection established.
INBOUND
2019-03-08T07:55:16.877-0500 INFO 107688 com.l7tech.server.message: Processing request for service: inbound [/inbound]
2019-03-08T07:55:16.878-0500 WARNING 107688 com.l7tech.server.policy.assertion.ServerAuditDetailAssertion: -5: ** WEBSOCKET INBOUND ESTABLISHED **
Hope this helps.
Regards,
Joe