-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference server problem? #33
Comments
Ping. Is the https://htsget.ga4gh.org/ reference server supported anymore? The IGV example has been failing since at least December https://igv.org/web/release/2.11.0/examples/htsget.html This fails from the web browser, due to (I think) a certificate problem https://htsget.ga4gh.org/variants/giab.NA12878?class=header&format=VCF https://htsget.ga4gh.org/variants/giab.NA12878?class=header&format=VCF |
This is still an issue, I'm removing htsget examples from IGV as there doesn't seem to be a working public htsget server. |
Has the reference server at https://htsget.ga4gh.org been abandoned? Still a 502 error. |
Same problem still occurs @jrobinso https://htsget.ga4gh.org/ takes 502. |
@sehaartuc I think this project has been abandoned. It would be nice if someone could confirm that and close this ticket, but that is my assumption. |
I am getting 502 errors now from the reference server at https://htsget.ga4gh.org/. This just started happening sometime on Dec 28, causing igv.js htsget unit tests to fail. Example in screenshot, but any request to https://htsget.ga4gh.org/ will return a "502 Bad Gateway" at the moment.
The text was updated successfully, but these errors were encountered: