We resolved the issue. Turns out there was a setting on the F5 under "Advanced" that was missed during the configuration for the production environment. There is a separate profile required for websocket that was set to none on production but had a profile on QA. The network engineer duplicated the WS profile and applied it to Prod. Which then allowed us to subscribe to our streaming services and resolved the issue. The moral of the story: work closely with your network engineering folks and *document, document, document* once you've gotten the correct settings on the F5 for a lower environment so they can then replicate those to the production environment. I should also add, we discovered this by essentially bypassing the F5 and updating the WebSocketContextURL to the server name wss://servername.domain:6143. Once we reverted the WebSocketContextURL to wss://reverseproxyservername.domain it failed to let us Subscribe.