This action stops hosting if the Lacewing Relay protocol part of the server is hosting at all.

If the server is not hosting, no error will be made; the action will simply do nothing.


Note that no Channel > On channel close, Connection > On disconnect or other leaving events will be triggered.

You should use a channel loop or client loop before calling the Stop hosting action if you want to do something with them.

Note the Client > Get client protocol implementation expression should always contain the text "HTML5" or "UWP" for WebSocket clients, as all WebSocket clients have implementation sent shortly as their next message after connection is approved.


Blue Clients connected to the WebSocket server(s) will not be disconnected by this action, but may be kicked from channels due to the channel's auto-close setting.

If this happens, the leave request will still not run, because it's not a request from the client.