aha, that might be because I tested to disable UDP hole punching on the comms network. Reverting that and the error message disappeared.