I am trying to connect to an instance(elastic search) deployed on aws from azure and randomly the connection is timed out.
I tried to curl the same instance(aws instance) from other aws instance and even from my local machine and its returning result just fine.
I am not sure what exactly is the issue in case of azure.
Earlier I thought it was the issue of heap memory, so increased it. For sometime it worked fine but has again started troubling me just the azure
Related
I launched an EC2 instance on Amazon Web Services and want to deploy Confluence on a Ubuntu 18.04 Server. Almost everything is set up now.
I just need the last step:
I need to call http://{ec2-public-ip}:8090 from my browser to do the last steps of configuration of Confluence via the frontend, as described in the instructions of Confluence (https://confluence.atlassian.com/doc/installing-confluence-on-linux-143556824.html).
I don't have any issues with connecting to the EC2 instance via ssh in terminal (macOS) as ubuntu and also as root by using privateKey.pem. This works fine. Installation of Confluence and setting up a MySql DB were also successful. EC2 instance is running. Getting a connection via AWS Session Manager also works, but opens a terminal in my browser and if I ping the EC2 instance via the AWS Session Manager, there is a 100% packet loss. Via local terminal on my mac there is 0% packet loss.
Also calling http://{ec2-public-ip}:8090 via browser causes ERR_CONNECTION_REFUSED in Safari, Chrome, IE and Firefox.
What I already tried:
Security Groups (All Traffic, MyIP); also tried to allow Any Traffic
Firewall completely off; Proxy completely off
Opened all necessary Ports in my Network (8090, 8000, 22, 23)
Emptied Browser Cache
Flushed DNS; new IP; rebooted router; rebooted EC2 instance
Does anybody have an idea how to solve this problem? I know that there have been a few discussion about this topic, but none of those comments or solutions worked.
I chose a different Port as selected by Confluence. This worked immediately.
The packet loss was caused by the already assigned HTTP Port 80, although Confluence uses 8090 by default. When I pinged the server, all of my packets have been delivered, while all incoming packets went to a different device in my Network. As result my Terminal told me, that no packet was delivered to my Mac. Which was obviously true.
Now everything is up and running just fine.
I saw that a lot of people in the Internet had the same problem. Just try it again but choose different Ports while installing Confluence on your Server.
So in Google Cloud Platform, I'm setting up a staging server for my job -- I'm not really a dev ops person so I'm not fully sure what happened here but:
I created a snapshot of the production server
I created a server out of the snapshot that I took
I set up SSH using a new key on my local computer, and the ssh connection works to staging
Checked the external IP to see if the site was loading and it was! Everything was working correctly.
Here's where I think I fucked up but I don't fully understand why or how to fix it:
I deleted the snapshot, and now the external IP doesn't point to anything at all! BUT my ssh connection from local to the server still works! So the server is still up but why can't I access it any more via browser? I'm very confused.
I assumed that since I made a server out of the snapshot, the snapshot's contents were now copied into the new server instance that I created, and I didn't want to be paying for both the new server and the snapshot. Content-wise that seems to be correct since I can still ssh into the correct IP address, but why can't I access via browser?
Should I create a new snapshot and make another server from scratch for my staging site? Is there a way to undo the deletion of the snapshot that I deleted? Or is this totally unrelated, and is it a total coincidence that the browser-access of the site via IP went down like within seconds that i deleted the snapshot? And why the heck is the ssh connection still working totally fine when I connect via terminal locally?
Please help!
Thanks :)
UGH I figured it out (mostly) -- Turned out that SOMEHOW HTTP and HTTPS connections became disabled for the server. I still have no idea how as i was making http connections right before i deleted the snapshot. Does deleting snapshots that a server is based on edit server settings????
I am running Bitnami WordPress on AWS server website working since two days but suddenly it stop showing anything and connection timeout is showing. The instance EC2 is running perfectly fine, and I have also seen IP logs, and nothing suspicious has come up.
Based on the above comments I guess the issue is with the internal web server
Make sure that the web server is running perfectly fine. And I do not mean just checking the EC2 instance state, because it is possible that the EC2 instance is running but the web server is down, causing the issue
I have a mysql server hosted by AWS RDS, which is intermittently uncontactable. I've been doing a lot of development today on a page that, although hosted locally, executes a query against the remote server on each page load, and I've discovered that every few minutes, I suddenly can't reach the server - it only lasts for a few seconds, but during that time I get the error SQLSTATE[HY000] [2003] Can't connect to MySQL server from any attempt to reach it.
Existing, already open connections (i.e. from the command line client) are not affected, and can run queries as normal. It's only establishing a new connection that is impossible.
Why does this happen? How can I track down the cause?
You might be using a instance type too small, t1.micro and t2 instances can show that behavior sometimes. What instance-type are you using?
Your CPU capacity might be throttled, and that could be the reason you see intermittent performance.
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.