invalid signature response means that the signature supplied when subscribing to the private or presence channel does not match the expected signature.
This can occur for one of the following reasons:
The credentials used in the signature are incorrect
The first thing to check is that the
app_secret are correctly set in the code that's used as part of the authentication.
- Are the values set at all?
- Are they set correctly? A frequent mistake is to use the
app_keyis expected and vice versa
channel_name values are not being used
The authentication process requires the a
channel_name to be supplied. If either of these values are not correctly supplied then the generated signature will not match the signature the Pusher generates.
A presence channel is being authenticated without the
Presence channels allow additional user information to be stored for a user. This data must be included when the signature is generated.
For more information see the authentication process section in the Pusher documentation.