HTTPS does not respond
On the server, the service answers over HTTP (http://127.0.0.1:8434/health/live) but not over HTTPS:
the driver or the administration app reports that the service isn't reachable, the browser shows an
error, or the connection breaks off.
Environment
Standalone Windows service with HTTPS on port 8433, certificate set up as in Set up HTTPS and the certificate.
Cause and fix
Go through the rows from top to bottom; the first one that applies is usually the cause. The commands are under Check in the guide.
| What you see | Cause | Fix |
|---|---|---|
On the server, Get-NetTCPConnection -LocalPort 8433 -State Listen returns no line | The service offers no HTTPS. No certificate was chosen during installation; the installation program then sets up HTTP on the server only | Set up the certificate: way A, or way B step 5 of the guide |
Test-NetConnection <name> -Port 8433 on the workstation: TcpTestSucceeded : False, on the server True | The server's firewall, or one in between, blocks the port | Check the firewall rule (step 6 of the guide), ask whoever runs the network firewall |
Test-NetConnection reports that the name can't be resolved | The workstation doesn't know the name | Create a DNS record for the name; check with Resolve-DnsName <name> |
Event Viewer, source Wkl.Data.Gateway: warning “Kein gültiges Zertifikat mit privatem Schlüssel für HTTPS gefunden” | No certificate in the store matches: a name other than in Subject, expired, or without a private key (only .cer imported) | Step 2 of the guide; set Subject to a name from DnsNameList, or import the .pfx |
| Event Viewer: warning “Zertifikat für HTTPS nicht lesbar” | The certificate file (File) is missing, the password is wrong, or the service account may not read the file | Check the path, the password, and read access to the file |
| Port reachable, no warning in Event Viewer, but the connection breaks off while being set up | The service account may not read the private key | Give read access: way B step 4 of the guide, or way A |
Edge: “Your connection isn't private”, NET::ERR_CERT_AUTHORITY_INVALID | The workstation doesn't trust the issuer: company CA not distributed, or a self-signed certificate | Distribute the company CA's root certificate through Group Policy |
Edge: NET::ERR_CERT_COMMON_NAME_INVALID | The name in the address isn't in the certificate, for example the short name srv01 or an IP address instead of srv01.firma.local | Use exactly the name from the certificate, in the driver, Excel, Power BI, and the administration app |
Edge: NET::ERR_CERT_DATE_INVALID | The certificate has expired, or the workstation's clock is wrong | Renew the certificate; check the time |
The service writes its messages in German. To open Event Viewer, press Windows key + R, type
eventvwr.msc, then go to Windows Logs > Application. Filter Current Log with the source
Wkl.Data.Gateway shows only the service's entries. The certificate warnings appear only once a
workstation tries an HTTPS connection. If the service's entries are missing entirely:
The service writes nothing to the event log.
Check
On a workstation, Edge shows Healthy at https://<name>:8433/health/live, without a certificate
warning.