I launched Wordpress stack for AWS launchpad on Bitnami. The instance shows its state as running in the EC2 console. I tried logging in via SSH, it doesn't connect. Also, if I try its public IP in the browser, it shows that the site could not be reached. I'm stuck on it from last 2 hours. Any help?
It looks to me that you have a firewall issue when connecting to the instance. I advise you to check if that is the case. In addition, I would also try restarting the instance or launching a new one to double check it.
Related
I have a Wordpress site hosiped.com that was live but is down at the moment. Am using Google cloud hosting.
The virtual machine instance shows running but I can't troubleshoot what the problem is. Who can help?
I wanted the site to be live.
You can check first the serial logs of your VM Instance.
The instance's operating system, BIOS, and other system-level entities often write output to the serial ports which is helpful in troubleshooting your instance.
I have a WordPress site hosted on Google Cloud, and was working very well.
With no apparent motive, stoped working and I can't access to it, neither the front panel or admin panel.
I can't access via FTP o SSH console.
The VM on Google cloud still running as far as I can see.
Errors I get:
When trying to access de website on Google Chrome:
ERR_CONNECTION_TIMED_OUT
When trying to access FTP via FileZilla:
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
When trying to access SSH:
Connection via Cloud Identity-Aware Proxy Failed Code: 4003 Reason:
failed to connect to backend You may be able to connect without using
the Cloud Identity-Aware Proxy.
i just want to update this issue.
The problem was that the memory quota.
I've increased the amounth of memory, restarted de VM and all went back to work.
Thanks
This page with SSH troubleshooting steps might be able to help you.
The issue could be solved by trying these troubleshooting steps. I think it is likely that the first one might be the cause of your issue since you mentioned it did work before.
Does the instance have a full disk? Try to expand it!
Is the firewall correctly setup, check your firewall rules and ensure that the default-allow-ssh rule is present.
Check your IAM permissions, do you have the roles required to connect to the VM?
Enable the serial console from your instance settings, connect and review the logs, they might give you some useful insights.
I have just launched an instance on AWS EC2 (free tier - t2.micro) - so I can start a Wordpress blog. I have tried connecting to this instance (using the basic 3 methods) so that I can download wordpress and get started. The problem is I am not able to connect to this instance using the 3 methods given.
I am running linux 18.04 on my laptop, so even on my AWS instance set up - I opted for Linux. When trying to connect with a standalone SSH client: I get this response ssh: connect to host ec2-198-51-100-1.compute-1.amazonaws.com port 22: Connection refused .
When using EC2 Instance Connect : There was a problem setting up the instance connection
An error occurred and we were unable to connect or stay connected to your instance. If this instance has just started up, try again in a minute or two. i get that response. With the last option of using Java SSH Client directly from my browser (Java required) - nothing happens when I click the launch ssh client blue button(it's as if it freezes). Has anyone else ever experienced this? how did they get through it?
To answer myself - here is the solution that worked:
Since I hadn't specified a key pair when launching the ec2 linux instance. I terminated the instance and launch a new one (made sure the key pair is specified this time). I replaced the .pem file of my key pair,with a new one.
I created an AWS server and installed wordpress with an elastic ip address and verified that the default website was up and running.
I wanted to make a backup image at that point so that I could use it as a beginning point for other websites. However, after getting the AMI running and attaching the elastic ip address to it, I got an "connection refused" error. I can both SSH and FTP into the server, but the wordpress site is offline. I then switched the elastic ip back to the original server and got the exact same issue.
I'm guessing that this is a "change of ip" type error(?) (although, when I've seen that before, the connection has never been outright refused... it usually allows at least access to the admin area of the website) but I thought by using an elastic ip address that I would avoid that. I'm also confused by the error in the first server, since the database still has that address.
Any ideas about how to troubleshoot something like that? Is there anything else that it could be?
Well.... I missed something vital.
Using an AMI works just fine with an elastic ip address. I had forgotten to make sure the webserver (httpd) and mysqld were running with :
service httpd restart
and
service mysqld restart
What made it click was reading that the main reason for this error is that there is listener to the incoming data.
Duh.
I have installed a LAMP server on an EC2 instance. Then I created an AMI so that I can easily spin up instances in the future.
Today I went back to spin up one such instance, and to my surprise the IP in the configuration is wrong. Basically when I first installed the LAMP server, Wordpress detected the IP and configured accordingly. Now on the instance that I launched today the IP is different, but the configuration for the previous IP is still there.
Now, I know how to change Wordpress IP. My question is: How can I make this step automatic when I launch an EC2 instance from an AMI?
Thanks
Instance Metadata will give you a lot of information about the current EC2 instace. You can use that + some hand-crafted shell scripts which will be triggered on boot to update configuration.
An alternative solution is to use some configuration management tool (Chef, Ansible ... ). To help you configure the application.