Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Health Test via URLs/ Incorrect URL
Updated on 2024-09-23 GMT+08:00
View PDF
Share

Incorrect URL

Status code was -1 and not [200]: Request failed: urlopen error [Errno -2] Unknown name or service

Symptoms

The error message "msg": "Status code was -1 and not [200]: Request failed: urlopen error [Errno -2] " is displayed.

Cause Analysis

The URL is incorrect. As a result, the system cannot parse the URL.

Solution

Check whether the URL in the action is correct.

Status code was -1 and not [200]: Request failed: urlopen error timed out

Symptoms

The error message "msg": "Status code was -1 and not [200]: Request failed: urlopen error timed out" is displayed.

Cause Analysis

  • The domain name in the URL is correct but the URL does not exist.
  • The requested service does not exist.
  • No inbound rule is added to the security group for the port in the URL.

Solution

Check whether the URL in the action is correct.

For details, see Prerequisites for Creating a Host Cluster in the User Guide. Add an inbound rule to the security group for the port in the URL and verify the deployment result again.

Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111]> Access denied

Symptoms

The error message "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111]> " is displayed.

Cause Analysis

The service is not started.

Solution

  1. Manually start the service and check whether it can be started properly.
  2. Increase the waiting time of the URL health test to ensure that the service can be started successfully.
Parent topic: Health Test via URLs