3 Answers
- Newest
- Most votes
- Most comments
0
Hi,
If it seems good to you, I leave you some questions to collect more information about your problem and thus be able to give you a solution.
- Is this new EC2 deployed in the same VPC and subnet as the rest of EC2 that works correctly?
- If not, does the VPC have an Internet Gateway attached that allows access to the Internet?
- In case the subnet is public, does it have route table that directs internet-bound traffic to the internet gateway?
- In case the subnet is private, does it subnet have route table that directs internet-bound traffic to a NAT gateway located at the public subnet?
0
Is port 80 ever blocked in network ACLs?
I want to make sure that port 80 is not blocked first, since the repository access via http is timing out.
Looking at the settings in the image, it looks fine. What about going through a proxy server as another way to deal with the problem? If I create one proxy server such as squid on EC2 and apt update via proxy, will it succeed? http://www.squid-cache.org/Doc/
The apt update proxy should be configured as follows.export http_proxy=http://EC2 Proxy Server IP:3128 export https_proxy=http://EC2 Proxy Server IP:3128 sudo apt update -y -o Acquire::http::Proxy=$http_proxy -o Acquire::https::Proxy=$https_proxy
Relevant content
- asked 3 years ago
- asked 3 years ago
Found the issue, the instance was deployed on a public subnet but it didn't get any ip address for some reason. But now it work when it has bin assigned a ip. Thanks all for the help.