# component_verify_Ticket Common Troubleshooting Guide

This article mainly for the third-party platform can not normally receive the component_verify_Ticket problem provides solutions to help you locate and solve the problem can not receive the component_verify_Ticket problem.

# Common failure causes and treatment ideas

# 0. ticket push service has stopped

• Processing scheme: please refer to the interface documentationLaunch ticket push serviceRestart the service.
• Added: This interface can also be used to check if the ticket push service is working

# 1. Authorization Event Receive URL Problem

• Cause: The success character string is not normally returned after a POST request or is not just a success character string

• Treatment Scheme: Make sure to receive POST Directly returns only the character string success

# 2. Network Issues 1

• Processing idea: Please check whether the firewall has blocked the callbackiP address of WeChat first.If you have checked your own firewall or operator problems, please go to the community -Service Provider AreaPost feedback processing.

• Get WeChat's callbackiP: Reference interface documentationhttps://developers.weixin.qq.com/doc/offiaccount/Basic_Information/Get_the_WeChat_server_IP_address.html, can be usedcomponent_access_TokenCall this interface.

• Because the export IP and the import IP may change, it is recommended that users request the interface once a day to update the IP list in time.

# 3. Network Issues 2

• Processing ideas: Please check whether the firewall has banned the outerip of WeChat push ticket here. If so, please leave the IP address.

• Get the outerip of WeChat push ticket here: follow the document guidelineshttps://developers.weixin.qq.com/doc/oplatform/Third-party_Platforms/2.0/operation/thirdparty/alarm.html, join the third-party alarm group, if there is an error, the alarm information group will push the WeChat request clientip, error message, corresponding domain name, corresponding domain name resolution IP address and other information to the alarm group, so that developers can troubleshoot and solve problems.

# 4. the platform is temporarily unstable

• Reason: the temporary instability of the platform caused the component not to be pushed in time_verify_ticket

• Solution: Due to component_verify_ticket The effective time is 12 hours, than the component_access_Token Longer, so please ask the most recently available component_verify_Ticket, in component_access_Token You can use it before it expires. component_verify_ticket To update and avoid the appearance of component_verify_ticket Failed to receive updates component_access_Token The situation.

# 5. Platform failure

• In case of platform failure, please go to the community -Service Provider AreaPost feedback processing. When posting, please provide the third party platform appid together, and as clear as possible to provide more information to facilitate the location of the problem Ha.