By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

443... failed: No route to host.

0

I'm encountering the following error. Any suggestions on how to resolve this would be greatly appreciated. Thank you

❯ wget https://stage.argocd.ppp.com --2024-03-08 16:47:22-- https://stage.argocd.com/ Resolving stage.argocd.ppp.com (stage.argocd.com)... 10.12.xx.224, 10.ww.ww.151, 10.ww.ww.104 Connecting to stage.argocd.com (stage.argocd.yy.com)|10.yy.yy.224|:443 (tcp) failed: No route to host

  • Gary Mclean EXPERT
    2 months ago

    Not enough information in your question. Where is stage. What setup do you have. Where are you testing this from etc. To help assist information about your setup would really help.

Topics
Security, Identity, & ComplianceNetworking & Content DeliveryContainers
Tags
AWS Network FirewallApplication Load BalancerNetwork Load BalancerAWS Virtual Private Network (VPN)Amazon EKS Anywhere
Language
English
reppakayala
asked 2 months ago297 views
1 Answer
0

Where are these IP addresses coming from?All 10.0.0.0/8 IPv4 address ranges are private and not publicly routable on the internet.

Are these the IPs of other resources in a VPC? Are they hardcoded into the /etc/hosts file on the host on which you're running wget?

When I lookup stage.argocd.com I get 103.224.212.214

profile picture
EXPERT
Steve_M
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content