Websockets non-negotiable?

It looks like our company’s infra is not prepared for dealing with websockets. Is there some fallback mechanism that avoids using them? Either currently available, or in the works?


Hi Dániel,

I doubt there’s a way to use Streamlit without websockets.

Are you allowed to use Jupyter notebooks over your company’s network? If so, then there should be a way to allow websocket connections with Streamlit since Jupyter also relies on websockets.

Most of the time I’ve seen this break on proxies that don’t have Connection upgrade set up so that a HTTP/1.1 can upgrade to a WebSocket connection. Modern proxies will allow this and it’s a matter of configuration.


1 Like

Thanks for the heads-up!

Jupyter (or more exactly, Zeppelin) is allowed at my company’s network, but the infra team had to manually set it up outside our normal deployment framework. Analogously, I can deploy my streamlit-based app with some manual steps, but that’s not a good position to be in if I intend to deploy it regularly. In any case, I think we’ll accommodate to streamlit being websockets-only, because we really like streamlit. :slight_smile:


Hi @danielvarga, I’m wondering what exactly you (or your networking folks) had to do to get Jupyter (or Streamlit if you got it working) behind proxy? I am having trouble connecting to our database from within Jupyter and Streamlit and am unfortunately not so fit in networking, so i’m not sure where to actually point our networking people to with how to resolve this?