thanks @simonbray
My guess is that the servers (or internet connections in general!) are simply very busy with so many more people working and studying online, often now from home, but I’ll follow up with some testing and open a ticket if it seems to be a problem rooted in the latest Galaxy release itself (20.01). Will link that back for tracking if a problem is uncovered.
And for end-users, a few workarounds:
- Place your history archive at a publically accessible location and load by URL.
- Upload individual datasets. History archives can be uncompressed. Your data will be inside. Use FTP to Upload data in batch: Loading Data
- If the goal is only to review prior work, a local Galaxy server can be easily set up. Example step-by-step for a basic local Galaxy install with an admin account created
- If the goal is to continue work, and public servers seem to be too busy for your needs, the Galaxy Cloudman server option was recently updated. AWS offers grants for computational and storage needs for research and study purposes (Galaxy itself is always free). https://galaxyproject.org/use/
Thanks!