jenkinsCLI --- "Exception in thread "main" java.net.SocketTimeoutException: connect timed out"

[niristotle okram]

any suggestions/fixes for this jenkins-cli error?

I have a deploy job, which is parametrized (test, stage, prod). So, whenever there is a deploy to the "staging" env, i am trying to make Jenkins *slaves* execute a groovy script. Trying to test the jenkins-cli.jar, i got this error:

[jenkins@ip-10-0-0-92 scripts]$ java -jar jenkins-cli.jar -s https://my_jenkins_url.com/

Exception in thread "main" java.net.SocketTimeoutException: connect timed out

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

at java.net.Socket.connect(Socket.java:579)

at hudson.cli.CLI.connectViaCliPort(CLI.java:203)

at hudson.cli.CLI.<init>(CLI.java:126)

at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72)

at hudson.cli.CLI._main(CLI.java:466)

at hudson.cli.CLI.main(CLI.java:382)

Suppressed: java.io.EOFException: unexpected stream termination

at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331)

at hudson.remoting.Channel.<init>(Channel.java:421)

at hudson.remoting.Channel.<init>(Channel.java:400)

at hudson.remoting.Channel.<init>(Channel.java:396)

at hudson.remoting.Channel.<init>(Channel.java:385)

at hudson.remoting.Channel.<init>(Channel.java:377)

at hudson.remoting.Channel.<init>(Channel.java:353)

at hudson.cli.CLI.connectViaHttp(CLI.java:157)

at hudson.cli.CLI.<init>(CLI.java:130)

... 3 more

I have done:

1. Set a fixed port for TCP/IP port for CLI and slaves & its listening on the master server

2. All ports are open between the jenkins nodes

3. Went through https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI

I am using nginx with valid SSL cert. 

[niristotle okram]

i got the help command working. I use the below command. It uses the private ip of the  jenkins master instead of the public. And in my case the comm is happening between the jenkins nodes which are in the same subnet. 

[jenkins@ip-10-0-0-92 scripts]$ java -jar jenkins-cli.jar -noCertificateCheck -s https://10.0.0.91/ help --username 12345 --password banana

Skipping HTTPS certificate checks altogether. Note that this is not secure at all.

  add-job-to-view

    Adds jobs to view.

  build

    Builds a job, and optionally waits until its completion.

  cancel-quiet-down

    Cancel the effect of the "quiet-down" command.

  clear-queue

    Clears the build queue.

  connect-node

    Reconnect to a node.

  console

    Retrieves console output of a build.

  copy-job

    Copies a job.

  create-job

    Creates a new job by reading stdin as a configuration XML file.

  create-node

    Creates a new node by reading stdin as a XML configuration.

  create-view

    Creates a new view by reading stdin as a XML configuration.

  delete-builds

So, the problem is likely the nginx in use ???