For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Isaac_S__177992's avatar
Isaac_S__177992
Icon for Nimbostratus rankNimbostratus
Nov 21, 2014

Connection closed

Upon launching an F5 BIG-IP VE AMI on EC2 (I'm using the 25Mbps trial edition), I notice that I can establish SSH connection to the instance (as well as HTTPS connection), but can't log in at all.

 

Trying key-based login with the key pair provided by Amazon, I'm getting a "Connection closed by " error message.

 

Not necessarily looking for an instant answer as to what's wrong (although that would be welcome); but what bothers me most is that I have no idea how to even go about troubleshooting this.

 

Accessing via HTTPS, I can see the login prompt. Obviously I can't login though because I don't know what the admin password is (I read that I should SSH into the instance in order to reset the admin password).

 

Any ideas?

 

application delivery
aws
cloud
deployment
LTM

7 Replies

    • Riley_Schuit_82's avatar
      Riley_Schuit_82
      Historic F5 Account
      Nov 21, 2014
      That will not work, it will require to use host based authentication in AWS.
    • Riley_Schuit_82's avatar
      Riley_Schuit_82
      Historic F5 Account
      Nov 22, 2014
      Just for informations sake; he is talking about how the root account's (that can not be accessed via the web interface) default password is 'default'. In AWS, you need to login via ssh as root that ties into your ssh key, then you can alter the admin password via the passwd command.
  • Riley_Schuit_82's avatar
    Riley_Schuit_82
    Historic F5 Account
    Nov 21, 2014

    I have had issues in the past were it was resetting my attempted connection. After waiting a bit, just magically worked. I feel it was in relation to the EIP association with the private IP of the VPC. I blame AWS.

     

  • ChrisMutzel_151's avatar
    ChrisMutzel_151
    Icon for Altocumulus rankAltocumulus
    Jan 21, 2015

    I had this problem as well. In my case, I was working on the 11.6 version of bigIp, but mistakenly followed the instructions for bigIp 11.4 In the documentation the credentials were different "ec2-user@" versus "root@..." to log into the device on the mgmt port.

     

    I am not sure if this is your problem, but I continually got the same "Connection closed", even when I double checked my private key matched the one stored in EC2.