When a packet is sent to the NSCA server and the following errror appears
in the server log:
Dropping packet with invalid CRC32 - possibly due to client using wrong password or crypto algorithm?
This can be cause by a number of reasons, as NSCA provides this as a
catch-all error message.
Wrong encryption_type set
It is possible the client is not sending the packet using the correct
encryption type. Currently this module only support no encryption or the
XOR encryption. If the server is expecting something different, this is
not going to work.
Wrong encryption_password set
It is possible that the client is not using the current encryption
password. Please double-check that the client and the server are using the
NSCA server compiled using custom constants
It is possible that the NSCA server was compiled with the constants
relating to the packet changed. If you changed the constants when compiling
NSCA, you will need to setup the client to use the same constant values.
See Net::NSCA::Client::ServerConfig on
how to change these constants for the client.