# Proxing Galaxy 19.01 with Apache **URL:** \ **Category:** Uncategorized\ **Tags:** devops-administration, proxy\ **Created:** [April 10, 2019, 1:00pm UTC](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055 "2019-04-10T13:00:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bertrand](https://avatars.discourse-cdn.com/v4/letter/b/a88e4f/32.png) [@bertrand](https://help.galaxyproject.org/u/bertrand)\ **Post date:** [April 10, 2019, 1:00pm UTC](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055/1 "2019-04-10T13:00:29Z")
Hi, I am trying to set up Galaxy proxying (on our 19.01 instance) with Apache. According to [Proxying Galaxy with Apache — Galaxy Project 26.1.dev0 documentation](https://docs.galaxyproject.org/en/latest/admin/apache.html), I set up configuration as is : - in httpd.conf : ProxyPass /galaxydev unix:///tmp/galaxy\_dev.sock|uwsgi:// RewriteEngine On RewriteRule ^/galaxydev/$ /galaxydev [R,L] RewriteRule ^/galaxydev/static/style/(._) /home/galaxydev/galaxy/static/june\_2007\_style/blue/$1 [L] RewriteRule ^/galaxydev/static/(._) /home/galaxydev/galaxy/static/$1 [L] RewriteRule ^/galaxydev/favicon.ico /home/galaxydev/galaxy/static/favicon.ico [L] RewriteRule ^/galaxydev/robots.txt /home/galaxydev/galaxy/static/robots.txt [L] - in galaxy.yml : uwsgi : socket: /tmp/galaxy\_dev.sock ###syntax unix:///tmp/galaxy\_dev.sock is not recognized ??? mount: /galaxydev=galaxy.webapps.galaxy.buildapp:uwsgi\_app() manage-script-name: true galaxy : cookie\_path: /galaxydev Accessing “galaxy\_host”/galaxydev with a browser fails. Apache error\_log returns this error : [Tue Apr 09 11:35:57.850743 2019] [:error] [pid 19307:tid 47544504309504] [client 195.221.174.148:63192] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 11:36:06.537558 2019] [:error] [pid 19211:tid 47544525321984] [client 195.221.174.148:63195] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 12:44:13.854039 2019] [:error] [pid 19307:tid 47544514815744] [client 195.221.174.148:63669] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 12:44:14.718221 2019] [:error] [pid 19307:tid 47544519018240] [client 195.221.174.148:63670] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 12:44:14.953882 2019] [:error] [pid 19307:tid 47544523220736] [client 195.221.174.148:63671] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 12:46:12.715991 2019] [:error] [pid 19307:tid 47544529524480] [client 195.221.174.148:63704] AH10097: error parsing URL //: Invalid host/port [Tue Apr 09 16:52:12.155767 2019] [:error] [pid 19307:tid 47544542131968] [client 195.221.174.167:59696] AH10097: error parsing URL //: Invalid host/port I am stuck with the “URL //: Invalid host/port” error message. Would you have any hint ? Regards. ---
**Author:** ![bertrand](https://avatars.discourse-cdn.com/v4/letter/b/a88e4f/32.png) [@bertrand](https://help.galaxyproject.org/u/bertrand)\ **Post date:** [April 12, 2019, 4:09pm UTC](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055/2 "2019-04-12T16:09:55Z")
This seems to be related to an apache mod\_proxy\_uwsgi bug. For those stuck in same situation, I used this workaround : 1. configure uwsgi proxying on a TCP socket (ie uWSGI on a TCP socket) 2. check apache2/mod\_proxy\_uwsgi.c and apply following fix if needed : [https://github.com/unbit/uwsgi/commit/6ce856c9fdb98833f9142f84c92b75f546b32dc2#diff-85cd090aa23e09feb1f28c92ae5aded6](https://github.com/unbit/uwsgi/commit/6ce856c9fdb98833f9142f84c92b75f546b32dc2#diff-85cd090aa23e09feb1f28c92ae5aded6) ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [May 25, 2019, 12:00am UTC](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055/3 "2019-05-25T00:00:19Z")
Hi @bertrand!! Thanks for posting the solution. > [@bertrand](#): > > This seems to be related to an apache mod\_proxy\_uwsgi bug. For reference, this is the bug referenced above: [mod\_proxy\_uwsgi port parsing · Issue #1491 · unbit/uwsgi · GitHub](https://github.com/unbit/uwsgi/issues/1491) ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [May 25, 2019, 12:04am UTC](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055/4 "2019-05-25T00:04:22Z")
Linked follow-up posts: > [@Proxing Galaxy 19.01 with Apache](https://help.galaxyproject.org/t/proxing-galaxy-19-01-with-apache/1055): > > Hi, I am trying to set up Galaxy proxying (on our 19.01 instance) with Apache. According to [https://docs.galaxyproject.org/en/latest/admin/apache.html](https://docs.galaxyproject.org/en/latest/admin/apache.html), I set up configuration as is : in httpd.conf : ProxyPass /galaxydev unix:///tmp/galaxy\_dev.sock|uwsgi:// RewriteEngine On RewriteRule ^/galaxydev/$ /galaxydev [R,L] RewriteRule ^/galaxydev/static/style/(.) /home/galaxydev/galaxy/static/june\_2007\_style/blue/$1 [L] RewriteRule ^/galaxydev/static/(.) /home/galaxydev/galaxy/static/$1 [L] Re… > [@Galaxy 19.01 drmaa problem switching from galaxy.ini to galaxy.yml](https://help.galaxyproject.org/t/galaxy-19-01-drmaa-problem-switching-from-galaxy-ini-to-galaxy-yml/994): > > Hi, I upgraded our Galaxy instance from 16.xy to 19.01. I succeeded to configure it with our deprecated galaxy.ini file. But I face problems to migrate configuration to galaxy.yml file and set it up to use our SGE 8.1.8 cluster : with galaxy.ini, galaxy jobs are correctly shifted and run by SGE but with galaxy.yml, galaxy jobs keep waiting to be shifted but are not received by SGE. I believe I must have misconfigured something but can’t find what. Would you have any hint ? Here are extra…