question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Streamlit Localhost Works, but Network Does Not Connect

See original GitHub issue

Summary

When I run streamlit hello it works very well in my local browser. When I try to connect from another computer on the network, using the provided network url or using the local ip address of the computer running the app, streamlit shows:

This site can’t be reached10.64.1.47 took too long to respond. Search Google for 8501 ERR_CONNECTION_TIMED_OUT.

This is nearly identical to Issue 422, but I do not even get to the please wait screen.

Steps to reproduce

  1. streamlit run xxxxx.py
  2. local URL: http://localhost:8501 - works!
  3. network URL: http://10.64.1.47:8501- works on local computer, fails on other compturs on network

Expected behavior:

I would expect taht network url would work on computers on the same network

Actual behavior:

test

Is this a regression?

No

Debug info

  • Streamlit version: 0.51.0
  • Python version: (get it with $ python --version)
  • Using Conda Environment
  • OS version: Windows 10
  • Browser version: Google Chrome
  • Port 8051 Open
  • Config.toml set to disable CORS

Additional information

Firewall status:

Profile = Domain Operational mode = Enable Exception mode = Enable Multicast/broadcast response mode = Disable Notification mode = Disable Group policy version = Windows Defender Firewall Remote admin mode = Enable

Ports currently open on all network interfaces: Port Protocol Version Program

8051 TCP Any (null)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
monchiercommented, Dec 18, 2019

This setup seems correct to me. I wonder the firewall blocks Websockets. Is there any way to double-check that?

3reactions
kurt-rheecommented, Dec 19, 2019

Hey I made a typo and allowed port 8051 instead of 8501 (smack myself in the forehead) I am closing this issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Network URL not working on other computers - Using Streamlit
When I try to access the web app from another computer using the provided network URL, Streamlit shows: Safari can't open the page...
Read more >
Localhost Refused to Connect Error: 5 Confirmed Ways to Fix It
Localhost refused to connect error can be caused by an incorrectly configured port, insufficient permissions, or an inoperative web server.
Read more >
run streamlit app using Network URL not working
although you are using same network for all the system, you have to connect (SSH) to the server where you are running this...
Read more >
Introduction to Streamlit and Streamlit Components - Auth0
The Streamlit client application (runs on localhost, port 4010). The component design is like Streamlit-Player. [1] Streamlit component host ...
Read more >
Deploy a Public Streamlit Web App for Free — Here's How
We should understand that Streamlit supports the connection to many different kinds of database, but online database hosts are not typically ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found