Versions Compared

Version Old Version 2 New Version 3
Changes made by

Marcos Moreno (Deactivated)

Marcos Moreno (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

The Site Controller software requires communication with the azeti Middleware to send out data and to receive configurations. Therefore some network ports must be opened to run the overall solution properly. Different types of communication is involved and it is mandatory to configure your firewall accordingly for proper functionality.

SIte Controller to azeti Cloud

The SiteController software running on your edge device requires outgoing traffic towards its destination azeti Control Panel server.

User Browser to azeti Cloud

The azeti Cloud is a web application that uses the websockets technology for communication and thus requires ports to be opened between the azeti Cloud Server and the users web browser.

Column
width400px
Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents

...

PortFirewallDirectionSource hostDestination hostProtocolDescription
80optionaloutgoingTomcatUser's Web BrowserHTTPWeb application (testing/dev)
8081optionaloutgoingActiveMQUser's Web BrowserWebsocketsWeb application live updates (testing/dev)
443mandatoryoutgoingTomcatUser's Web BrowserHTTPSWeb application (production)
8082mandatory

outgoing

ActiveMQ

User's Web Browser

Secure WebsocketsWeb application live updates (production)

Firewall Between Site Controller and azeti Cloud

PortFirewallDirectionSource hostDestination hostProtocolDescription
1883optional outgoingActiveMQSiteControllerMQTTSiteController from/to azeti Cloud Broker in VPN environments
8883optionaloutgoingActiveMQSiteControllerMQTT + TLSSiteController from/to azeti Cloud Broker in Internet environments

...

PortFirewallDirectionSource hostDestination hostProtocolDescription
1883
outgoingActiveMQ
MQTTSiteController from/to azeti Cloud Broker in VPN environments
8883

ActiveMQ
MQTT + TLSSiteController from/to azeti Cloud Broker in Internet environments
8081

ActiveMQ
WSWeb browser to ActiveMQ web sockets
8082

ActiveMQ
WSSWeb browser to ActiveMQ web sockets
61613

ActiveMQ
STOMPInternal connection Back-end/ActiveMQ
61614

ActiveMQ
STOMP+TLSInternal connection Back-end/ActiveMQ
61616

ActiveMQ
JMSInternal connection Back-end/ActiveMQ







5432

PostgreSQL
TCP/Postgres-specificInternal connection Back-end/PostgreSQL







8083

InfluxDB
HTTPInternal connection Back-end/InfluxDB admin interface
8086

InfluxDB
HTTPInternal connection Back-end/InfluxDB







80

Tomcat
HTTPWeb application (dev/test)
443

Tomcat
HTTPSWeb application (production)