MergenHub Envest
Home/Docs/User Manual (in-app, complete)

Installation & Deployment

Setup Wizard

Windows installer (self-contained — .NET is not required on the target). Configurable during setup: OPC/REST/HTTPS ports, certificate, administrator password, EULA. It installs three services: MergenHub (core) + MergenHubDataBridge + MergenHubHistorian. It includes a domain DNS / external IP check helper.

Administrator Account page (first/clean installation only; skipped on upgrade): the user name is administrator. You sign in to the web interface, the desktop application and the REST API with this account. The password and its confirmation are required (blank/whitespace is rejected). At first installation the entered password is also added as an OPC UA user with the same name; the web and OPC UA accounts are separate. Generate strong password creates a secure 16-character password, fills both fields and copies it to the clipboard; the Copy button puts the password you typed on the clipboard at any time; the Show password checkbox removes the mask. A strong password is required if the installation is opened beyond localhost.

Note On upgrade, existing project/user data is preserved AS IS; if the "Clean installation" box is checked, ProgramData\MergenHub is reset (cannot be undone).

Publishing on the Web (domain, certificate, proxy)

This section answers a single question: from where, at which address and with which certificate will the MergenHub interface be accessed? All the settings are on the Settings → Web, REST API & Mobile page: the Access (HTTP and HTTPS gates: port and who can connect), Publishing & HTTPS (choosing your case, steps, HTTPS, public address, check), Certificate and Mobile tabs. On the Publishing & HTTPS tab, first pick your case; the page then shows only the steps for that path, each with its Done / To do status next to it. The Apply the recommended settings button fills in the missing settings (they are written when you press Save).

HTTP and HTTPS gates (Kepware layout) The Access tab has two gates. HTTP: port (default 8090) and HTTP: who can connect — This computer only (default) or All devices on the network. HTTP cannot be turned off completely: the web interface, the REST API, the desktop app and the MergenHub services use the same gate; "this computer only" closes HTTP to the network. HTTPS: on / off, port (default 443) and HTTPS: who can connect. The web interface and the REST API are served on both gates; external programs (Kepware-compatible clients, scripts) connect as in Kepware with a user name and password (HTTP Basic). Changes are applied when the service is restarted.
A · Local network onlyReached from inside the plant / office network, not from the internet. Address: like http://192.168.1.50:8090. No certificate is required; if you like, encrypt with self-signed (https://192.168.1.50). No domain needed.
B · Directly on the internetThere is no web server in front; MergenHub serves HTTPS itself. A domain + a real certificate (PFX) are required.
C · A web server in frontIIS / nginx / Apache / Caddy (reverse proxy) on the server listens on 443 and forwards to MergenHub. The certificate is on the web server; HTTPS stays off in MergenHub.

Can I open it directly with a certificate, without a web server?

Yes (path B). You do not need to install IIS or nginx: upload the certificate issued for your domain as a .pfx on the Certificate tab and turn on Enable HTTPS. MergenHub listens on 443 itself.

If I use a reverse proxy, does MergenHub need a self-signed certificate?

No (path C). The certificate visitors see is the one on the web server. The web server connects to MergenHub on the same machine over plain HTTP; in MergenHub Enable HTTPS stays off and you do not need to generate a self-signed certificate.

Is a domain required?

On a local network no — you connect by IP. If you will expose it to the internet, yes: a trusted certificate is issued to a name, not to an IP. After getting the domain, point its A record to the server's public IP (use DDNS if the IP changes).

What self-signed does and does not do

Settings → Web, REST API & Mobile → Certificate → Generate self-signed: you sign the certificate yourself, on your own behalf. It encrypts the traffic but does not verify identity: the browser shows a "Not secure" warning on every visit. It is suitable for local networks and testing; do not use it on an internet-facing system. To remove the warning you must add the generated certificate to the Windows Trusted Root Certification Authorities store on every client computer.

Note As the name asked while generating self-signed, enter what you type in the browser to reach the machine (mergenhub.firma.local or the IP, e.g. 192.168.1.50; an IP is put into the certificate as an IP address). If the address differs from the name in the certificate, the browser also shows a name mismatch error.

When a PFX is needed and how to obtain one

PFX (.pfx / .p12) = certificate + private key in one file, protected by a password. MergenHub accepts only this format (Certificate → Upload PFX). It is required whenever you use a real certificate (path B). MergenHub does not obtain or renew the certificate itself; you upload the file you obtained in one of the ways below.

