Question: Error in hosting on same network (0.0.0.0:8080)
0
gravatar for jchen015
2.9 years ago by
jchen01580
Singapore
jchen01580 wrote:

Dear all.

with reference to the photos (https://www.dropbox.com/sh/gi80qmyjcdwl1kb/AABVIkCbEq3s6T2pelA2oFRga?dl=0), the image - "server_hosting(0.0.0.0:8080).png" shows that the server is successfully hosted on network without looping.

I browsed through the forum and realized some other users are also facing this problem (https://biostar.usegalaxy.org/p/5044/). After which, from the answers suggested, i went ahead with iptables firewall configuration and in the second image - "IP_TABLES_FIREWALL.png" shows the firewall settings i believe.

I do not really understand the result from the second image but my problem here is...

I want to let other users in my network to access the Galaxy which is hosted on my laptop. And for them to access, they have to type 0.0.0.0:8080 ?

 

Regards,

Julius

ADD COMMENTlink modified 2.9 years ago by Dannon Baker3.6k • written 2.9 years ago by jchen01580
1
gravatar for Dannon Baker
2.9 years ago by
Dannon Baker3.6k
United States
Dannon Baker3.6k wrote:

By default galaxy will only accept connections from the machine it's running on (when host = 127.0.0.1).  Setting this to 0.0.0.0 will cause the Galaxy web server to listen on all available interfaces, which *includes* the loopback, 127.0.0.1, explaining the second screenshot.

Other users will not use 127.0.0.1:8080 to access your galaxy server from their machine on the network, they will use http://your_machine_ip:8080

Does this help explain things?

ADD COMMENTlink written 2.9 years ago by Dannon Baker3.6k

Hi Dannon.

following your guidance, i hosted Galaxy on my local server as stated below.

Starting server in PID 2444.
serving on 0.0.0.0:8080 view at http://127.0.0.1:8080

 

Knowing that my IP address is for e.g. (101.61.20.55), and i ask my follow peers to try accessing my galaxy server at "http://101.61.20.55:8080" but it failed.

Error Message: "Firefox can't establish a connection to the server at 101.61.20.50:8080."

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

 

May I know what are some of the problems causing this to fail?

Regards,

Julius

ADD REPLYlink written 2.8 years ago by jchen01580

You'll need to make sure that the server you're running this on doesn't have a firewall that would prevent access and that the IP address it receives is actually public.

ADD REPLYlink written 2.8 years ago by Dannon Baker3.6k

Dear Dannon

I had already allowed all connections to be accessible. (As shown below).

===================================

root@user-Aspire-4755:~# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:8080
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:80

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination   
      

===================================

And my Galaxy server has been set up and running which shows:

"Starting server in PID 5270.
serving on 0.0.0.0:8080 view at http://127.0.0.1:8080"

 

I found out that my IP address is 101.127.6.49 through the command below:

root@user-Aspire-4755:~# wget -qO- http://ipecho.net/plain ; echo
101.127.6.49
root@user-Aspire-4755:~#

 

Assuming all are correct, now i access my galaxy server via http://101.127.6.49:8080 , and the browser still returns error... the same error...

 

What could possibly happen?

 

Regards,

Julius

 

 

 

ADD REPLYlink written 2.8 years ago by jchen01580
1

The ip reflected by ipecho.net is the public ip that makes the request, not (necessarily) what someone would use to access your computer on a local network.

Try the command 'ifconfig' on the command line, and look for the 'inet' address listed for eth0 or en0 to get the correct ip address.

ADD REPLYlink written 2.8 years ago by Dannon Baker3.6k

i typed iconfig, but my current connection is wireless and not through lan cable.

Do I have to make it connected through an ethernet cable to get it hosted and broadcast the network?

Regards,

Julius

ADD REPLYlink written 2.8 years ago by jchen01580
1

No, you do not. I'd recommended it if this is going to be a sever many other people access, though. The output of ifconfig should still have had an internet address.

If you don't see it or otherwise have trouble with this, I'd really recommend finding someone in local IT to help you figure out the best way to provide a service on your local network.

ADD REPLYlink written 2.8 years ago by Dannon Baker3.6k

Hi Dannon

Thanks for the prompt reply. Appreciate it.

the only available inet addr i seen after executing ifconfig is:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host

wlan0     Link encap:Ethernet  HWaddr 10:0b:a9:43:b3:0c  
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::120b:a9ff:fe43:b30c/64 Scope:Link

 

i would believe none of them are my ip address?

 

Regards,

Julius

 

ADD REPLYlink written 2.8 years ago by jchen01580
1

You want wlan0: 192.168.0.101

This is your local network ip address that others can access your computer at. Like I mentioned, if you're going to be running this as an actual service for folks, I'd really recommend contacting local IT to figure out how to best do that.

ADD REPLYlink written 2.8 years ago by Dannon Baker3.6k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 116 users visited in the last hour