Skip to main content

ec2-plugin can create instances but doesn't keep the ssh connection



  • Gwen Sarault

    Not sure how a proxy for the PluginManager could have an impact on the startup of an EC2 slave...but seeing the same issue with no proxy.

  • Chris Campbell

    I too am having this issue; removing the proxy in PluginManager did not help.

    The plugin creates the ec2 instance fine, but never connects back to Jenkins, with the same output above.

    Interestingly, I am able to create a "manual" node in Jenkins, point it to the SAME ec2 instance created OK by the plugin, use the same Key provided to the plugin, and the Jenkins agent connects fine.

    Per another Jenkins support ticket ( ), i added "-Djenkins.ec2.bootstrapAuthSleepMs=60000", but that did not get the plugin working either.

    What's missing?



Please sign in to leave a comment.

About CloudBees Support

Our Support Engineers are available to help with any questions or problems you may have with any of our products.