LogoLogo
  • Solution Overview
    • PLC Management and Code Versioning platform
    • Basic terminology
    • Supported automation vendors
  • Project versioning
    • How to upload and manage projects
    • How to use the Windows local client
    • How to view projects incl. changes
  • AI Generated Code Documentation
    • Overview
    • How to generate a documentation
  • Connectivity Service
    • Overview
    • Requirements
    • How to set up a Gateway
    • Configuring Proxy
    • Configuring networks
    • FAQ
  • Browser Based Engineering
    • Working with Browser Based Engineering
    • Up- and download of TIA licenses for Browser Based Engineering
    • Troubleshooting
  • Automated backup
    • Configuring automated PLC backups
  • Automated deployment
    • Directly deploying your projects
    • Deployment Requests (preview)
      • Actions with 2 Factor Authentication (preview)
  • Console administration
    • Creating an account
    • SSO via Azure Active Directory
    • Deleting an account
    • Inviting console users
    • Receiving a console invite
    • Understanding permissions
    • Managing permissions
    • Choosing a subscription plan
    • Viewing bills, downloading invoices, and managing payment methods
  • Examples
    • Quick Start Guide
    • Preparing a Raspberry Pi to be used as a Gateway
  • FAQ
    • Deployment
    • IDEaaS
Powered by GitBook
On this page
  • Pre-requisite: proxy is configured in the OS
  • Configure proxy in the Connectivity Client
  1. Connectivity Service

Configuring Proxy

Some enterprise networks are configured with a Proxy Server when accessing the Internet. The SDA Connectivity Service complies with this scenario, but an extra configuration step is needed.

PreviousHow to set up a GatewayNextConfiguring networks

Last updated 10 months ago

Pre-requisite: proxy is configured in the OS

If the host operating system is already configured with a proxy and the SDA Gateway installation succeeded, jump straight to Configure proxy in the Connectivity Client.

This requisite can be tested by looking up the environment variables that contain the address of the proxy server. In a terminal session, try echoing these variables:

$ echo HTTP_PROXY=$HTTP_PROXY \
     HTTPS_PROXY=$HTTPS_PROXY \
     ALL_PROXY=$ALL_PROXY \
     http_proxy=$http_proxy \
     https_proxy=$https_proxy \
     all_proxy=$all_proxy

If any of them exists, proxy is already configured. If not, follow to configure it globally.

Mind that a proxy address has one of the formats:

http://<proxy-address>:<port-number>
http://<username>:<password>@<proxy-address>:<port-number>

Configure proxy in the Connectivity Client

The connectivity client needs to be extra configured for proxies, as this is going to imply on the way that the application starts and connects to our IoT Broker.

Once the client is installed, the sda-gateway CLI can be used to configure proxy:

$ sudo sda-gateway proxy set --help
>> Usage: sda-gateway proxy set [OPTIONS]
>> 
>>   Set the proxy configuration
>> 
>> Options:
>>   -t, --type [http|https|socks4|socks5]
>>                                   Proxy protocol type  [required]
>>   -h, --host TEXT                 Proxy host  [required]
>>   -p, --port INTEGER              Proxy port  [required]
>>   -u, --username TEXT             Proxy username
>>   -w, --password TEXT             Proxy password
>>   --help                          Show this message and exit.

As an example:

$ sudo sda-gateway proxy set -t http -h sdaproxy.io -p 8080 -u sdauser -w sdapwd
$ sudo sda-gateway proxy get
>> http://sdauser:sdapwd@sdaproxy.io:8080

For unsetting proxy, run:

$ sudo sda-gateway proxy delete

After changing any proxy configuration, the application services needs to be restarted:

$ sudo systemctl restart sda-gateway

If the application is not restarted after configuring proxy, changes may not be effective.

this guideline