KBEC-00148 - Debugging port connection failures

Article ID:360033193811
1 minute readKnowledge base
On this page

Summary

After entering a resource in CloudBees CD (CloudBees Flow), the web GUI shows the CloudBees CD (CloudBees Flow) Agent ping failing with the message "Connection refused: no further information".

Use the following techniques to identify if the problem is outside of CloudBees CD (CloudBees Flow).

Techniques

  1. Use ping to check the network connections

    1. From the CloudBees CD (CloudBees Flow) Agent, ping the CloudBees CD (CloudBees Flow) Server.

      1. If you get an error message, fix the networking problem before proceeding.

      2. If the screen responds with a ping packet, ping is working OK from the agent.

    2. From the CloudBees CD (CloudBees Flow) Server, ping the agent

      1. If you get an error message, fix the networking problem before proceeding.

      2. If the screen responds with a ping packet, ping is working OK from the server.

  2. Use telnet to check the port connections

    1. From the CloudBees CD (CloudBees Flow) Agent, "telnet 8443":

      1. If you get an error message, fix the networking problem before proceeding.

      2. If the screen responds with an "empty frame", telnet is working OK from the agent.

    2. From the CloudBees CD (CloudBees Flow) Server, "telnet 8443":

      1. If you get an error message, fix the networking problem before proceeding.

      2. If the screen responds with an "empty frame", telnet is working OK from the server.