Free (Let's Encrypt)Run win-acme (wacs.exe) and validate the domain; the tool produces a .pfx. Validity is 90 days: after each renewal upload the new .pfx again and restart the service. If you want automatic renewal, set up path C with Caddy (Caddy obtains and renews the certificate itself).
Purchased / corporate CAIf you were given .crt + .key, convert to PFX:
openssl pkcs12 -export -out mergenhub.pfx -inkey ozel.key -in sertifika.crt -certfile ara-zincir.crt
Ready certificate on Windowscertlm.msc → certificate → Export → include the private key → .pfx
Warning Always include the intermediate certificate (the chain). A PFX with a missing chain appears to work in the browser but gives a "certificate chain could not be verified" error on mobile devices and API clients.

A · Local network only — step by step

  1. On the Access tab set HTTP: who can connect = All devices on the network (the listen address becomes http://0.0.0.0:8090).
  2. From other computers, type http://server-IP-address:8090 in the browser.
  3. Optional encryption: Certificate → Generate self-signed (the IP or the machine name as the name), then Access → Enable HTTPS and HTTPS: who can connect = All devices on the network.
  4. Save and restart the service (tray icon → Restart Runtime).
  5. The web port must be open in Windows Firewall; setup adds this rule.

B · Direct publishing — step by step

  1. Point the domain's A record to the server's public IP.
  2. Get the certificate, convert it to PFX and upload it with Certificate → Upload PFX.
  3. On the Access tab set HTTPS: who can connect = All devices on the network — if it stays This computer only, it cannot be reached from outside.
  4. On the Publishing & HTTPS tab turn on Enable HTTPS; leave HTTPS port at 443.
  5. On the Access tab set HTTP: who can connect = This computer only: everyone on the network uses HTTPS, the desktop app keeps working over HTTP on this computer. (Redirect HTTP to HTTPS is optional; if it is on, HTTP connections on this computer are redirected too.)
  6. In the Public address field, enter https://scada.firma.com; invitation e-mails and AI/MCP links are derived from it.
  7. Save and restart the MergenHub service (port, HTTPS and certificate are applied at startup).
  8. Open the HTTPS port in Windows Firewall: setup adds rules only for the web and OPC UA ports; the HTTPS rule exists only if HTTPS was chosen during setup. The Open ports in Firewall button next to the step adds the rule.
  9. On the modem/firewall, open an external 443 → server:443 forward.
  10. Verify from outside: on a phone over mobile data, open https://scada.firma.com (a test from the same network is misleading). The Test button on the Check card tries HTTPS from this browser.
Before exposing to the internet Strengthen the Administrator password · disable unused accounts · do not expose the OPC UA port (48010) or the HTTP port (8090) to the internet, keep only 443 open · review the audit log regularly · if possible use a VPN or source-IP restriction on the firewall · put the certificate's expiry date in your calendar (the Check card shows the days left). For connections from the internet, data access keys, the MCP connection and VPN configuration work only over HTTPS.

C · Publishing behind a reverse proxy

The certificate and 443 are on the web server side; in MergenHub Enable HTTPS stays OFF. On the Publishing & HTTPS tab answer the Where is the web server? question:

  • On this computer: HTTP: who can connect = This computer only (http://127.0.0.1:8090, closed to the outside). No trusted proxy needs to be entered.
  • On another computer: HTTP: who can connect = All devices on the network, and the web server's IP in the Trusted proxies field.

The Ready proxy config button produces an Apache / nginx / IIS / Caddy configuration file for your domain. Enter the externally visible address in the Public address field.

Three proxy settings are critical (1) Buffering must be off: live values and AI responses stream via server-sent events; if they are buffered the screen looks frozen. (2) Timeout at least 300 s so long streams are not cut. (3) The Host and X-Forwarded-Proto headers must be forwarded. The ready proxy config includes all three.
If the proxy is on another machine (3.10.1) X-Forwarded-* headers are accepted only from a trusted proxy. Nothing needs to be done for a proxy on the same computer. If the proxy is on another machine, type its address into the Settings → Web, REST API & Mobile → Publishing & HTTPS → Trusted proxies field and restart the service; otherwise the server takes the connection for plain HTTP (endless redirect, the proxy's address in the audit log). Details: HTTPS / Public Exposure.
nginx:
server {
  listen 443 ssl;
  server_name scada.firma.com;
  ssl_certificate     /etc/ssl/certs/scada.crt;
  ssl_certificate_key /etc/ssl/private/scada.key;
  location / {
    proxy_pass http://127.0.0.1:8090;
    proxy_http_version 1.1;
    proxy_set_header Host              $host;
    proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_buffering off;        # canli akis (SSE) icin SART
    proxy_read_timeout 300s;
  }
}
Apache (mod_proxy + mod_proxy_http + mod_headers etkin olmali):
<VirtualHost *:443>
  ServerName scada.firma.com
  SSLEngine on
  SSLCertificateFile    /etc/ssl/certs/scada.crt
  SSLCertificateKeyFile /etc/ssl/private/scada.key
  ProxyPreserveHost On
  RequestHeader set X-Forwarded-Proto "https"
  ProxyPass        / http://127.0.0.1:8090/ flushpackets=on timeout=300
  ProxyPassReverse / http://127.0.0.1:8090/
</VirtualHost>

IIS: install URL Rewrite + Application Request Routing (ARR), add a reverse proxy rule to the site (target http://127.0.0.1:8090/), set Response buffer threshold = 0 in the ARR settings (for live streaming), and add the certificate to the IIS site binding.

Common issues

Cannot be reached from outsideHTTPS: who can connect (direct publishing) or HTTP: who can connect (local network) is still This computer only · no 443 forward · no HTTPS rule in Windows Firewall · the setting was saved but the service was not restarted.
"Not secure" warningYou are using self-signed or the address differs from the name in the certificate (Name in the certificate on the Check card).
Certificate error on mobileThe PFX has no intermediate certificate (chain).
Desktop app does not openRedirect HTTP to HTTPS is on and the certificate does not include the name localhost: turn the redirect off; HTTP: who can connect = This computer only is enough.
Screen frozen, no values arriving (proxy)Proxy buffering is on: nginx proxy_buffering off, IIS ARR buffer 0.
Session keeps dropping (proxy)Timeout is too short; set it to 300 s.
AI/MCP address looks wrongThe Public address was left empty; enter the domain there.

Service Management

Services are managed from services.msc. The core service is installed under the name "MergenHub" (important for recovery scenarios). The tray application shows the status. Settings file: %ProgramData%\MergenHub\settings.json; project: mergenhub.db.