This may be an emergent bug. I have seen similar reports recently, here and here. Seems to be something related to custom timeout settings on macOS clients. For now, can you try one of the predefined timeout options, instead?
I don’t know if this has been reported on GitHub yet. You may want to file a bug report there.