java.io.IOException

There was a problem while connecting to 172.16.63.206:22

Samebug tips1

Signals that an error occurred while attempting to connect a socket to a remote address and port. Typically, the remote host cannot be reached because of an intervening firewall, or if an intermediate router is down.


rafaelrafael

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web288

  • via Unknown by fullung,
  • via Unknown by fullung,
  • Stack trace

    • java.io.IOException: There was a problem while connecting to 172.16.63.206:22 at com.trilead.ssh2.Connection.connect(Connection.java:755) at com.trilead.ssh2.Connection.connect(Connection.java:546) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:470) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:168) at hudson.plugins.virtualbox.VirtualBoxComputerLauncher.delegateLaunch(VirtualBoxComputerLauncher.java:83) at hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:67) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:183) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.net.NoRouteToHostException: No route to host at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384) at java.net.Socket.connect(Socket.java:542) at com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:342) at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:450) at com.trilead.ssh2.Connection.connect(Connection.java:699) ... 11 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    balintnbalintn
    10 times, last one
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    rprp
    2 times, last one
    29 more bugmates