Documentation Index

Fetch the complete documentation index at: https://docs.homag.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Network requirements

Prev Next

Is there a firewall active on your network? If so, please check the following network requirements with your network administrator:

  • Please activate a DHCP server in the network – for automatic network integration (IP address assignment for the )

  • Please enable port 443 in the direction of the Internet – for encrypted communication to the Internet

  • Please enable the NTP protocol (UDP port 123) to the Internet – for time synchronization

 Internet Settings

Priority

Port

Protocol

Protocol Name

Description

required

123

UDP

NTP

Access to the time server provided by the dhcp server - without NTP, no secure connections can be established because certificates cannot be validated.

required

53

UDP

DNS

Domain Name Service – name resolution on the Internet. With this protocol, Internet addresses (e.g. https:// *.tapio.one/) are resolved into IP addresses.

required

443

TCP

HTTPS

Encrypted connection to the Internet. Required to connect the tapio Cloud and the HOMAG Cloud Services.

optional*

13

ICMP

ICMP

Outgoing pings are required to verify the connection to the tapio Cloud.

* Optional: These ports are not required for the operation of the CUBE and are used for diagnostics and analysis in support cases.

Settings for the internal network

The HOMAG CUBE has various diagnostic services that should be accessible in the local network. We recommend that you make these services available only on the internal network.

Priority

Port

Protocol

Name of the protocol

Description

required

80

(45001)

TCP

HTTP

Tapio Cloud Connector Local Diagnostics Page

required

5555

TCP

HTTP

Cloud Connector Diagnostics Page

optional*

5353

UDP

mDNS

Multicast DNS service for providing the HOMAG Cube name in the local network

optional*

5355

UDP

LLMNR

Link-Local Multicast Name Resolution; allows hosts to perform name resolution for devices on the same LAN.

optional*

13

ICMP

ICMP

Incoming pings to check if the CUBE is online - Attention: Only one ping per second is allowed!

optional*

22

TCP

SSH

The SSH service is disabled by default and must be enabled manually through the Diagnostic Web Interface. In the case of local maintenance or remote maintenance, the service employee can activate the function manually. When the SSH service is enabled, the status is displayed in the diagnostic pages and via the status light

* Optional: These ports are not required for the operation of the CUBE and are used for diagnostics and analysis in support cases.

Required URLs

Used for

URL

Description / Further information

tapio Discovery Service

https://disco.tapio.one/

Further information:

service@tapio.one

tapio Realtime Data

https:// *.azure-devices.net/

https://iothubcloudgwayprodwe01.azure-devices.net

Further information:

service@tapio.one

tapio Diagnostics Data

https://dc.services.visualstudio.com

https://dc.applicationinsights.microsoft.com
See here: https://docs.microsoft.com/en-us/azure/application-insights/app-insights-ip-addresses

Further information:

service@tapio.one

https://docs.microsoft.com/en-us/azure/application-insights/app-insights-ip-addresses

tapio Login

https://tapiousers.onmicrosoft.com

https://login.microsoftonline.com/

Further information:

service@tapio.one

tapio Additional tapio services

https:// *.tapio.one/

Further information:

service@tapio.one

HOMAG sh-core API

https://smarthardware-core.homag.cloud

API for the firmware update

HOMAG Storage

https://dfshcoreprdeu01sa.blob.core.windows.net/* 

Firmware update data storage

Time synchronization (fallback)

time.windos.com
time1.google.com
time2.google.com
time3.google.com
time4.google.com

These URLs serve as a substitute function if a valid NTP server has not been configured via DHCP or via the local configuration page.