NOVA-C Port bug

This behavior affects the PureLife NOVA-C app in conjunction with self-hosted instances.

Description of the problem #

The sensor cannot connect to the PureLife Cloud, although the temporary solution to the connection bug has been implemented.

The problem is divided into two parts:

1. The PureLife Cloud uses port 10010 for the NOVA-C port by default, but the app always assumes that port 1061 is used.
2. The app sends the port of the server URL to the sensor.

Temporary solution #

In the PureLife Cloud configuration file, the NOVA-C server should be set to listen on port 1061.

# Configuration of the Qinglan server.
[Qinglan]

  # Activates or deactivates the qinglan server.
  Enabled = true

  # Listen address of the server.
-  ListenAddress = ":10010"
+  ListenAddress = ":1061"

  # Hostname via which the sensor reaches the server.
  Host = "your-hostname"

  # Port via which the sensor reaches the server.
- Port = 10010
+ Port = 1061

If Docker is used, the port mapping should be adapted

purelife-cloud:
   ...
   ports:
      - "8080:8080"
      - "10000:10000"
      - "10001:10001"
-     - "10010:10010"
+     - "1061:1061"
   ...

It must also be ensured that the PureLife Cloud web server uses the standard HTTP/S port. This means that the web server must be accessible via port 80 for an unencrypted connection or via port 443 for an encrypted connection (TLS).

Likewise, no port may be specified for the server in the PureLife NOVA-C app.

Final Solution #

An update to the PureLife NOVA-C app allows a custom port to be entered and used. The app no ​​longer appends the port to the server URL.