New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
VPS pings but doest downloads any files through wget / yum
I got a vps from a provider
and when i do this :
wget -p -k http://google.com
i get :
--2016-07-30 01:11:33-- http://google.com/
Resolving google.com... 173.194.122.233, 173.194.122.238, 173.194.122.228, ...
Connecting to google.com|173.194.122.233|:80...
and it times out.
I tried clearing the repo and checked the resolvers. All seems Ok. Any idea what's wrong with this ?
Comments
Have you checked your firewall configuration? Ping uses icmp protocol and download uses tcp.
Yes probably you have to check firewall configuration
Firewall is disabled.
Checked that 10 times.
run a traceroute or mtr to google.com
Also what does route -n show?
FYI,
routeis deprecated and has been replaced byip routein most Linux systems, your command translates toip route listLearning something new everyday, thanks for the info
Anyone ?
Still haven't pasted the results of
ip route list, have you?what do you get for yum update?
what would the result of
mtr google.comortraceroute google.comortracepath google.combe ?http://prntscr.com/bzhett
Tracert :
Since your yum issue is when it goes over IPv6, can you do
traceroute6 ipv6.google.com, please ?Also
ip -6 routewould be useful.Most VPS have eth1 as the private LAN so you probably want to confirm things are on the right interface.
Francisco
what would be your resolv.conf?
I have disabled ipv6 but still same problem.
Already did that. No luck.
It's set to google's resolver's.
@Caater when you disabled v6, just to confirm, it now resolved to v4 only, with precisely the same error ?
Yep same error on v4. Connection timed out.
For me it looks like there is something blocking connectivity for your IPs for specific ports or protocols only. I'd bet it might be ACLing on provider's end, or a provider to your provider's end.
Technically you have the connectivity. ICMP comes through, so routing must be ok. You can reach the very destination with tracert, with no apparent issues on the way. At the same time you're saying you have no sort of firewall enabled on this machine (just to make sure, have you done iptables -F INPUT iptables -F OUTPUT, and iptables -L shows you default policy as ACCEPT?) there is not much you can do really, maybe with exception of wiretapping your own traffic with tcpdump and looking what you get back on that level.
You could also run a tcptraceroute to see where exactly it gets stuck, but I don't know if you'll have much luck installing it when your connectivity is in this state. It's by no means a default system utility.
It looks like a problem that has to be raised with support so they can check their network.
Out of curiosity, is that a new server ? How did it happened ?
straceyour wget command and check which system call it blocks on.Is your host-name mapped to loop-back in your hosts file in etc?
EDIT: Cl0udFl@re sucks
Any proxy configured in /etc/wgetrc?
MTU issue? Whats the max size you can ping with ?
I had a similar issue once with a VPS at HVH and i tried all the tricks including reinstalling OS but no success i wasn't even able to use yum update and always had connection time out/fail and in the end i came to know the issue was at provider end. Changing the node fixed the issue.
Hello,
Maybe you're filtered outside your VPS ? If you have nmap can you run :
nmap -p 80 any_webserver_ip