The most common reason is that your Proxy or Firewall is blocking the SOPHiA GENETICS servers. This can be easily fixed by your IT department by updating your firewall rules to allow access to all our servers.
It seems like your network system (proxy or firewall) blocks access to our servers.
Firewall rules
In case you are using a firewall, your IT team must update the firewall rules to open access to our servers.
All in secure mode (https) and port 443:
allow connections for all sophia sub domains : *.sophiagenetics.com.
ddm-fra.sophiagenetics.com
ddm-aus.sophiagenetics.com
ddm-br.sophiagenetics.com
ddm-us.sophiagenetics.com
ddm-ch.sophiagenetics.com
ddm-cha.sophiagenetics.com
dropgen.sophiagenetics.com
apis-cha.sophiagenetics.com
iam.sophiagenetics.com
uploaderstoragecha.blob.core.windows.net
lma.sophiagenetics.com/sgml_sga_1/ddm
www.ncbi.nlm.nih.gov/SNP
www.ncbi.nlm.nih.gov/clinvar
www.broadinstitute.org
exac.broadinstitute.org
cancer.sanger.ac.uk/cosmic
www.internationalgenome.org
evs.gs.washington.edu/EVS
127.0.0.1:21000
127.0.0.1:60151
ddm-aus.sophiagenetics.com
Proxy configuration
In case you are using a proxy, your IT department must do the following:
SOPHiA DDM™ will try to detect automatically your proxy configuration based on the computer’s network settings.
Unfortunately, some proxies cannot be properly identified, and you might encounter problems connecting. If this happens, you can define the proxy configuration and force SOPHiA DDM™ to use it.
If you need to go through the proxy, you can create a file in c:\Users\”pc_username”\.dg-cache\proxyCfg.txt with the following example:
-Dhttps.proxyHost=10.165.3.76
-Dhttps.proxyPort=8080
-Dhttp.proxyHost=10.165.3.76
-Dhttp.proxyPort=8080
Please keep in mind that the above proxy is just an example, as we do not know which IP you’re using. Also, please ensure that you add the – right before D.
In case the proxy also needs authentication, the user will be prompted upon startup to enter the credentials.
Recent Comments