PTMsigDB This site can't be reached

[Anne-Christine Uldry]

Dear all,

I don't know when it started, but presently I find myself unable to reach the PTMsigDB database at https://proteomics.broadapps.org/ptmsigdb/

On firefox, I get the following error message:

---------------------------------------------

Secure Connection Failed

An error occurred during a connection to proteomics.broadapps.org. PR_END_OF_FILE_ERROR

Error code: PR_END_OF_FILE_ERROR

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
-------------------------------------------------

On chromium, this error message:

This site can’t be reached
proteomics.broadapps.org unexpectedly closed the connection.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_CLOSED

--------------------------------------------------

Has anyone had the same problem, and is there a fix?

Thanks and best wishes,

AChU

[Julie Sanchis]

Dear all, 

I have the same problem, did anyone find a solution?

Best,

Julie

[David Eby]

Hi all,

PTMsigDB is not directly connected with the GSEA-MSigDB project, so we can't speak for them on what kind of issues their portal might be having.  I would recommend trying to reach their team via their GitHub site, at https://github.com/broadinstitute/ssGSEA2.0 .

I should also note that the Broad Institute had a round of layoffs recently.  I have no idea if this team was involved, but it's possible that they or the supporting staff were affected.

David Eby
www.gsea-msigdb.org

--
You received this message because you are subscribed to the Google Groups "gsea-help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gsea-help+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gsea-help/da43b357-b5cb-49a5-9b02-8856297ad0ddn%40googlegroups.com.

[Anne-Christine Uldry]

Oh, thanks David for this insight, and sorry for the confusion. I have now posted this issue on the ssGSEA2.0 github page.