Skip to main content
Skip table of contents

Configure proxy for Outbound connections

How to configure: go to websecadmin → advanced and edit proxy-config.json, as in below example:

CODE
{
    "proxyHttpPort": 4128,
    "proxyHttpsPort": 4128,
    "proxyHttpsHost": "10.79.5.112",
    "proxyHttpHost": "10.79.5.112",
    "overwriteDiskConfig": true,
    "nonProxyHttpHosts": "localhost|develop.veridium-dev.com|dmz.develop.veridium-dev.com|shib.develop.veridium-dev.com|ssp.develop.veridium-dev.com",
    "nonProxyHttpsHosts": "localhost|develop.veridium-dev.com|dmz.develop.veridium-dev.com|shib.develop.veridium-dev.com|ssp.develop.veridium-dev.com"
}

overwriteDiskConfig → please set to true, if you want to have this configuration active for all veridium components (information from setenv.sh will be ignored).

nonProxyHttpHosts → this contains the list of hosts for which traffic will not be sent through proxy server.

How to troubleshooting:

from the webapp server, try the following:

CODE
export http_proxy=10.79.5.112:4128
export https_proxy=10.79.5.112:4128

curl https://api.push.apple.com:443
curl https://fcm.googleapis.com:443
curl https://oauth2.googleapis.com:443

In this way, it can be seen what is the issue. Based on the received error, troubleshooting can be done.

Also, you can test network connectivity to proxy, by running:

CODE
nc -zv 10.79.5.112 4128
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.