Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

On this page:

Firewall Between User's Web Browser and azeti Cloud

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

Full Networking Within azeti Cloud Installation

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
STOMP
61614

ActiveMQ
STOMP+TLS
61616

ActiveMQ
JMS







5432

PostgreSQL









8083

InfluxDB


8086

InfluxDB









80

Tomcat
HTTP
443

Tomcat
HTTPS
  • No labels