The ws-conn-string parameter refers to the original Bokeh server, which has been completely deprecated since last year and in unsupported in any way.
The new server will automatically use ws/wss based on the connection type (http or https) reported by a proxy. You can find more information about deploying a Bokeh Server with SSL/Nginx here:
The main point is to use the "--use-xheaders" option on the bokeh server, and then configure your proxy to forward the X-headers. Things will almost certainly work with other proxies (Apache, NodeJS) but I don't have the expertise to develop those sections. If you, a pull request to add additional example configurations to the documentation would certainly be appreciated.
On Aug 13, 2016, at 12:31 PM, Henry Harrison <[email protected]> wrote:
I'm running into an issue with bokeh server behind nginx proxy. getting "websocket creation failed to url: ws://<doman>/<app>/ws"
From google it seems there used to be an server option ws-conn-string that can be used to change ws to wss but that doesn't seem to be the case anymore. did that functionality move?
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/10ebd76c-e2ed-408f-9a5c-2de335002f4b%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.