Repository installation is not possible due to an invalid Galaxy URL


I’m trying to install a tool from the Toolshed but I got this error:

Repository installation is not possible due to an invalid Galaxy URL: None. You may need to enable third-party cookies in your browser.

The cookies are OK (tested on Firefox and Chrome).

I’ve found this similar topic:

So I checked the admin_users parameter in galaxy.yml file. It was empty.
-> First of all it’s weird that I could connect as admin mode (with login) if this field is empty.
-> Then I added my admin login and restarted Galaxy, without success.

I tested with several tools (mirkwood from Test Tool Shed, bamtools from Main Tool Shed), always with the last revision.

I’m using Galaxy with docker, tested on bgruening/galaxy-stable:18.05 and bgruening/galaxy-stable:19.05.

Finally, I tested with Install new tools (Beta) mode from Tools management. This time it worked. It’s a bit weird that the only way to install a tool is the beta mode.
So I don’t really know if it’s worth bothering to try to solve this problem or if anyway the old, classical way to install tools is going to be replaced by the currently beta mode…

Thank you for reading me.

1 Like

Hello @i-guigon

Dependency resolution with conda is now the default and recommended method for tool installation. Start here: &&

The versions of Galaxy noted are over a year old – use the latest versions of Galaxy releases for the best functionality. You’ll find that the dependency resolution functions are no longer in beta and can be customized. Using default settings is generally best unless you have specific reasons to install differently. The links above cover the options.

If you need help with a Docker version of Galaxy, this Gitter chat is a direct way to communicate with the image maintainers:

The Galaxy Test ToolShed is a testing sandbox – meaning, tools are not in a stable/release form. Obtain tools from the Galaxy Main ToolShed instead.

If a tool is only available in the Test ToolShed, and not in the Main ToolShed, it may still be useable, but installation may not work “automatically” and require some advanced tuning. Explore the development repository for the tool (is usually linked to the tool’s ToolShed page, but not required, especially at the Test ToolShed), review open known issues, and open a new issue there describing problems as needed.

The tool wrapper authors are the best resource for troubleshooting installation issues (if using managed dependencies and the most current version of Galaxy itself). An exception can be tool wrappers authored by the IUC or Devteam – you can ask if there are known issues (if you can’t find one yet at the development repository) or for installation help (after reviewing the development docs linked above) at this Gitter chat:

Please be aware that some tools may no longer be actively maintained, and some may use older or custom dependency resolution methods. ToolSheds are community resources – anyone can publish a tool there. How to tell if a tool is maintained/functional or requires a specific installation method? 1) The tool wrapper’s publication date, how many times downloaded, and other notes on the tool’s ToolShed page and 2) commit/update dates at the linked development repository.

The Test and Main ToolSheds were just upgraded, so there were recently windows where tool installation was expected to not function correctly, no matter which ToolShed was the source. Example Q&A about that at this Gitter chat:

Current and historical status/notes about downtime are at the Galaxy status page. It includes all usegalaxy.* servers and core resources like ToolSheds.

Hope that helps!

I got same message when installing new tools via toolshed. I am using an old version of galaxy, too afraid to update as an important Qiime v1 workflow is manually configured there.