Why can’t the SOPHiA Platform reach the SOPHiA GENETICS servers?

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 3 of our servers depending on your location.

France or Belgium, open access to (All in secure mode (https) and port 443):

fr.sophiagenetics.com

ddm.sophiagenetics.com

dev.sophiagenetics.com

Australia, open access to (All in secure mode (https) and port 443):

aus.sophiagenetics.com

ddm.sophiagenetics.com

dev.sophiagenetics.com

 United States, open access to (All in secure mode (https) and port 443):

us.sophiagenetics.com

ddm.sophiagenetics.com

dev.sophiagenetics.com

Canada, open access to (All in secure mode (https) and port 443):

ca.sophiagenetics.com

ddm.sophiagenetics.com

dev.sophiagenetics.com

Other countries, open access to (All in secure mode (https) and port 443):

ch.sophiagenetics.com

ddm.sophiagenetics.com

dev.sophiagenetics.com

If the SOPHiA Platform cannot automatically detect your proxy configuration based on the computer’s network settings, you will need to define the proxy configuration and force SOPHiA Platform to use it.

Example: if you need to go through the proxy “”sophiagenetics”” and the port 8000, you can create a file in c:\Users\userfolder\.dg-cache\proxyCfg.txt with the following text:

-Dhttps.proxyHost=sophiagenetics

-Dhttps.proxyPort=8000

-Dhttp.proxyHost=sophiagenetics

-Dhttp.proxyPort=8000

If your proxy also needs authentication, the user will be prompted upon startup to enter the credentials.