Data visualization tools failing on 19.01 proxied galaxy instance


Our galaxy instance is hosted on our intranet server and made accessible to everyone through an apache proxy from our www web server.
Our galaxy architecture is set up through 2 apache proxies (one on each server). That is :
apache_www_server/galaxy (version 2.4.12) => apache_intranet_server/galaxy (version 2.4.39) => (uwsgi) galaxy.

Our instance url is :

Set up was done according to

Here is our apache set up :
<Location “/galaxy/”>
Require all granted

<Directory “/home/galaxy/galaxy/static”>
Require all granted

ProxyPass /galaxy uwsgi://

RewriteEngine On
RewriteRule ^/galaxy/static/style/(.) /home/galaxy/galaxy/static/june_2007_style/blue/$1 [L]
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] RewriteRule ^/galaxy/ /galaxy [R,L]

<Directory “/home/galaxy/galaxy/config/plugins/(.+)/(.+)/static”>
AllowOverride None
Require all granted

RewriteRule ^/galaxy/plugins/(.+)/(.+)/static/(.*)$ /home/galaxy/galaxy/config/plugins/$1/$2/static/$3 [L]

Here is an extract of our galaxy.yml set up :
uwsgi :
mount: /galaxy=galaxy.webapps.galaxy.buildapp:uwsgi_app()

galaxy :
cookie_path: /galaxy

We face problems with some of the data visualization tools.

For instance, msa tool fails loading data because url built to access the data is wrong :
instead of

I have also tried with nginx instead of apache and encountered the same problem.

Furthermore as some visualization tools do work (phyloviz for instance), I believe that this problem is due to a msa plugin bug for accessing the dataset.

Is it possible to get any assistance from the dev team to solve this problem ?
Any help welcome.


1 Like