Loading Profile...
EC2 Instance / SSH woes
Great service. However after setting up my server and deploying it to EC2 I can't access the machine via SSH.
I've confirmed that the necessary security group exists with the appropriate permissions but all attempts to SSH into the machine are met with a 'Connection Refused' response like the sshd isn't running.
The only change from the standard Rails 2.1 server is that I've associated an elastic IP address to the server before attempting the first connection.
Any pointers would be really welcome!
Thanks.
https://elasticserver.com/server/7611...
Update: I also don't have any of the additional tabs mentioned here -> http://blog.elasticserver.com/2008/03...
I've confirmed that the necessary security group exists with the appropriate permissions but all attempts to SSH into the machine are met with a 'Connection Refused' response like the sshd isn't running.
The only change from the standard Rails 2.1 server is that I've associated an elastic IP address to the server before attempting the first connection.
Any pointers would be really welcome!
Thanks.
https://elasticserver.com/server/7611...
Update: I also don't have any of the additional tabs mentioned here -> http://blog.elasticserver.com/2008/03...
I’m frustrated
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I built a new server using a similar configuration and it now works. Haven't tried setting the elastic IP yet but I even have the new fancy admin interface now :) -
Inappropriate?Armand,
Glad to know that you managed to get it working. Sorry about the initial problem.
We have tested with elastic IP addresses in the past and things have worked, but it's possible that the specific timing is important. If so we'll document it and then try to make things work better.
Thanks for your feedback.
Nicholas
Update: I've just tried adding an elastic IP address to a new instance -- this, of course, changes the public DNS name as it replaces the existing IP address and the DNS record associated. If you're using ElasticServer.com's tools to link to your machine then the DNS record will no longer be the correct one. (Something for us to think about and fix.) But if you SSH directly to the new IP address (or modify EC2's DNS name appropriately) you shouldn't have any problems.
I’m thankful
-
Inappropriate?Thanks for the quick replies! I did try and reboot the instance a couple of times without change.
I also removed the elastic IP and tried on the public DNS again without success. (I could access the server on http but not ssh)
One additional bit of info that might help : I definitely had a very different CohesiveFT elastic server management interface with the first server I built. It basically only allowed time sync, password changes and Passenger and MySQL services to be restarted.
The new one is perfect! Thanks for a great service.
I’m happy
EMPLOYEE
EMPLOYEE
