Thank you for getting back to me.
I had searched for how to do this with Tornado, but came up blank (it does have IPv6 support though). My hunch is that changes would be required in Bokeh to expose IPv6 support given the error I’m getting.
For now, I’m going to try to set up a reverse proxy. Thank you so much for that suggestion!
If anyone else has any ideas or figures out a solution, please let me know.
On Thursday, May 17, 2018 at 10:23:23 AM UTC-4, Bryan Van de ven wrote:
I don’t honestly know. This really seems more like a Tornado question, since ultimately Bokeh server is built entirely on Tornado. You might have better luck asking in a Tornado forum. It’s possible changes in Bokeh would be needed to expose IPv6 functionality (or not, I really don’t know) but the Tornado community/devs would probably know best.
In any case, even if the answer is “no” it’s probably always possible to accomplish by running behind a reverse proxy like nginx that exposes an IPv6 endpoint.
On May 16, 2018, at 20:49, [email protected] wrote:
Is it possible to start a Bokeh app and allow access through and IPv6 address?
I am currently starting my Bokeh app using the following command for local access on my network:
python3 -m bokeh serve beer_tilt_web_app.py --allow-websocket-origin 192.168.1.20:5006
I would like to enable direct access via my public IPv6 address.
Thanks for any help!
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/da4087e2-55c1-4fb3-baf5-7fed7b0df14c%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.