Start here when something does not work. Find your symptom, read what it means, and follow the fix. Most problems come from the network, a wrong Comm Key, the wrong timezone or an unmapped code, not from the terminal.
#Quick checks (do these first)
- Is the connector PC on and showing Online on the Connectors tab?
- Does the device card say what is wrong? (It states, for example, "Connector ... is offline", "Setup required" or "No connector assigned".)
- Press Test connection on the device. Read the answer against the status table.
- Open Activity on the device: are punches arriving, and what happened to them?
#Device unreachable
"Device unreachable" or "did not answer in time".
| Check | How |
|---|---|
| Power and cable | Is the terminal on, and is its network light on? |
| Address and port | Compare with the device menu (ZKTeco: Menu → Comm. → Ethernet; port 4370). The address may have changed if the device uses DHCP: give it a fixed address. |
| Same network | The connector PC and the terminal must be on the same network segment, or routed to each other. A guest Wi-Fi or another VLAN blocks it. |
| Firewall | Allow the device's port from the PC: 4370 TCP/UDP for ZKTeco, 5010 TCP for Anviz, the web port (80) for Hikvision. |
| One connection at a time | Some terminals allow only one PC connection. Close other attendance software that is connected to the same device. |
| Ping from the PC | In a command prompt: ping <device address>. If it fails, it is the network, not SolaHR. |
#The connector
| Symptom | Fix |
|---|---|
| Connector Offline | Switch the PC on; check the service with sc query SolaHRDeviceConnect (must say RUNNING); check its internet access. Waiting punches are sent when it is back. |
| "The connector did not pick up the request" | The same: the PC is off, asleep or offline. Turn off sleep for that PC. |
| "Connector needs re-pairing" / "Connector was revoked" | Make a new pairing code and pair again (Install). |
| "Code expired - create a new one" | A pairing code lasts 15 minutes and works once. |
| Windows warns about the installer | Expected: the preview is not code-signed. Check the SHA-256 value, then More info → Run anyway. |
127.0.0.1:8790 does not open |
Another program may use that port. The service still works without the page. |
#Authentication and keys
| Symptom | Fix |
|---|---|
| Reachable · Comm Key rejected | Enter the Comm Key from the device (Menu → Comm. → PC Connection). No key means 0. Keys have 1 to 6 digits. On ZKTeco firmware Ver 6.60 the device asks to sign in even with key 0; connector 0.1.5 and later handle this, so update the connector if you still see it. |
| Reachable · device busy | Wait a minute and test again. |
| Hikvision: login refused | Use a separate device user created for SolaHR (not admin) and check that the device is activated. |
| Suprema: login refused | Use a read-only BioStar 2 operator and the exact server address (with https://). |
| "Serial mismatch" | The device at that address is not the one registered. Check the IP. |
#Setup required
Setup required is a status, not a fault of the terminal. The connection type needs the manufacturer's software on the connector PC and it is not ready. Follow Vendor SDK setup, or press Use the built-in connection instead. For most ZKTeco terminals, ZKTeco (direct) needs no extra software.
#Punches arrive but no attendance appears
| Cause | Fix |
|---|---|
| The code is not mapped | Device users → link the code. Waiting punches are written as soon as you link it. See Mapping and attendance. |
| Payroll settings for the date are missing | Add them, then Reprocess pending. |
| Before the Import history from date or before the employee's start date | Edit the device date, or correct the start date. |
| The day was already entered by HR or the portal | A device punch does not overwrite it. See Rejected punches on the Review tab. |
| The employee is suspended without pay | No attendance is created. |
| A check-out without a check-in | Add the missing check-in in Attendance. |
#Wrong times
| Symptom | Fix |
|---|---|
| Off by whole hours | Edit the device and set the right Device clock timezone (for example Asia/Amman, Asia/Dubai). |
| Off by minutes | Sync time now (Owner). Also check the device's own clock and daylight settings. |
| A night shift looks split | Check the work schedule's overnight setting in Work schedules. |
#Names and text
| Symptom | Fix |
|---|---|
Arabic names show as ??? or strange symbols |
On the device record set the text encoding: UTF-8 first, then Windows-1256 (Arabic), then GBK. Read the users again. |
| Names are cut | Many terminals allow only a short name (often 24 characters or less). |
#Changes do not work
| Symptom | Fix |
|---|---|
| "Changes to this device are turned off on the connector PC" | Turn on Allow changes to devices on the connector page. |
| Edit, enable, delete or push greyed out / "not supported here" | The connection type or model does not support it. ZKTeco direct cannot enable/disable users or copy faces; the ZKTeco SDK type can (software-tested). |
| Copy, restart or sync time missing | Owner only. |
| "The device has no free space for this" | The terminal is full of users, faces or fingerprints. Delete unused users. |
| "The device refused the change" | Check the Comm Key and that the device allows remote changes. |
#Push devices
| Symptom | Fix |
|---|---|
| "Last contact" is old or empty | Check the terminal's server setting (ZKTeco: Menu → Comm. → Cloud Server Setting): address, port, and that the terminal has network access. |
| Punches rejected | The device serial must match the one registered in SolaHR. See Quarantine. |
| Plain HTTP refused | Many push devices speak only HTTP. Ask your administrator to read the Installation readiness panel; it checks the web server rules. |
#Frequently asked questions
Does SolaHR store fingerprints or faces? No. Never. It only knows whether a person has a face or fingerprint on a device. See what is stored.
Do I have to open a port in my router? No. The connector only makes outbound connections to SolaHR. Only push devices need SolaHR to be reachable from them, which it is.
Does it work without the internet? The connector keeps working inside the office but cannot reach SolaHR; punches wait and are sent later.
Can I use more than one connector? Yes, one per site is typical. Each device is assigned to one connector.
Is my terminal supported? See Supported devices. Only the ZKTeco iFace702 was connected for real so far; other models are expected or untested. Test one first.
Can I mix connector and file import? Yes. Repeated punches are recognised and not counted twice.
How often are punches read? As you choose: every 1, 2, 5, 10, 15 or 30 minutes. See Mapping and attendance.
Is the connector safe to run? It listens only on the PC itself and keeps secrets encrypted, but it is an unsigned preview and its Windows service has not been tested on every Windows setup. Treat the PC like a server.
Where do I get help? Use solahr-dc diagnostics on the connector PC to make a support bundle without secrets, and send it with the device name and the status you see.