The local server does not answer (port 5600)

The desktop app runs as one process. It keeps your activity in a local server that listens on port 5600 of your own computer only, and sends it to Workify360 from there. When you quit the app, the local server stops too.

Signs

• Help ▸ Troubleshoot this computer reports “The local Workify360 Focus service does not answer on port 5600.”
• The app does not start and says “Port 5600 is already in use, so Workify360 Focus cannot start. Quit the other program and try again.”
• The app says “The local Workify360 Focus server could not be started. Please start the app again.” or “The local Workify360 Focus server stopped unexpectedly. Please start the app again.”

Nothing is lost meanwhile: what the app recorded waits on your computer and is sent once the local server runs again.

Start the app again

1. Choose Quit Workify360 Focus in the menu, if the app is running.
2. Wait a few seconds, then start Workify360 Focus again.
3. Choose Help ▸ Troubleshoot this computer to check that the finding is gone.

Another program uses port 5600

If the app says that port 5600 is already in use, another program on your computer listens on it, for example a separate ActivityWatch installation, which uses the same port. Find out which program it is:

• macOS and Linux: run this command in Terminal; it prints the program that listens on the port:

  lsof -nP -iTCP:5600 -sTCP:LISTEN

• Windows: run this command in PowerShell:

  Get-Process -Id (Get-NetTCPConnection -LocalPort 5600 -State Listen).OwningProcess

Quit that program, or remove it from the programs that start at login, and start Workify360 Focus again. If you need the other program, report a problem and say which program it is.

If it keeps happening

Restart the computer and start Workify360 Focus again. If the local server still does not answer, report a problem: the diagnostics show the port in localServer.port and whether the server runs in localServer.listening.