Galaxy refusing traffic from other machines?
![](https://secure.gravatar.com/avatar/47a0b35b045ad0afd998c0136021122d.jpg?s=120&d=mm&r=g)
Hello there, I downloaded Galaxy (Dist) from http://bitbucket.org/galaxy/galaxy-dist/ ran a basic setup and then "run.sh". Joy, Galaxy works fine. But when trying to access Galaxy from another machine, the connection is refused. I've checked that it's not a funny misconfiguration of our network which would block traffic between the machines, so I deduce that it's Galaxy which rejects every traffic not coming from localhost. I've searched a bit in the config files where to change that but did not find a place. Where do I tell Galaxy it should accept traffic from a given host (or IP range). Regards, Bastien -- DSM Nutritional Products AG R&D Human Nutrition & Health Bioinformatics - Bldg. 203 / 115 P.O. Box 2676 CH-4002 Basel / Switzerland Tel. +41 61 815 8264 DISCLAIMER : This e-mail is for the intended recipient only If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.
![](https://secure.gravatar.com/avatar/d6d3dd5a3198fea62331a4ecfddb4d53.jpg?s=120&d=mm&r=g)
Chevreux, Bastien wrote:
Hello there,
I downloaded Galaxy (Dist) from http://bitbucket.org/galaxy/galaxy-dist/ ran a basic setup and then "run.sh". Joy, Galaxy works fine.
But when trying to access Galaxy from another machine, the connection is refused. I've checked that it's not a funny misconfiguration of our network which would block traffic between the machines, so I deduce that it's Galaxy which rejects every traffic not coming from localhost.
I've searched a bit in the config files where to change that but did not find a place.
Where do I tell Galaxy it should accept traffic from a given host (or IP range).
Hi Bastien, At the top of universe_wsgi.ini, change: host = 127.0.0.1 to: host = 0.0.0.0 This will instruct Galaxy to listen to all available interfaces. --nate
Regards, Bastien
-- DSM Nutritional Products AG R&D Human Nutrition & Health Bioinformatics - Bldg. 203 / 115 P.O. Box 2676 CH-4002 Basel / Switzerland Tel. +41 61 815 8264
DISCLAIMER : This e-mail is for the intended recipient only If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.
_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
![](https://secure.gravatar.com/avatar/47a0b35b045ad0afd998c0136021122d.jpg?s=120&d=mm&r=g)
At the top of universe_wsgi.ini, change: host = 127.0.0.1 to: host = 0.0.0.0 This will instruct Galaxy to listen to all available interfaces.
Hi Nate, thanks, that did the trick. Now assuming that I want to restrict the access to a certain range of machines (or IPs), would that be possible too via wsg_ini or do I need to do this via an Apache proxy? I tried "host= 127.0.0.1, 192.168.0.2" but this was unsuccessful. Regards, Bastien -- DSM Nutritional Products AG R&D Human Nutrition & Health Bioinformatics - Bldg. 203 / 115 P.O. Box 2676 CH-4002 Basel / Switzerland Tel. +41 61 815 8264 DISCLAIMER : This e-mail is for the intended recipient only If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.
![](https://secure.gravatar.com/avatar/d6d3dd5a3198fea62331a4ecfddb4d53.jpg?s=120&d=mm&r=g)
Chevreux, Bastien wrote:
Hi Nate,
thanks, that did the trick. Now assuming that I want to restrict the access to a certain range of machines (or IPs), would that be possible too via wsg_ini or do I need to do this via an Apache proxy?
I tried "host= 127.0.0.1, 192.168.0.2" but this was unsuccessful.
Hi Bastien, Do you mean restricting to certain interfaces, or only to allow certain clients to connect? Restricting clients would best be handled in Apache. --nate
Regards, Bastien
-- DSM Nutritional Products AG R&D Human Nutrition & Health Bioinformatics - Bldg. 203 / 115 P.O. Box 2676 CH-4002 Basel / Switzerland Tel. +41 61 815 8264
DISCLAIMER : This e-mail is for the intended recipient only If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.
![](https://secure.gravatar.com/avatar/47a0b35b045ad0afd998c0136021122d.jpg?s=120&d=mm&r=g)
From: Nate Coraor [mailto:nate@bx.psu.edu] Do you mean restricting to certain interfaces, or only to allow certain clients to connect? Restricting clients would best be handled in Apache.
Restricting clients was what I meant and I already had the impression Apache would be the way to go. So, next stop: Apache. Thanks a lot for your answers. Best regards, Bastien -- DSM Nutritional Products AG R&D Human Nutrition & Health Bioinformatics - Bldg. 203 / 115 P.O. Box 2676 CH-4002 Basel / Switzerland Tel. +41 61 815 8264 DISCLAIMER : This e-mail is for the intended recipient only If you have received it by mistake please let us know by reply and then delete it from your system; access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail) immediately.
participants (2)
-
Chevreux, Bastien
-
Nate Coraor