Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have recently signed up for the Amazon Web Service Free Tier and started an EC2 instance. I installed Nginx on this server and started the service. The problem is that whenever I try to navigate to the public DNS provided by Amazon's EC2 Management Console, I receive "This page can't be displayed".
I have added a new security group within the EC2 Management Console providing access to port 80, 22, and 443 (to 0.0.0.0/0).
I have verified nginx is running by
ps -ef | grep nginx
and it returned
I verified it is listening on port 80 by running
netstat -pant | grep :80
and it returned
I verified the default site is enabled in the .conf file and contains the "Welcome to Nginx" message.
Any ideas what could be blocking the site?
Turns out I did not need to create a new security group. I had to edit an existing one, opening the HTTP port. I'm not sure what the security group I created did, but it's gone now.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am doing Team Project about Web Server and streaming.
One of my team member has created Instance, and I want to use that instance.
He and I are both IAM user.
But when I tried to use SSH connect by PUTTY, there was an error:
no supported authentication methods available (server sent publickey)
Is it because trying to access with my IAM account, but the owner of that instance is my team member? How can I connect his AWS EC2 instance with my account (using PUTTY)?
Thank you.
This error is similar like setting up AWS SSH for the first time, possible problems?
Incorrect .ppk file, Wrong username, Wrong IP.
Also check permission of your pem file
/folder/ec2-user/ - 700
/folder/ec2-user/.ssh/ -600
/folder/ec2-user/.ssh/authorized_keys - 600
This post may answer your question https://stackoverflow.com/a/46112210/13126651
if it doesnt
First of all make sure your security group attached to Ec2-instace allows inbound connection to ssh on port 22
the usual default username in EC2 for these Linux distro:
Amazon Linux: ec2-user
Ubuntu: ubuntu
Debian : admin
then, if you are using :
Windows - get PEM key from AWS website and generate PPK file using PuttyGen. Then use Putty to use the PPK (select it using left-column: Connection->SSH->Auth: Private key for authorization)
for Linux
Linux - run: ssh -i your-ssh-key.pem login#IP-or-DNS
there is one more sleek method to connect to your instance which doesn't require any pem file from your end since authentication key is stored on was side
To access the instance through a browser, make sure you add a rule in your security group to allow port 80 and port 443 inbound.
under your instance, you can see connect, click on it and select connect using the browser
Aws doc for troubleshooting, this error check this
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I accidentally disabled the public checkbox on port 3389 in the Windows Firewall system on my RDP. I can't connect my RDP, but I've added public access in AWS security group for the port.
Can you please let me know on how to enable the port on windows firewall and connect to my RDP?
I have solved my problem and now I can connect my RDP.
Step to reproduces
1. Logged on AWS and goto SSM
2. Run a Command
3. Disable firewall (Because I have disabled my public port in Firewall)
4. Connect my RDP (It's working without a firewall - Firewall status is False)
5. Logged on my RDP and enabled the public port after that will enable the firewall again.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have some EC2 instances running an express application listening on port 3000. I then have an elastic load balancer forwarding request from it's port 80 to these EC2 instances. Every time I bring down one of the express servers running on an EC2 instance and try to bring it back up I get the address in use error for port 3000. I can not find any actual process using this port (lsof, netstat, etc) is ELB still connected on port 3000 ? If so what is the workflow to restart applications behind ELB ?
Take a look at "Connection Draining" and either disable it or reduce the time.
It sounds like the process isn't exiting until all connections have closed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have application deployed on tomcat server on machine A,B,C,D
I want to load balance using the Nginx using two load balancer nodes LB1 & LB2.
All configuration I got is using only one node as load balancer.
is it possible using Nginx.
If we have a critical application running on server require the zero down time. If we go with one LB and for some reason LB itself fails,then there will be an issue.
We have this set up initially using AWS Load balancer, but recently we start using the websockets. The web sockets are not working correctly on EC2 load balancer.
if some one has better option please suggest.
Use Amazon ELB and forward TCP:80/443 instead of HTTP:80/443
The only downside of balancing TCP is that your appservers have to deliver SSL certificates themselves if you use HTTPS.
If you want to run the loadbalancer yourself without having a single point of failure you can use haproxy to fall back to a standby machine when the primary balancer fails.
http://www.loadbalancer.org/blog/transparent-load-balancing-with-haproxy-on-amazon-ec2
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I will make an array of Varnish servers using Amazon Auto Scaling. With that, I'll have to send a purge request to all servers that are as healthy on the load balancer.
It is possible? What is the easiest way to do? Should I use API?
That's fairly straightforward using awscli / API.
Get healthy instance IDs from ELB using aws elb describe-instance-health. Lots of examples here: AWS CLI - elb describe-instance-health
Get IP addresses of your healthy instances by using aws ec2 describe-instances. Docs here: AWS CLI - ec2 describe-instances
Once you have IP addresses just do what is needed on your EC2 instances (make sure your security groups are set up properly).