Yes, the listening ports of the custom container runtime and the HTTP server in the custom container runtime must be the same. The default listening port (CAPort) of a custom container runtime is 9000. If a custom container runtime uses the default listening port, the listening port of the HTTP server started in the custom container runtime must also be 9000. If the listening port of the custom container runtime is 8080, the listening port of the HTTP server started in the custom container runtime must also be 8080.

The HTTP server started in a custom container runtime must listen on the 0.0.0.0:CAPort or *:CAPort port. If you select the 127.0.0.1:CAPort port, the request times out and the following error occurs:
{
  "ErrorCode":"FunctionNotStarted",
  "ErrorMessage":"The CA's http server cannot be started:ContainerStartDuration:25000000000. Ping CA failed due to: dial tcp 21.0.5.7:9000: getsockopt: connection refused Logs : 2019-11-29T09:53:30.859837462Z Listening on port 9000"
}