-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI does not display when serving at port 3000. #4921
Comments
Hi @phihung! 😃 Thanks for sharing your question! Unfortunately we can't always dig deep and troubleshoot challenges like this on GitHub. We typically use GitHub for feature requests and bug reports. For troubleshooting help, you can visit our awesome community forums, where thousands of other Streamlit hackers help each other and talk about the amazing things they are creating! |
Hi @mayagbarnes, |
I also ran into this problem today, and I tracked down its cause and I think it's indeed a bug. When you set the server port to 3000, if you check the browser console you will find that it's still trying to access port 8501 for websocket connection which causes errors. The reason it's doing that is that port 8501 is hard-coded as the "development port" (link), and the condition for streamlit to tell that it's in development mode is, interestingly, to check whether the server port is 3000 (link) which I find unreasonable. I think development mode shouldn't be set based on which port the server runs on but through some configuration / environment variable. Can we re-open this issue and fix this? |
@mayagbarnes Please re-open this ticket. Streamlit won't function on port 3000 which is a real problem! |
Summary
Streamlit UI does not display when serving at port 3000
--server.port 3000
-p 3000:8501
Steps to reproduce
Docker file
Run locally
Run with Docker
In K8S
Everything works fine when changing 3000 to any other port
The text was updated successfully, but these errors were encountered: