Troubleshooting network connections from within Omniscope

This page helps solve common networking problems with Omniscope.

If you are able to access the internet in your browser, but Omniscope installed on the same desktop cannot (e.g. when using a connector such as a File block to retrieve data over HTTP), it's likely there is a proxy settings issue.

If your computer connects to the internet via a proxy server, often the case in larger corporate environments, Omniscope attempts to detect this automatically. Sometimes this does not work correctly, depending on how the proxy is configured.

Disabling system proxy detection (Windows)

If you are able to browse the internet in your web browser, but Omniscope is unable to connect externally, you may be encountering this problem.

Typically the following steps resolve this:

1. Edit this file using Notepad:
   C:\Program Files (x86)\Visokio Omniscope\installconfig.properties
   or
   C:\Users\[your name]\AppData\Local\Visokio Omniscope app\installconfig.properties
   (depending on where you have Omniscope installed).
   
   
2. Find the line beginning
   ADDITIONAL_JVM_ARGS=
   (If this line does not exist, there will be a commented-out line similar to:
   #ADDITIONAL_JVM_ARGS=-XX:+UseG1GC
   Remove the # at the start to uncomment it, and delete the example options after =)
   
   
3. Append the following options, space-separated, all on one line:
   -Dvisokio.disableCustomProxySelector=true
   -DenableProxyDebug=true
   -Dvisokio.disableSystemProxies=true
   It should look something like:
   ADDITIONAL_JVM_ARGS=-Dvisokio.disableCustomProxySelector=true -DenableProxyDebug=true -Dvisokio.disableSystemProxies=true
   (all on one line).
   
   
4. Save the file and restart Omniscope.

Specifying proxy settings directly

In unusual cases, you may need to configure proxy settings directly. Your proxy settings can be obtained from your network administrator, and typically comprise a proxy server host name and port, for http and https.

Windows

On Windows, edit the "installconfig.properties" file following the procedure above, but appending the following options to the "ADDITIONAL_JVM_ARGS" property, space-separated, all on one line, substituting with the necessary host names/IP addresses and prots:

-Dhttp.proxyHost=HHHH

-Dhttp.proxyPort=PPPP

-Dhttps.proxyHost=SSSS

-Dhttps.proxyHost=QQQQ

For additional options, such as listing non-proxy hosts, and configuring a SOCKS proxy, see the Java documentation on Networking Properties. All required properties listed there must be appended, space-separated and prefixed "-D", as above.

If using a Windows service, the equivalent arguments e.g.  -Dhttp.proxyHost=HHHH -Dhttp.proxyPort=PPPP, must be applied also as multiple additional wrapper.java.additional.n properties in the wrapper.conf file in the service subfolder of the installation folder, e.g.:

wrapper.java.additional.10=-Dhttp.proxyHost=HHHH

wrapper.java.additional.11=-Dhttp.proxyPort=PPPP

Linux

On Linux, the same JVM arguments as above, e.g. -Dhttp.proxyHost=HHHH -Dhttp.proxyPort=PPPP) should be applied inside _launch.sh within the installation folder. Append, space-separated, to the JAVA_VM_PARS property before the final quote ('), e.g.:

JAVA_VM_PARS='-Xms64M ... etc. ... -Dhttp.proxyHost=HHHH -Dhttp.proxyPort=PPPP'

Further help

Please get in touch at [email protected] if you are still having difficulty with this.