Troubleshooting

Symptoms: a banner saying the board is offline, controls greyed out, or an empty roster on a fresh install.

1. Check the X32 is powered on and its network cable is in — the board's own Setup → Network screen shows its IP address.
2. Open ⋮→Settings→X32 and press 🔍 Scan Network for Boards. If the board appears, press Connect and you're done.
3. If the scan finds nothing, switch to ✏️ Enter Board IP Manually, type the address from the board's own screen, leave the port at 10023, and press Save & Reconnect.
4. Still nothing: the PC and the board are probably on different networks or different subnets. Check they're on the same switch and the same address range.

After connecting, the app reads every channel and bus from the board. You'll see a percentage, and changes are refused until it finishes — deliberately, so nothing is written against a half-known board.

• A normal download takes seconds to a couple of minutes depending on the network.
• If it never finishes or restarts repeatedly, that's a network problem between the PC and the board. See above.

The Servers page reflects what the cloud last heard from your installation.

1. Check the app is actually running on the church PC — look for the icon in the system tray, by the clock.
2. Check that PC has internet access. Musicians reach the app over the internet; without it, only devices on the church's own network can connect.
3. Right-click the tray icon and choose Restart.
4. Give it a minute. The status is refreshed on a timer, so it won't flip the instant the app comes back.

A row showing ⚠️ means the app and the board disagree — usually because a fader or a mute was changed at the console itself, or two people ended up assigned the same equipment.

1. Open that musician from the roster.
2. Read the warning text; it names what's wrong.
3. Press Repair. This re-applies everything that musician should have, straight to the board.

• Reconnecting… that won't clear means the browser can't reach the server. On the church network, check the PC is on; over the internet, check the phone has a signal.
• After an update, an installed (home-screen) copy can hold on to old files. Close it fully and reopen it; if it persists, remove it from the home screen and add it again.
• A blank white page usually means a stale cached copy. A hard reload — pull down to refresh, or Ctrl+Shift+R on a computer — clears it.

The server writes a log file. It's plain text, it starts fresh each time the app launches, and the last ten runs are kept.

%APPDATA%\worship-device-manager\worshipdevicemanager.log

Paste that path into File Explorer's address bar to find it. The exact path is also shown on ⋮→Settings→Logging, along with the level control — set it to DEBUG, reproduce the problem, then send the file.

Your church's configuration lives separately, and is worth knowing about if you ever need to move an installation:

C:\ProgramData\Worship Device Manager\

Both folders keep Audio Passport's former name, Worship Device Manager. That is expected — an update leaves them where they are so your settings and logs stay put.

Email support@worshipdevicemanager.com with the log, your church name, the version from ⋮→Settings→About, and roughly when it happened.