1. Error message “Server return failure” appears when selecting “Create via API Mode”

Cause: The link is connected (the physical network connection is normal, i.e., the network is available), but the server returned a non-200 OK HTTP status code (such as 403, 404, 500, etc.) after receiving the request.
Solution: Check the backend logs or network layer logs to confirm whether the server received the request, and view the error logs to locate the business logic error.

2. When selecting “Create via API Mode” to create a robot, the prompt “Network connection failed” appears.

Cause: The smart robot attempted to connect to your server URL but failed during the TCP handshake phase, indicating that the request was blocked.
Solution:
(1) Public network connectivity: Confirm that the provided URL is accessible in a public network environment (you can try testing it using mobile data).
(2) Firewall policy: Check whether the server firewall (such as security groups, iptables) has blocked the request.
(3) Certificate issue: If using HTTPS, please ensure that the SSL certificate is valid and configured correctly, and is not a self-signed or expired certificate.

3. When selecting “Create via API Mode” to create a robot, the prompt “Intranet URL not supported” appears.

Cause: The entered domain address resolves to a private IP range (e.g., 192.168.x.x, 10.x.x.x, 127.0.0.1, or localhost). The smart robot cannot access intranet environments from the public network.
Solution: Replace the URL with a public domain. Use a domain that is publicly accessible.

4. Error message “Server returned an error” appears when selecting “Create via API Mode”

Cause: The decrypted plaintext echostr was not returned.
Solution: Please refer to the API documentation to provide the correct response.

5. When creating a robot, an error message appears: “The service did not respond correctly, please confirm and try again.”

If you selected “Create via API Mode” when creating the robot, the URL validity must be verified. Please correctly respond to WeCom’s request as per the API documentation guidelines, or refer to the API documentation.
Note:
(1) The URL filled in does not support intranet links or intranet IPs. Intranet links/IPs will prompt “Network connection failed”.
(2) If you are using a third-party platform’s tutorial service for configuration, please consult the corresponding third party.

6. It promotes “Login Timeout, Please Try Again” when you creating a smart robot in the WeCom for Mac app

In the WeCom for Mac app, perform the following operation: press Command + Shift + Control + D at the same time -> enter debug mode -> click Debug in the upper-left corner -> navigate to Browser & WebView Related -> Webview Type Settings -> check “Use Console Configuration (Use WKWebview)”, and then proceed with the creation.