Check points if you are using a proxy environment

Owned by Seongho Jang (Unlicensed)
Last updated: Aug 16, 2022 by Jiyoon Ahn (Unlicensed)
4 min read



Cannot connect to ARGOS Servers? — Determine if the issue is due to your network

Many companies deploy additional network features to enhance security such as proxy servers, web security servers, and/or firewalls. These features may interfere when signing-in with the ARGOS service cloud.
To determine if your company network is causing the access issues, here is what we recommend for you to try. 
  1. Using any devices connected to a public network like your home PC or your mobile phone, please sign up with ARGOS Supervisor at "https://rpa.argos-labs.com".
  2. Using a device that is located inside your company network, open browser and connect to the same page, "https://rpa.argos-labs.com", then sign-in to the Supervisor account you just created.
  3. If 2 above does not work, it is probably your company network's security configuration that is causing to block signing-in to ARGOS service cloud.


For evaluation purposes, use ARGOS POC server 

Purpose of ARGOS PROXY

For those who want to test ARGOS but find it difficult to use ARGOS SaaS due to the network environment, we are operating the ARGOS PROXY service to make testing easier. Here's an easy way to try out ARGOS solutions without bothering your organization's IT administrators.

You can use it for production environment, but there might be performance issue. We recommend to use only for experience or for POC/Testing.

How to use ARGOS PROXY


  • ARGOS Proxy IP: 61.109.249.22
  1. Add a rule to your(or customer) firewall for opening IP=61.109.249.22 & port 80/TCP 443/TCP

  2. Add below information to host file of PAM PC and User’s PC. 

    # Service URL
    61.109.249.22 api-rpa.argos-labs.com
    61.109.249.22 api2-rpa.argos-labs.com
    61.109.249.22 io-rpa.argos-labs.com
    61.109.249.22 patch-rpa.argos-labs.com
    61.109.249.22 pypi-official.argos-labs.com
    61.109.249.22 pypi-official-data.argos-labs.com
    61.109.249.22 rpa.argos-labs.com
    61.109.249.22 www.argos-labs.com
    61.109.249.22 wiki.argos-labs.com
    61.109.249.22 manager-rpa.argos-labs.com


  3. Update a local host file in your PC

    1. Use the following instructions if you’re running Windows 10 or Windows 8:
    2. Press the Windows key.
    3. Type Notepad in the search field.
    4. In the search results, right-click Notepad and select Run as administrator.
    5. From Notepad, open the following file:
      c:\Windows\System32\Drivers\etc\hosts
    6. Make the necessary changes to the file.
    7. Select File > Save to save your changes.
  4. Run STU/PAM and use it freely



For permanent fixes, please refer to tips below

Issues due to firewall

ARGOS uses AWS and AWS CDN network, so your firewall must be openly configured for "*.argos-labs.com" domains (or IP address) and 80/TCP, 443/TCP ports. Because the IP addresses of AWS and AWS CDN is changeable things, we suggest to use 'domain based policy'. If your device does not support 'domain based policy', you can use "AWS IP range" instead.

See https://ip-ranges.amazonaws.com/ip-ranges.json for more details.


Additionally, you should whitelist "Python Program Language repository" sites.  


Here is the current  (Aug 10, 2022) Service URLs and IP addresses. 


Issues due to Proxy

#1. How to find out whether you are using a proxy or not

  1. Run 'Internet Explorer'
  2. Click a cog icon() in the top right corner
  3. Select "Internet options"

4. Choose "Connections" tab

5. Click "LAN settings"

6. Check out "Proxy server" session


  • Above image shows 'No proxy' setting.

#2. issues due to proxy

STU and Supervisor uses an "Authorization" header when making requests to authentication service. Some proxies, such as ProxySG (by Symantec), strip an authorization header information by default for security. When the authentication service of ARGOS does not see the authorization header, the session cannot be established successfully and you will get '401 Unauthorized Error' from the authentication server when you trying to sign-in to STU or Supervisor.
To resolve this issue, we recommends working with your IT team to allow the authorization header through your proxy. The configuration details may differ depending on the device you are using.
For example configuration, read "Allow ProxySG to always forward server authorization upstream". 


#3. Issues due to the connection error to pypi.org

If it takes a long time from the execution of STU to the time it is usable, use the following command to check the cause. ARGOS is needed to install of python modules that downloaded from pypi.org. But, if your cannot to connect it, your STU takes a long time to start.

Attempt to upgrade pip module itself
%userprofile%\.argos-rpa.venv\Python37-32\python -m pip install -U pip

If you see a log like the one below, you need to add pypi.org to the firewall whitelist.


#4. Issues due to Self-Signed Certificate

If it takes a long time from STU execution to start, and the plugin list does not appear in STU, check the result of executing the command below.

Attempt to upgrade alabs.ppm
%userprofile%\.argos-rpa.venv\Python37-32\python-m pip install -U alabs.ppm -i https://pypi-official.argos-labs.com/pypi

If you can see a "Self-Signed Certificate" error, you'd better to your IT manager to check it out. Because ARGOS uses public & trusted SSL certificate, it might be related to your proxy and certificate settings.

You can also try the workaround of storing the self-signed certificate in the local CA repository. See https://support.kaspersky.com/CyberTrace/1.0/en-US/174127.htm.

First, you have to change "1. Open the https://127.0.0.1" to "1. Open the https://pypi-official.argos-labs.com/pypi" and follow the rest of the steps.