Using HTTP(S) proxies

Introduction

ResIOT can be configured to access web pages and services via a proxy server of your choice.

Why does ResIOT need to make HTTP(S) calls?

ResIOT needs to access web pages and services every now and then in order to work properly. Here's a few examples: HTTP pusher calls, updates, licensing, gateway remote access, third party api calls and so much more...

Configuration

In case you need to configure ResIOT to work with proxies, all binaries understand the following environment variables: http_proxy and no_proxy.

Always remember to restart ResIOT after editing these!

http_proxy: value can be like http://user:password@host:port/. User, password, and port parts are all optional.

no_proxy: a comma-separated list of servers that should not be connected through proxy. Its value can be like foo.com,bar.net:4000.

Restarting ResIOT

The easiest way to restart all ResIOT services is by rebooting your server. If you want to manually restart your services that use HTTP(S), you'll need to restart the resiot and restioservice service via systemctl or Windows services panel.