How to run streamlit in https mode?

Is there a new approach oder workaround available with st v1.0?. It seems still to host only unsecured http sessions.

1 Like

I am sure you are aware of this, but for anyone who works with data or use cases that are at all sensitive, this is, or at least should be, a crucial requirement, both because it is common sense and good practice, and because there is a large and vociferous privacy community that is just waiting to jump on companies that ignore privacy protection. One of the first things I did at my last PM job was to move us to https.

1 Like

Streamlit as a Python library intentionally stops before https, not because we can’t do it, but rather so that we focus on providing the best data app experience for users.

Our Streamlit Deployment Guide (wiki) highlights several community-based solutions for using nginx or Apache2 to set up https authentication, and Streamlit Cloud is https by default.

So there are definitely ways to run your Streamlit apps securely, irrespective of the version of Streamlit you are using.




The following is meant as friendly offer of a complementary perspective, not trying to bust your chops, or to argue with the near-term focus on providing best data app experience, and I totally commend Streamlit for providing good pointers to community documentation about how to deploy SSL.

I’ve been acquiring, processing, creating, and distributing global data sets since the 1990s (for NASA’s EOSDIS) and I have learned to think about data as coming with a whole lot of intangible attributes attached other than just raw numbers. Most data comes into existence from its very first moment with terms of use, privacy considerations, copyright and security issues attached (as well as inadequate documentation, and the need to update the data). I’m exaggerating, but just scribbling a few figures on a page of a lab notebook is enough to set those rights in motion. And irritatingly, terms of use, etc., are very often a real and immediate constraint that prevent people from doing interesting and magical things with data. All those issues come with people attached who care intensely about them, and for all those people, having https enabled has become just one of many ‘table stakes’ items that are expected from people who are using their data and especially making it visible via a “data app”. And roadblocks on deploying SSL are significant obstacles for those battling through them (I’ve done it dozens of time, but it’s always a headache). I am sure I speak for many when I wish those roadblocks would just go away. :wink:

I’m guessing that as Streamlit scales, the “soft” issues around data will become more important, and so will the outside-the-library deployment issues. So my $0.02 is “put it on the roadmap!”


Disagree. There are many more requirements, as you suggest, than just using https. There are data access, personnel, data sharing, auditing… the list is endless. HTTPS is only a single aspect of this, and may be more or less important depending on use case.

And all of these components of good data governance are difficult to do well, especially in a generic sense, without the context of the actual project.

There are many solutions to good HTTPS access, and signposting these and providing good integration is vital, but do not try to reinvent the wheel on this. A bad security implementation is a massive security risk. Focus on what you uniquely do well - streamlit explicitly NOT providing Https is much more preferable than an outdated or incomplete implementation.

Hosting on streamlit or behind a reverse proxy is trivial and allow separation of security from business logic.

My $0.02 - do NOT put it on the road map!

1 Like

It’s quite easy to run it on HTTPS with reverse proxy as madflier suggests. I have done that by configuring apache server. When the request comes to the IP, apache will receive it and forward it to the appropriate port in which streamlit is running. I then used certbot to issue the certificate and also reroute all the traffic to https. Finally, you adjust the config in streamlit to point to the correct ip address / domain name in which you are serving the app.

Since Streamlit uses Tornado you can just edit the Package to make it use HTTPS instead of HTTP by adding the following “ssl_options” in file “” in path “C:\Python310\Lib\site-packages\streamlit\server”. And everything works fine. HTTPS gets used instead of HTTP and WebSocketSecure (WSS) gets used instead of WebSocket (WS).


I tried it on my server but web page does not work once I added ssl_options. Do I need any actions on top of adding ssl_options?

This worked for me but I am on a Mac so the path was slightly different. You’ll want to generate an unencrypted key if your starting with a .PFX since it is password protected.

This is great.

For a networking newb like myself, I guess I have to generate those two files. How would I go about that?


1 Like

How did u get SSL certificate for the IP address? let me say if its 145.354.346.222:8051

This works perfectly!
Anyone wondering how to get the cert file and key file refer to this, you will need a domain name for this beforehand, certificate generation will not work on the IP address directly.

The server port in ‘settings.toml’ should be set to 443 like so. Headless just means that there will not be a popup of the app on launch.

port = 443
headless = true

The cert file is equivalent to the ‘fullchain.pem’ file and the key is equivalent to the ‘privkey.pem’ file.
Enter the paths in this path and you should be good to go.

To run the app in port 443 you may need to run as superuser.

1 Like

Oops, So no way we can get SSL for IP address to run my VPS hosted streamlit.
But thanks for the reply. Sure this conversation will prove helpful to someone.

How you create cert.cert and key.key for this?