Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Determine if the issue is due to your network


Many company deploy additional network features to enhance security, such as proxy servers, web security servers or firewalls. These can sometimes interfere to sign-in of ARGOS service cloud.
To determine if the network you're connected to is causing issues with using ARGOS service cloud , try to connect on a device outside of your company network such like a home pc or a mobile device (Except corporate WiFi environment). If you are able to successfully connect & sign-in to "https://rpa.argos-labs.com", your company network is likely the reason why you cannot connect or sign-in to ARGOS service cloud.


Use ARGOS POC server 


Include Page
How to use ARGOS PROXY
How to use ARGOS PROXY




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.


#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.

Code Block
languagepowershell
titleAttempt 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.

Code Block
languagepowershell
titleAttempt 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.