We have a server hosted in Amazon cloud which I'm accessing it remotely over ssh. I'm not aware of much details about the server setup. I had been given the IP and credentials to access it remotely.
Now, I have tried to reboot(sudo reboot) the server from the remote console. But after the reboot command, server is not coming up. I'm not able to access the server using the same IP & credentials. Could you please help me find what has gone wrong here? Does the server change its IP when we reboot ?
Thanks in advance.
-Dilip
If the server is not assigned an Elastic IP, the hostname changes upon every reboot.
Log into AWS console, find your instance and determine if the instance is assigned a hostname, or if it is assigned an elastic IP. Make sure you are using the correct information to log in.
Also, depending upon the shutdown behavior, the instance may be terminated on stop. If you log in and find your instance terminated I would suggest enabling termination protection to prevent this from occurring again.
If you are unable to log into the AWS console, I suggest contacting the server admin for further assistance.
Related
I just launched a instance on AWS and I'm trying to open the website. So I copy the Public IPv4 address and paste it on my page. But it always returns This site can’t be reached 35.78.183.239 took too long to respond.
I've changed my firewall setting to access google chrome and set security groups HTTP, HTTPS. I can't figure out where the problem is. Any suggestions?
You didn't specify what webserver or AMI is on your EC2 instance.
You need to setup an AMI or manually install and setup a webserver for anything to show, otherwise the EC2 instance, while reachable, will not respond.
Make sure that ssh access is enabled and try ssh into the machine. If you can successfully login, then you know the instance is reachable and the problem is with your webserver software. This will help you debug.
What port is your application running on? When you enable HTTP and HTTPS it only allows ports 80 and 443 on the security group. This won't help if your application runs on a different port, so you'll need to add that to your security group to allow inbound traffic.
it seems I've run though everything and it will not connect,
I've verified my firewall is not blocking anything, I reset my ssh keys, I've set my user roles, and I've tried resolving it through the cloud shell.
Code: 4003
Reason: failed to connect to backend
You may be able to connect without using the Cloud Identity-Aware Proxy.
Anyone have any ideas? I just need this to work.
vm instance- OpenLiteSpeed Wordpress
zone- us-east4-b
machine type- n1-standard-1
cpu platform- Intel Broadwell
It seems you already tried to troubleshoot issue , I had similar issue so just want to know below
what is your role in project ( owner/editor)?
VM instance having external ip or not?
If firewall blocking it will give timeout error, its not timeout error.
I am trying to fix a website that is hosted on Google Cloud Platform using VM instance. The website is giving me a connection refused error message. I have checked that the firewall rules are set up and are provided to the VM instance.
The VM external IP is static and the same IP is present on both cloud DNS and GoDaddy.
I'm also unable to SSH into the instance.
The SSH screen is stuck here and is not loading any further
I have given the necessary permissions to the instance and the user (Compute Admin, Compute Instance Admin (v1)), but still no luck.
As the instance is created from a custom image, so later, I tried creating another instance with the same config and I was able to SSH from it. So, please find some screenshots attached below if those could be of any help
netstat -a
route -n
df -h
I am new to this so any help to fix the issue and get the website up and running would be highly appreciated.
If it worked at the second attempt (2nd Instance I mean), I suspect that the SSH service hasn't started properly. I would recommend you to check the Serial Port Output, and Accessing into the Instance through the serial port in order to be able to troubleshoot it.
Note that you'll need a user to access through the serial port. If you don't have any user created, you will be able to do so using an startup-script.
Hope this helps!
I've experienced two times now of the "No data received" issue ever since I've moved my WordPress site to use RDS.
Though I could still connect to my RDS via MySQLWorkbench, but not able to connect to my instance via SSH (It shows "Operation timed out") after this issue has happened each time.
Doing "ping" in Terminal would show that my instance is "100.0% packet loss", and rebooting the instance would not fix this issue neither. I've set the correct IP for the SSH in the security groups inbound rules, and also checked that my instance is appear to be running on the EC2 console. The browser would still returns "No data received.".
Interestingly, I've found that stopping the instance, and then restart the instance and the httpd service would fix the issue. However, this issue will always come back again after couple of hours.
Could anybody help me or guide me to troubleshoot it, please?
My Amazon EC2 small instance stopped responding, I looked at the AWS console and CPU use had gone through the roof. I tried rebooting instance but it didn't respond. So I stopped it and started it again (twice).
Now says the CPU usage is fine (was triggering an alarm when breaching 90%) but still can't login via SSH and Apache is not working (my sites are down).
Anyone give me any idea how I can sort this out? I'm out of my depth a bit as unfamiliar with the ins and outs of EC2.
EDIT: console log http://pastebin.com/JWFeG7NU shows Apache, SSH, etc starting up fine but I can't access via SSH and no response to pinging website hosted on server.
If you have stop/started your instance and you were not using an elastic IP address, your instance IP has changed.
If you were using an elastic IP address, it would have become disassociated.
If you do have applications that are causing you to exceed the allocated CPU, other applications such as ssh, may become slow to respond or not respond at all within the timeout.