ENLYZE
🇬🇧 ENLYZE
🇬🇧 ENLYZE
  • Welcome to ENLYZE
  • Getting Started
    • Quickstart
  • Guides
    • Platform Configuration
    • Machine Setup
      • Variable Selection
      • Configuring OEE Data Collection
      • Machine Data Sheet Template
    • Defining Downtime Reasons
    • Downtime Contextualisation
    • Connecting Booking Data
      • Integration of MES, BDE, or ERP-Systems
      • Synchronising Production Context via Machine Data
      • Booking Production Orders via the ENLYZE App
    • SPARK Setup
      • Preparations
      • Installation
      • Connecting to the Manufacturing Data Platform
    • ENLYZE EDGE
      • Accessing the Interface
      • Configuring the Network
      • Setting Up Routes
      • Managing Routes
      • Network Tools
      • Troubleshooting
  • PLATFORM
    • Integrations
      • Grafana
        • Structure of the ENLYZE Data Sources for Grafana
        • Connecting ENLYZE to Grafana
        • Tutorials
          • First steps with Platform Grafana
          • Grafana Basics for Process Monitoring
          • OEE data with Infinity data source
          • Mapping UUIDs to Display Names with Infinity Data Source
      • Power BI
        • Installing the ENLYZE Power BI Integration
        • Structure of the ENLYZE Power BI Connector
        • Tutorials
          • Getting Started with the ENLYZE Power BI Connector
          • Querying Time Series Data from Machine Variables
          • Querying Machine Productivity Metrics
          • Mapping UUIDs to Display Names
          • Calculating Aggregated Timeseries Data
  • EDGE
    • Overview EDGE Functionalities
    • SPARK Edge Device
    • ENLYZE EDGE
  • IT Security
    • IT Security
  • Why is the connection secure even though a warning is displayed
  • How to Choose the Right Integration Scenario?
  • Resources
    • Glossary
Powered by GitBook
On this page
  • What happens in the background?
  • Why does the warning appear anyway?
  • Why isn't an official certificate practical for Edge devices?
  • What does this mean for you?
  • 🛡️ Conclusion:

Why is the connection secure even though a warning is displayed

PreviousIT SecurityNextHow to Choose the Right Integration Scenario?

Last updated 22 days ago

When opening the address for the ENLYZE EDGE interface in your browser, the following warning may appear:

This can be unsettling—but in this case, it's completely normal and not a sign of an actual security issue.

What happens in the background?

Each SPARK Edge device uses an SSL/TLS certificate for encrypted communication. This certificate:

  • ensures that the connection between your browser and the device is encrypted.

Why does the warning appear anyway?

For a browser to automatically accept a certificate, it must be issued by an official Certificate Authority (CA)—for example, by organizations like Let's Encrypt, DigiCert, or Sectigo. These trusted authorities verify the authenticity of websites and domains on the internet.

However, the certificates used by SPARK Edge devices are not issued by an official CA. That's why the browser displays a warning.

Why isn't an official certificate practical for Edge devices?

The ENLYZE EDGE setup interface is used in local networks or offline environments. This means:

  • No public domain name is available.

  • There is no internet access to retrieve an official certificate.

  • The IP address is dynamic and varies from device to device.

Because of these conditions, a SPARK cannot use a certificate signed by a public CA.

Instead, the SPARK automatically generates a self-signed certificate tailored to the local IP address upon initialization. Although browsers do not automatically trust this certificate, it provides the same level of secure encryption as an officially signed certificate.

What does this mean for you?

  • The connection is encrypted: Your data is protected from third-party access.

  • The warning is purely technical: It appears because the certificate isn't CA-accredited—not because there’s an actual security risk.

🛡️ Conclusion:

The connection is technically secure and encrypted. The browser warning is a standard mechanism for non-public certificates and is not a cause for concern in this case.


Let me know if you’d like this added to a help center page or need the screenshot caption translated too.

Screenshot: Not a secure connection in the browser