Hi all, I'm (finally) attempting to install a tool from the main Tool Shed into a local Galaxy instance, using Firefox, and got the same red error that Adam reported (below): Repository installation is not possible due to an invalid Galaxy URL: None. You may need to enable cookies in your
Hi peter, Do you have cookies blocked in your Firefox browser? Does your cookie_path setting work for what you've configured in your apache prefix? It's impossible to tell what specifically could be causing this in your environment, but it's definitely related to cookies. Greg Von Kuster
On Tue, Aug 6, 2013 at 6:11 PM, Greg Von Kuster g...@bx.psu.edu wrote: Hi peter, Do you have cookies blocked in your Firefox browser? Does your cookie_path setting work for what you've configured in your apache prefix? Yes, logging into my Galaxy and using it works fine - I can close tabs
On Tue, Aug 6, 2013 at 6:22 PM, Greg Von Kuster g...@bx.psu.edu wrote: On Aug 6, 2013, at 1:14 PM, Peter Cock p.j.a.c...@googlemail.com wrote: My Firefox is setup to accept cookies until the expire, but not to accept third-party cookies. Do I need to worry about cross-site cookies for my
You just need something like the following in your universe_wsgi.ini. # Tool config files, defines what tools are available in Galaxy. # Tools can be locally developed or installed from Galaxy tool sheds. tool_config_file = tool_conf.xml,shed_tool_conf.xml On Aug 6, 2013, at 1:27 PM, Peter
Greg, Thanks for the tip on Safari. I have switched to another browser and working now! Thanks, -Adam -- Adam Brenner Computer Science, Undergraduate Student Donald Bren School of Information and Computer Sciences Research Computing Support Office of Information Technology
Adam, Normally, the Galaxy URL should be automatically determined and set in a cookie during the repository installation process. To help track down this issue, could you provide the revision of Galaxy you're running, and the end of the paster.log file when this error occurs? --Dave B.
In addition, it's helpful to know which browser you are using. Safari has fairly strict policies on 3rd-party cookies if you have them blocked. Chrome and firefox are less strict, so unblocking 3rd-party cookies if using Safari or simply switching to chrome or firefox will probably solve this