Not really sure what is happening here, does your galaxy.ini file have
the following sections:
use = egg:PasteDeploy#prefix
prefix = /galaxy
filter-with = proxy-prefix
cookie_path = /galaxy
If yes, it might be best to share nginx configuration and your galaxy
logs when this occurs so we can see what routes Galaxy thinks are
On Thu, Aug 27, 2015 at 4:50 PM, Bernau, Christoph
I have a problem with configuring my galaxy instance with a proxy server
when I try to serve at a subdirectory.
I followed the description at
The basic configuration works just fine.
When I use the procedure described in the section
“serving galaxy at a subdirectory”, the proxying principally also works.
However, when registered users try to log in to galaxy, galaxy will simply
directs them to the starting page (which I think is
what normally happens after logging in) without displaying an error message.
Nonetheless, users do not have access to the functionalities which only
logged in users
can use. E.g. each time they try to use the “workflows”-button they are told
to log in.
Could you please provide any help on this issue?
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:
To search Galaxy mailing lists use the unified search at: