Overview
This article mainly introduces the common problems in using the MNS message notification function.
Possible causes and solutions
FAQ | Solution |
---|---|
The HttpEndpoint interface cannot receive messages. How can I debug them quickly? |
For detailed solutions, see Troubleshooting methods when the HttpEndpoint interface does not receive messages in the MNS. |
How do I confirm that the certificate address identified by x-mns-signing-cert-url in a push request is official to Alibaba Cloud? | detailed address, see how to confirm that the MNS push request to the public key in the certificate address is the official alibaba cloud sdks of. |
When authenticating HTTPEndpoint interface in MNS, remote request for public key certificate is time-consuming. How can authentication performance be improved? | detailed address, see use MNS in HTTPEndpoint interface authentication at how to improve authentication performance. |
Call the HttpEndpoint interface signature authentication failed. | For a detailed solution, see Signature authentication failed when using the MNS HTTPEndpoint interface. |
After the MNS subscription is successful, no message is received and no relevant records are found in the log. |
For detailed solutions, see MNS subscription is successful and no message is received. |
When writing the HttpEndpoint interface in PHP in MNS, no message body was received. |
For a detailed solution, see MNS using PHP to write the HttpEndpoint interface when not receiving message body.
|
Application scope
- MNS