Hey, We are trying to resolve the issue so that others do not have to change the Apache settings.
Is it possible to test this potential fix here: https://github.com/galaxyproject/galaxy/pull/4225 and comment on the issue? Thanks in advance, Sam On Thu, Jun 15, 2017 at 5:13 PM, Nicola Soranzo <nsora...@tiscali.it> wrote: > According to the same documentation, you need it only if using the > mod_proxy Apache module with HTTP transport, but I'm using nginx, not > Apache, so I'm not the best person to ask. > > Cheers, > Nicola > > > On 15/06/17 15:55, Fernandez Edgar wrote: > > Thanks Nicola for the comfirmation. > > > > Would you mind explaining a little more: > > > > ProxyPass / http://127.0.0.1:8080/ > > Should I add this too? > > > > *Edgar Fernandez* > > System Administrator (Linux) > > Technologies de l'Information > > *Université de Montréal* > > > > PAVILLON ROGER-GAUDRY, bureau X-210 > > ( Bur. : *1-514-343-6111 <(514)%20343-6111> poste 16568* > > > > *From:* Nicola Soranzo [mailto:nicola.sora...@gmail.com > <nicola.sora...@gmail.com>] *On Behalf Of *Nicola Soranzo > *Sent:* June 15, 2017 10:44 AM > *To:* SAPET, Frederic <frederic.sa...@biogemma.com> > <frederic.sa...@biogemma.com>; Fernandez Edgar > <edgar.fernan...@umontreal.ca> <edgar.fernan...@umontreal.ca>; > galaxy-...@bx.psu.edu > *Subject:* Re: [galaxy-dev] new installation galaxy-17.05 - Uncaught > error. > > > > Hi Edgar, Frederic, > if you are using Apache as proxy for your Galaxy server, then you should > probably add > > AllowEncodedSlashes NoDecode > > > to your Apache config, see https://galaxyproject.org/ > admin/config/apache-proxy/#allow-encoded-slashes-in-urls > > Cheers, > Nicola > > On 15/06/17 15:35, SAPET, Frederic wrote: > > Hi > > > > Same for me. > > But It looks like to be related with tools installed via the toolshed (Ie > : bedtools, emboss, blast+ suite…). > > My own tools seem to be ok. > > > > Just like you Edgar, nothing in the log… > > > > Fred > > > > *De :* galaxy-dev [mailto:galaxy-dev-boun...@lists.galaxyproject.org > <galaxy-dev-boun...@lists.galaxyproject.org>] *De la part de* Fernandez > Edgar > *Envoyé :* mercredi 14 juin 2017 17:11 > *À :* galaxy-...@bx.psu.edu > *Objet :* [galaxy-dev] new installation galaxy-17.05 - Uncaught error. > > > > Hey Guys, > > > > Hope everyone is doing ok. > > > > I have a small issue with a brand new installation of galaxy-1705. > > It starts properly and I installed some tools. > > But when I try to test any tools I get and “Uncaught error” (see picture). > > > > I can’t find anywhere in the logs what is happening. > > > > Any ideas? > > > > Regards, > > > > *Edgar Fernandez* > > System Administrator (Linux) > > Technologies de l'Information > > *Université de Montréal* > > > > PAVILLON ROGER-GAUDRY, bureau X-210 > > ( Bur. : *1-514-343-6111 <(514)%20343-6111> poste 16568* > > > > > > > ___________________________________________________________ > > 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/ > > > > > > ___________________________________________________________ > 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/ >
___________________________________________________________ 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/
