login problems when using a proxy and serving at a subdirectory
Dear all, 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 https://wiki.galaxyproject.org/Admin/Config/nginxProxy 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? Cheers, Christoph
Not really sure what is happening here, does your galaxy.ini file have the following sections: [filter:proxy-prefix] use = egg:PasteDeploy#prefix prefix = /galaxy [app:main] 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 being accessed. -John On Thu, Aug 27, 2015 at 4:50 PM, Bernau, Christoph <Christoph.Bernau@lrz.de> wrote:
Dear all,
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 https://wiki.galaxyproject.org/Admin/Config/nginxProxy
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?
Cheers,
Christoph
___________________________________________________________ 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/
When I've seen similar behavior in the past, it's always that cookie_path is incorrect. On Thu, Aug 27, 2015 at 1:46 PM, John Chilton <jmchilton@gmail.com> wrote:
Not really sure what is happening here, does your galaxy.ini file have the following sections:
[filter:proxy-prefix] use = egg:PasteDeploy#prefix prefix = /galaxy
[app:main]
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 being accessed.
-John
On Thu, Aug 27, 2015 at 4:50 PM, Bernau, Christoph <Christoph.Bernau@lrz.de> wrote:
Dear all,
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 https://wiki.galaxyproject.org/Admin/Config/nginxProxy
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?
Cheers,
Christoph
___________________________________________________________ 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/
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/
Hello John and Dannon, thanks a lot for your help. I had also suspected the cookie_path but I had actually already set it just the way you proposed. That's also what the description on the web says about the cookie path. I also use exactlly the same subdirectory as in the description. Nonetheless, I get this strange login behaviour. I have attached now my nginx.conf, galaxy.ini and the galaxy log. The log includes one of these failed logins in the last lines. However, I cannot find any error or debug messages there. Best, Christoph Von: Dannon Baker [mailto:dannon.baker@gmail.com] Gesendet: Donnerstag, 27. August 2015 19:50 An: John Chilton <jmchilton@gmail.com> Cc: Bernau, Christoph <Christoph.Bernau@lrz.de>; galaxy-dev@lists.galaxyproject.org Betreff: Re: [galaxy-dev] login problems when using a proxy and serving at a subdirectory When I've seen similar behavior in the past, it's always that cookie_path is incorrect. On Thu, Aug 27, 2015 at 1:46 PM, John Chilton <jmchilton@gmail.com<mailto:jmchilton@gmail.com>> wrote: Not really sure what is happening here, does your galaxy.ini file have the following sections: [filter:proxy-prefix] use = egg:PasteDeploy#prefix prefix = /galaxy [app:main] 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 being accessed. -John On Thu, Aug 27, 2015 at 4:50 PM, Bernau, Christoph <Christoph.Bernau@lrz.de<mailto:Christoph.Bernau@lrz.de>> wrote:
Dear all,
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 https://wiki.galaxyproject.org/Admin/Config/nginxProxy
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?
Cheers,
Christoph
___________________________________________________________ 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/
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/
participants (3)
-
Bernau, Christoph -
Dannon Baker -
John Chilton