Cannot connect to Galaxy

hello all.
I have a problem. I am trying to run stacks de novo without refrence genome for paired end reads. it run once, i tryied to download the results but one of the files kept saying corrupted. so I deleted the results and re-run again. and it was when i found issues. It runs the platform but i cannot see the results and everytime i try to refressh to see if the job is completed the following messagwe keeps poping up " Cannot connect to Galaxy. Galaxy is currently unreachable. Please try again in a few minutes. Please contact a Galaxy administrator if the problem persists."
i´ve deleted the entire history, uploaded again all data and the end result is the same.

any help would be appreciated.

thank you

Hello Silvia,

I changed your history visualization to the beta version, which is useful with history with a lot of datasets like your.
The history panel is slightly different, but I hope you will be able to orientate.
At any time, you can revert the visualization to the previous, clicking on the double arrow icon top right.
Make a try and let me know if it’s helpful

Cheers,
Gianmauro

2 Likes

thank you so much.

its seems to be working. at least i can visualize the data. i´ll check it, re run and see what happens. thank you once again. easy fix but not for me for sure. just starting to use galaxy and rad-seq data.

once again thank you for your time.

1 Like


and also says bad agateway (502). I still cannot run in normal view and using the Beta version, i cannot see the results as well , see picrure

what should i do? this is weird…

thank you for your time

Hello,

I have the same issue trying to reach the server.

I get this : Galaxy could not be reached

You are seeing this message because a request to Galaxy timed out or was refused. This may be a temporary issue which could be resolved by retrying the operation you were performing. If you receive this message repeatedly or for an extended amount of time, please contact an administrator.

could you help me with this ?

thank you

I get the same message.

How do we contact the administrator?

Hello @Silvia @David83200 @kavaho @gmauro

Unexpected but resolved now. :hammer_and_wrench: Thanks to all for letting us know!