I have a WordPress website and It's working perfectly but sometimes more than 3-4 times in a day it's going down and display error "Error Establishing a Database Connection".
I am using AWS server. Every time I have open the putty and rebooting the server.
Below command, I am using on putty
sudo -i
sudo reboot
Some time login on AWS then Action->instance state->Reboot and then it's working.
Sometimes "The connection has timed out".
Would you help me out what is the issue with AWS server? Currently, my plane is micro.
I too faced the same issue and despite trying the suggestions, it didn't work.
Finally did two changes and it worked-
1- used My sql 5.6.40 version
2- Also added All traffic to outbound rule in the EC2 Security group (WebDMZ).
Related
I am trying to deploy a Nodejs & WordPress website together on an ubuntu server and I am using apache2 for my server config. Everything works fine initially. But after some time my website start showing connection timeout in the browser and when I checked the Ubuntu machine then I found the following:
I checked the error log and increased the worker limit but then got this error again.
I also checked the tasks using htop command then I found this and as I am increasing the worker request number in the apache2 config file the tasks increase automatically.
I also checked which IP calling so many requests and then I found this:
Access logs file :
I have no idea what is going on here and don't know how to fix it. If anyonw know the solution to this problem then please reply.
Thanks
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 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 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.
I have a droplet on DigitalOcean with SSH key created.
My SSH and SFTP access work perfectly with Mac OSX Terminal and Transmit.
But for some reason SFTP does not work with PHPSTORM :
Error
Connection to 'ipaddress' failed
SSH_MSG_DISCONNECT: 2 Too many authentication failures for root
I had the same problem, after a while looking for ssh keys and others non working ideas I was just using a root user which just could not access to server
The error message was buggy, it appear for ssh issues and also user issues :-(