Actually I just fixed that by adding the "host" in each handler but I get the same error as before from the browser when I try to access the webpage: Bad Gateway The proxy server received an invalid response from an upstream server. My apache configuration settings are the following: RewriteEngine on #RewriteRule ^(.*) http://localhost:8080$1 [P] RewriteRule ^/galaxy$ /galaxy/ [R] RewriteRule ^/galaxy/static/style/(.*) /home/galaxy/galaxy/static/june_2007_sty$ RewriteRule ^/galaxy/static/scripts/(.*) /home/galaxy/galaxy/static/scripts/pac$ RewriteRule ^/galaxy/static/(.*) /home/galaxy/galaxy/static/$1 [L] RewriteRule ^/galaxy/favicon.ico /home/galaxy/galaxy/static/favicon.ico [L] RewriteRule ^/galaxy/robots.txt /home/galaxy/galaxy/static/robots.txt [L] LoadModule proxy_uwsgi_module /usr/lib64/httpd/modules/mod_proxy_uwsgi.so LoadModule uwsgi_module /usr/lib64/httpd/modules/mod_uwsgi.so <Location "/galaxy"> Sethandler uwsgi-handler uWSGISocket 0.0.0.0:4001 uWSGImaxVars 512 </Location> From: makis4ever@hotmail.com To: galaxy-dev@lists.galaxyproject.org Date: Wed, 14 Oct 2015 12:17:05 +0300 Subject: [galaxy-dev] Galaxy in cluster mode won't start from 0.0.0.0. Hello everyone, I am trying to set up a local Galaxy instance publicly available and configured via pbs/torque in order to fully exploit a multi-cpu server. So I changed my job_conf.xml and my galaxy.ini files (described in the end of the e-mail) according to the istructions on the Galaxy site but when I tried to run the run.sh script: GALAXY_RUN_ALL=1 sh run.sh --daemon all the handlers start from 127.0.0.1 instead of 0.0.0.0. Has anyone encountered that issue before. Am I missing something? Thank you, Makis The changes in the files: galaxy.ini [uwsgi] processes = 12 stats = 0.0.0.0:9191 # i had this at 127.0.0.1:9191 but with no difference socket = 0.0.0.0:4001 # I had this at 127.0.0.1:4001 but with no difference pythonpath = lib threads = 4 logto = /home/galaxy/uwsgi.log master = True [server:handler0] use = egg:Paste#http port = 8090 use_threadpool = True threadpool_workers = 10 [server:handler1] use = egg:Paste#http port = 8091 use_threadpool = True threadpool_workers = 10 [server:handler2] use = egg:Paste#http port = 8092 use_threadpool = True threadpool_workers = 10 [server:handler3] use = egg:Paste#http port = 8093 use_threadpool = True threadpool_workers = 10 [server:handler4] use = egg:Paste#http port = 8094 use_threadpool = True threadpool_workers = 10 [server:handler5] use = egg:Paste#http port = 8095 use_threadpool = True threadpool_workers = 10 # The port on which to listen. #port = 8090 # The address on which to listen. By default, only listen to localhost (Galaxy # will not be accessible over the network). Use '0.0.0.0' to listen on all # available network interfaces. host = 0.0.0.0 job_conf.xml <?xml version="1.0"?> <job_conf> <plugins workers="16"> <!-- "workers" is the number of threads for the runner's work queue. The default from <plugins> is used if not defined for a <plugin>. --> <plugin id="pbs" type="runner" load="galaxy.jobs.runners.pbs:PBSJobRunner" workers="16"/> </plugins> <handlers default="handlers"> <!-- Additional job handlers - the id should match the name of a [server:<id>] in galaxy.ini. --> <handler id="handler0" tags="handlers"/> <handler id="handler1" tags="handlers"/> <handler id="handler2" tags="handlers"/> <handler id="handler3" tags="handlers"/> <handler id="handler4" tags="handlers"/> <handler id="handler5" tags="handlers"/> </handlers> <destinations default="torque"> <!-- Destinations define details about remote resources and how jobs should be executed on those remote resources. --> <destination id="torque" runner="pbs"/> <destination id="other_cluster" runner="pbs"> <param id="destination">@other.cluster</param> </destination> <destination id="long_jobs" runner="pbs"> <param id="Resource_List">walltime=72:00:00, nodes=1:ppn=8</param> <param id="-p">128</param> </destination> </destinations> ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/