If you deploy vMA 5.0 within your virtual infrastructure will find the first time you try to access it by SSH that the appliance is continuously rejecting your connections.
Try to check if SSH is enabled and running and will se that everything is OK.
So you will be asking yourself, what the hell is going on? BTW restarting the service doesn’t help either.
The key to fix this issue is in the
hosts.allow files. In Unix and Linux systems this files are used by the TCP Wrapper daemon
tcpd to decide whether or not to accept an incoming connection.
If you look into
host.deny will see that everything is denied by default.
Add the following line to the
Now you can access the appliance via SSH.