Hi @earthworm
If you really think that the connection between your computer and the Galaxy server is dropping out, the process will usually end in an error – in the Upload tool itself or as a “red” dataset in the history. This would be especially true for a compressed file. So, maybe something else is going on.
You could run this command on your data locally and one in Galaxy to compare → Secure Hash / Message Digest. The md5 option is usually a good choice. If you are not sure how to run that on your computer – try an internet search, since the exact command can differ by operating system.
Other items:
- It is important to not navigate away from the Upload view while loading data. Closing the pop-up window is Ok, but moving to some of the other views is not. So, try waiting first if it seems that is going on.
- Let Galaxy auto-detect the datatype for any fastq data. This avoids other types of potential conflicts … beyond just file sizes.
- Loading uncompressed data is sometimes needed. Some small fraction of local compression file types might be not understood, and this gets around that problem. You can always re-compress once in Galaxy.
Two other solutions when working at the UseGalaxy.eu server.
- Use the resume function in the Upload tool. This only shows up as an option when an interrupted connection is still available … and might not be your use case if the data does load successfully (results in a new “green” dataset in the history) but the size just seems off.
- The EU server hosts an FTP function. The URL of where you are working is important for a successful connection to the right server. Can be a choice for batches of data but usually not needed for one or a few files anymore since the resume function handles those fine. Upload many files (>10) via FTP
Give that a review, then maybe share more details if things are still going wrong. Screenshots would probably help to clarify more for this.