- Knowledge Base
- FAQ
- General FAQ
-
Getting started!
- Introduction
- Step 1: Booking System Preparation
- Step 2: Humly Control Panel Installation
- Step 3: Connect HCP to Booking System
- Step 4: HCP Basic Setup - Global Settings
- Step 5: HCP Basic Setup - Default Room Settings
- Step 6: HCP Basic Setup - Add Buildings and Structure
- Step 7: Add licenses
- Step 8: Humly Room Display installation
- Step 9: Humly Booking Device Installation
-
Administration
-
Release Notes
-
Humly Control Panel
-
Humly Reservation
-
Humly Visitor
-
Humly Wayfinding
-
Humly Floor Plan
-
Humly Room Display
-
Humly Booking Device
-
FAQ
-
Latest News
The connection to HCP becomes unsecure after using the Humly Connect function
the first is the connection to HCP
When using Humly connect function, it is a must to accept the self-signed certificate to be able to connect to the device over VNC service.
The connection is established over an IP address “The Device IP Address” not using FQDN. Since the browser is connected to two destinations, the first is the connection to HCP, the second one is the connection to the device. Then it must show an insecure connection warning.
But this does not mean that the connection between the browser and the Humly Control panel is un-secure, this connection is always secured by Humly Cloud TLS if you are using Cloud Services, or it should be secured by your installed certificate if you are using the on-prem solution.