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.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I want to allow access to the admin panel hosted in AWS ec2 only through a specific port like http://65.0.177.9:49555/,I have tried in the security group to set the port range but not successful
At server level, there is Security Group, but assuming you use VPC, there is also Network Access Control which might be blocking such exotic port.
Please also remember to open whichever web server is running on that server to accept connections on that port.
And finally, make sure local firewall is not blocking it.
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 4 years ago.
Improve this question
On my backend instance a service is running which has to accept multiple connection in a second but TCP LB is not allowing multiple connection at a time.
Please help me to increase LB connection to max.
Where did you get the information it only allow one connection at time?
The Network Load Balancer (Also known as TCP load balancer) allows you to balance load of your systems based on incoming IP protocol data, such as address, port, and protocol type. As long as your instance services has resources to handle the request, the load balancer will redirect the traffic.
You can read more about it in this oficial document form Google.
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 8 years ago.
Improve this question
For experimentation purposes, I’m trying to setup an AWS EC2 inside a VPC that has both public and private subnets as described in this tutorial.
However, when I try to SSH in step #2, it fails (Operation times out. Connection failure):
$ ssh -i MyKeyFile.pem ec2-user#XXX.XXX.XXX.XXX
ssh: connect to host XXX.XXX.XXX.XXX port 22: Operation timed out
and:
$ telnet XXX.XXX.XXX.XXX 22
Trying XXX.XXX.XXX.XXX...
telnet: connect to address XXX.XXX.XXX.XXX: Operation timed out
telnet: Unable to connect to remote host
Can someone explain what I'm doing wrong? Why cannot I connect to this NAT EC2 as described in the tutorial? It seems like it should be simple
There are several factors stopping you to do an SSH into NAT instance - please check the following items.
Internet Gateway is attached and is added in the route table of the Subnet ( or Main Route table )
Check if the NAT's security group is open to your local on Premises ( for simplicity try with 0.0.0.0/0 )
Is Elastic IP is attached to the NAT instance - to established communication to / via. NAT
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.