CRC mismatch despite having identical configurations for Client and Server

I'm trying to write my own network manager with separate client and server gameobjects, but connecting with a client to the server results in "UNet Client Disconnect Error: CRCMismatch", despite the client and server configuration being the same.

Configuring the NetworkServer on the client fixed this when running inside the editor, but not in the build. Also, it's odd why would I need to do that on a client.

Here's the code for NWServer.cs and NWClient.cs. I'm using version 5.2.3f1.

 

Yes, I tried Connect() and ConnectWithSimulator(), ended up with CRCMismatch in both cases.

 

Are you using AddComponent<NetworkBehaviour script> during runtime? I've found this can create mismatch errors.

 

It doesn't use NetworkBehaviour at all, as it's only clientside or serverside. I'm using only NetworkServer and NetworkClient + Network Messages for communication.

Edit: Turns out that not configuring the client / server doesn't give me an error. But what could differ in them?

 

@TFlippy Were you able to find a way to use a custom configuration without getting the mismatch error? I'm having a similar issue.

 

Not really, I was forced to use the default one.