7 Answers
- Newest
- Most votes
- Most comments
1
Based on your output it appears DNS is working. Have you tried this and used the suggestions to troubleshoot yet? If not I'd give that a shot.
answered a year ago
0
I've already used the tips check the subnets route table and it's correct apparently I'm likely to ping websites meaning I have internet access, I'm only able to use apt-get update
answered a year ago
0
I would check the route table associated with the subnet hosting the instance. You will need a route to either an Internet Gateway or a NAT Gateway in your public subnet.
Relevant content
- asked 2 years ago
- asked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Can you do a curl or wget on an external website over port 80?
This is what was generated using wget
--2023-04-27 16:04:09-- http://www.google.com/ Resolving www.google.com (www.google.com)... 172.253.115.99, 172.253.115.103, 172.253.115.104, ... Connecting to www.google.com (www.google.com)|172.253.115.99|:80...
curl did not generate any results. However, port 80 is included in the input and output security rules for ipv4 and ipv6
Are any NACLs assigned to the subnet? Can you post a screen shot of the SG rules as well as any NACLs?
Follow the requested captures to verify
The SGs and NACLs look as if they should allow your calls. At this point I would boot up another generic Ubuntu in the same subnet with a SG that allows all outbound traffic and see if it can download the patches. If successful, this eliminates any routing and NACL issues and points to SG or something local on the server.