/
Configure Proxy Settings for GEO Jobe Products

Configure Proxy Settings for GEO Jobe Products

Admin Tools (2.3.1.6+):

  • Config file location: <AdminToolsDirectory>\app-server\BMOFetch\bmofetch.exe.config

  • Nodeconfig file location: <AdminToolsDirectory>\app-server\config\nodeconfig.json
    To enable the use of bmofetch.exe, set the following in nodeconfig.json:

    "useAdvancedFetch": true,

Backup My Org (1.4.1.20+):

Config file location: <BackupMyOrgDirectory>\BMOFetch\bmofetch.exe.config

Clean My Org (1.6.1.8+):

Config file location: <CleanMyOrgDirectory>\IWAFetch\iwafetch.exe.config

Symphony (1.2.0.7+):

  • Config file location: <SymphonyDirectory>\BMOFetch\bmofetch.exe.config

  • Nodeconfig file location: <SymphonyDirectory>\server-side\config\nodeconfig.json
    To enable the use of bmofetch.exe, set the following in nodeconfig.json:

    "useAdvancedFetch": true,

Configuring the Proxy file in bmofetch.exe.config (or iwafetch.exe.config for Clean My Org)

GEO Jobe products support several proxy setups via the bmofetch.exe.config file (Clean My Org: iwafetch.exe.config). If you omit proxy keys entirely, the app uses the machine’s system proxy (if any) or goes direct.

Config keys (under <appSettings>)

<add key="ProxyUrl" value="" /> <add key="ProxyUseDefaultCredentials" value="false" /> <add key="ProxyUser" value="" /> <add key="ProxyPassword" value="" /> <add key="ProxyDomain" value="" /> <add key="ProxyBypassList" value="localhost;127.0.0.1;*.corp.local" />

Field value explanations:

  • ProxyUrl

    • http://proxy:port → use this proxy explicitly

    • system → use the OS/system proxy (WinINET/WinHTTP)

    • empty/missing → don’t override; app will use the system proxy if present, otherwise direct

  • ProxyUseDefaultCredentials

    • true → send the current Windows user/service account creds to the proxy (common in corp environments)

    • false → no creds unless ProxyUser/ProxyPassword are set

  • ProxyUser/ProxyPassword/ProxyDomain

    • Use when the proxy requires a specific username/password instead of SSO

  • ProxyBypassList

    • Semicolon or comma separated; supports wildcards (e.g., *.internal)

Common scenarios

  1. No proxy (direct) — default
    Leave all proxy keys out (or set ProxyUrl to empty).
    The app will connect direct unless the OS has a system proxy configured.

  2. Explicit proxy (URL only, no auth)

    <add key="ProxyUrl" value="http://proxy.company.com:10262" /> <add key="ProxyUseDefaultCredentials" value="false" />

  3. Explicit proxy with Windows SSO (Integrated auth)

    <add key="ProxyUrl" value="http://proxy.company.com:10262" /> <add key="ProxyUseDefaultCredentials" value="true" />

  4. Explicit proxy with custom credentials

    <add key="ProxyUrl" value="http://proxy.company.com:10262" /> <add key="ProxyUseDefaultCredentials" value="false" /> <add key="ProxyUser" value="myuser" /> <add key="ProxyPassword" value="mypassword" /> <add key="ProxyDomain" value="MYDOMAIN" /> <!-- optional -->

  5. Use the system proxy (IE/WinHTTP/PAC/WPAD)

    <add key="ProxyUrl" value="system" /> <add key="ProxyUseDefaultCredentials" value="true" /> <!-- or false if no auth -->

  1. Add bypasses (applies to #2–#5)

    <add key="ProxyBypassList" value="localhost;127.0.0.1;*.corp.local;intranet-server" />

Troubleshooting

  • 407 Proxy Authentication Required

    • Set ProxyUseDefaultCredentials=true, or provide ProxyUser/ProxyPassword[/ProxyDomain].

  • Requests bypass proxy unexpectedly

    • Check ProxyBypassList and OS bypass rules (PAC/WPAD).

  • Running as a Windows Service

    • Service account’s system proxy may differ from your user session. Prefer ProxyUrl in config, or set the WinHTTP proxy for that account.