While good at python, network stuff is new for me.
In my corporate environment, i can only share https not http addresses with different users.
So I installed nginx, got a certficate and got it running. I am for now using default http://localhost:8501 for my streamlit app and it runs fine.
My goal is for nginx to reroute everything to httpS://localhost:8501.
Is there anyone out there who has a complete nginx conf file that will accomplish this?
Thanks for taking the time to set this up, sadly I cannot get it to work.
When I try the conf file in your guide, it does not work. I get an error on parameter ‘upstream’. Is that the entire .conf file? All i want is to go from http:// localhost:8501 to https://localhost:8501.
(Also, not a big deal, but your streamlit application example lacks some imports and a quotation mark)
I was using Nginx as my reverse proxy for the longest and I recently switched over to using Traefik. I have a post about it. It has made life so much easier.
Hello everyone! I am trying to deploy a streamlit application on Linux (Ubuntu 18.04.4) machine. I am not deploying it via docker, I am just editing Nginx configuration file at/etc/nginx/nginx.conf. Here is a full file:
This result are next errors in the terminal (I also attach a screenshot):
Unchecked runtime.lastError: The message port closed before a response was received.
ar-hand-api-stg.centralus.cloudapp.azure.com/:1 GET https://ar-hand-api-stg.centralus.cloudapp.azure.com/dashboard/vendor/bokeh/bokeh-2.4.1.min.js net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK)
bokeh-widgets-2.4.1.min.js:38 Uncaught TypeError: bokeh.register_plugin is not a function
at bokeh-widgets-2.4.1.min.js:38:20
at bokeh-widgets-2.4.1.min.js:43:1
at bokeh-widgets-2.4.1.min.js:32:3
at bokeh-widgets-2.4.1.min.js:33:3
ar-hand-api-stg.centralus.cloudapp.azure.com/:1 GET https://ar-hand-api-stg.centralus.cloudapp.azure.com/dashboard/static/js/5.df97478a.chunk.js net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK)
Can anyone please help me here? I’ve already tried a dozen of different Nginx and Streamlit configurations, nothing really works. I will really appreciate any help here!
Hello is this post related to deploying a streamlit app using https protocol?
I need some help in this regard. I have created a streamlit app on AWS EC2 instance. However the IP address appears as http but I need the address to be in the https format. Could u please share your insight with me ion how to do it?
Thank you.
Hello,
with this configuration I have been working since the first day without problems. But today I have seen that if I update my project no longer works because it gives 404. I have seen that they have changed the endpoint names. I tried to change /stream to /_stcore/stream but it still doesn’t work. Do you know what more changes I should do in my Nginx config?
@evtrompa is it possible you updated streamlit? I just spent all day trying to figure out why my nginx configuration was suddenly causing an endless Please wait… error. It turns out it was because the endpoint /stream was changed to /_stcore/stream in new-ish versions of streamlit, which I found here: Any changes regarding websocket for Streamlit v1.14 vs. 1.18?. I adjusted my configuration and now things seem to be working fine. Sharing in case it helps with your issue and because the documentation about this change still seems sparse.
After struggling with this for a few days, these are the settings I finally got to work when connecting your app deployed on an AWS EC2 instance with NGINX.
Hello @Marc , @nthmost , @yahayakenny , @Mac_Jones, @evtrompa
I am trying the same thing I want to use Nginx to route to different web applications which are on different ports.
Therefore i have made my configuration like this :
It didn’t work for me,
but instead of using /app as the route i just used “/” as the location then the application was running on that endpoint. not sure why it was not working when it was /app as the endpoint. I might be missing a few tweaks in the code can any of you please help with this, that would be great.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.