Troubleshooting

Solutions to the problems people actually run into.

Start here

The page will not open

First: is the service running? Open JudoNet Monitor. If it says STOPPED, press START SERVICE.

This is by far the most common cause, especially after the PC has restarted — JudoNet does not start with Windows and nothing warns you that it is not running.

If the service is running:

• The address is http://localhost:5220 — http, not https, and port 5220. An old bookmark with a different address will not work.
• Use Open In Browser in the Monitor rather than typing it. That also signs you in.
• From another PC, replace localhost with the JudoNet PC's name or address, and expect read-only access.

I only have read-only access

You can see everything and change nothing: switches, buttons and settings are greyed out.

That is the normal state when the page was not opened with the Open In Browser button — for example when you typed the address on another PC.

To get full access, someone with access to the JudoNet PC presses Copy Access Token to Clipboard in JudoNet Monitor and sends you the token; you paste it under Access Token in the left-hand menu. Full detail in access tokens.

A scoreboard does not appear

Work through these in order.

1. Is it switched on and on the right network?

Obvious, but check it first. The scoreboard PC must be on the same local network as JudoNet, by cable.

2. Is broadcast traffic being blocked?

Scoreboards announce themselves by UDP broadcast on port 8888. Many managed switches and virtually all guest Wi-Fi networks block that.

This is the usual cause when a scoreboard is definitely on, definitely reachable, and simply never appears. It is a network configuration problem, not a JudoNet problem.

3. Is the firewall allowing JudoNet?

JudoNet adds its own firewall rules on startup, but only when it has administrator rights. Check that rules named _JudoNet UDP 8888, _JudoNet UDP 18918, _JudoNet UDP 123 and _JudoNet NT Access exist in Windows Defender Firewall.

4. Was it removed from the list?

A scoreboard that stops announcing itself is dropped after about a minute. That much is harmless: it keeps its settings, and comes back enabled and relaying as soon as it announces itself again.

Pressing Remove is not harmless. That forgets the scoreboard's settings, so when it announces itself again — often within seconds — it returns as newly discovered, and a newly discovered scoreboard is disabled. The row looks present and connected while that mat relays nothing, and no alert is raised for it. If a mat has stopped being recorded and its row otherwise looks normal, check the Enable switch first.

Remove now asks before it does that, and the message says so — but a scoreboard removed before that was added will still be sitting there disabled.

A scoreboard appears but sends nothing

The scoreboard is in the list, but the contest information stays empty.

Is it enabled?

Look at the Enable switch on that scoreboard's row. Grey means disabled, and a disabled scoreboard is watched but not recorded. Newly seen scoreboards always start disabled. Click the switch; it turns green.

This is the single most common cause, and it looks exactly like a fault.

Is the WebSocket port right?

Discovery and the data connection are separate. JudoNet finds a scoreboard by broadcast, then opens a WebSocket to it — on the port that scoreboard announces, or on Scoreboard WebSocket Port if it announces none.

So a wrong setting no longer silences everything. It affects only boards that announce no port of their own; a board that states its port is unaffected. If every scoreboard is listed but silent, this setting is unlikely to be the cause — look at the network instead.

The port actually dialled is not shown anywhere in the interface. JudoNet writes it to the log as Connecting to ws://10.0.0.5:18855/ws when it connects, but that line is written at debug level and is not in the default log — ask support to turn on debug logging if the port in use has to be confirmed.

Is it connected to two networks?

A scoreboard on both cable and Wi-Fi announces itself on both addresses, and the connection may keep dropping and re-establishing. Disable Wi-Fi on scoreboard PCs, and make sure only one address is selected.

Nothing is going online

Contests are being received — you can see live data — but nothing reaches the platform.

Check, in order:

1. Is a JudoManager server selected? Without one, JudoNet does not know where to send anything. Live data → JudoManager Servers.
2. Are the master switches on? Store Online and Display Online do different jobs; both are off by default after a fresh install.
3. Is the token valid? On the Settings page, use Test token for JudoManager, or Refresh Token. An expired token produces API failures in the alerts.
4. Is the internet working? Look at the network check graph. A rising line means uploads will be slow or failing.
5. Read the alerts. API failures are reported on Alerts and Errors with the reason, which is usually specific enough to act on.

The CutterV2 finds no contests

The Video CutterV2 reports Finished contests: 0 while fights are clearly finishing.

JudoNet is the CutterV2's only source of timings, so the fault is usually here.

Time warnings

JudoNet's own clock

The left-hand menu says JudoNet's time is ahead or behind, or that trusted time was never established.

JudoNet corrects its own clock on startup and checks every minute, so a persistent warning means it cannot reach a time server. Check the internet connection.

Trusted startup time was not established is the more serious message: JudoNet could not reach a time server when it started, so it is using the PC's own clock and timestamps may be wrong. Fix the connection and restart the service.

Another machine says Sync Time!

JudoNet reports on the clocks of scoreboards, JudoManager servers, FairReplay Recorders and other JudoNets — but it cannot correct any of them. Somebody has to go to that machine and fix its clock.

Do this the day before if you can. A scoreboard with a wrong clock records contests at the wrong time, and the video is cut from the wrong place.

TZ mismatch!

The machine's time zone differs from JudoNet's, which is a different problem from the clock being wrong.

Duplicate mat

Two scoreboards claim the same mat number, and JudoNet shows a duplicate-mat warning.

JudoNet has no way to tell which is the real one, so that mat's data cannot be trusted until it is fixed. Either correct the mat setting on one of the scoreboard PCs, or remove the scoreboard that should not be there.

Do not leave this for later. Every contest recorded for that mat meanwhile is suspect.

Everything is duplicated

Contests appear twice online, or FairReplay receives every marker twice.

More than one JudoNet is running with the same switches on. Open Live data → JudoNet Services: a conflicting instance is highlighted orange with an asterisk by its name.

Only one JudoNet on the network may have Store Online, Display Online, Broadcast UDP to Graphics or Broadcast UDP to FR enabled. Switch the extras off on the others. A backup JudoNet should have Store Locally only.

Alerts that will not go away

An alert with a red circle is still happening. A green one has resolved itself and is only there for the record — dismiss it with the X.

If a red alert persists after you have fixed the cause, dismiss it and see whether it comes back. Alerts are raised when a problem is detected, and some only clear on the next check.

A scoreboard disconnected alert is a special case, and it used to be the awkward one. It turns green by itself when that scoreboard sends its next packet, and it disappears altogether if the scoreboard is removed — whether you removed it or JudoNet dropped it after a minute of silence. So a red one means JudoNet is still watching that scoreboard and has not heard from it. In older versions it could stay red for a scoreboard that had already come back; if you see that, check the version.

Log files

Everything JudoNet does is written to disk, in far more detail than the page shows. Open Log Folder in JudoNet Monitor opens the folder directly:

C:\JudoNet\logs

Open them with Notepad or any text editor. When reporting a problem, send the whole day's folder rather than one file.

Getting help

Have ready:

• The JudoNet version, from the top of the left-hand menu.
• What the alerts say.
• The contest code if it concerns one contest.
• The log folder for the day.
• What changed recently — a new PC, a network change, a different venue.

The Documentation link at the bottom of the left-hand menu opens this documentation.