Vodacom is gaslighting me

T

Trowalts

New Member
Joined
Mar 31, 2015
Messages
5
Reaction score
0
So there are two sites I cannot access (as of today) when using Vodacom as my ISP:
  • login.tailscale.com
  • <fqdn for a server I use at work> (I'll refer to it as my.work.server in the post as an example)

DNS is not a problem; I can resolve their IP addresses. Connecting to port 80 results in a 502 response.
Connecting to 443 just fails, no connection/filtered.

I've replicated this with 3 different SIM cards from Vodacom
* My phone (Vodacom contract - business)
* 4G Router with home internet contract
* A different 4G router with a pre-paid SIM card

I've also tried accessing these sites from 2 Macbooks, a Desktop and my phone. None of these permutations works.
What I find particularly concerning is that Vodacom is blocking my work server, as this is a dedicated instance in AWS that I use daily and is not used by anyone else. It's not like login.tailscale.com, which is used by thousands; this work server is just me. How did this get on their ban hammer send packets to /dev/null radar, and why?

I've switched everything off and on.
When I use a VPN (obviously not Tailscale), I can connect without issues to both sites.

I've contacted Vodacom support, they checked the APN and nothing is blocked (didn't figure it would be that, but at least that's shortened the next support call).
I gave Vodacom support the two sites; they also could not access them (they weren't down, I was connected to them via a VPN during the call)

I'm asking for help, but mostly I'm asking, WHY???
 
Rickster said:
Don't use Vodakak?
Click to expand...
Yar yar, sadly not many options by me. In the sticks, there's a Vodacom tower about 300m from my place, other operators seem to get throttled badly when they piggyback off said tower. Though if it's my only option then it I'll have to get another SIM, any ISPs that Vodacom play nice with when using their infra?
 
Do you still have a support ticket open at least?
Seems like you'll have to follow up until it reaches someone that can fix it on their side.
 
Are you Vodacom's network itself on a WISP's APN?

If you traceroute what do you get? Or tcptraceroute to the SSL port is it falling off the bus somewhere?
 
Trowalts said:
So there are two sites I cannot access (as of today) when using Vodacom as my ISP:
  • login.tailscale.com
  • <fqdn for a server I use at work> (I'll refer to it as my.work.server in the post as an example)

DNS is not a problem; I can resolve their IP addresses. Connecting to port 80 results in a 502 response.
Connecting to 443 just fails, no connection/filtered.

I've replicated this with 3 different SIM cards from Vodacom
* My phone (Vodacom contract - business)
* 4G Router with home internet contract
* A different 4G router with a pre-paid SIM card

I've also tried accessing these sites from 2 Macbooks, a Desktop and my phone. None of these permutations works.
What I find particularly concerning is that Vodacom is blocking my work server, as this is a dedicated instance in AWS that I use daily and is not used by anyone else. It's not like login.tailscale.com, which is used by thousands; this work server is just me. How did this get on their ban hammer send packets to /dev/null radar, and why?

I've switched everything off and on.
When I use a VPN (obviously not Tailscale), I can connect without issues to both sites.

I've contacted Vodacom support, they checked the APN and nothing is blocked (didn't figure it would be that, but at least that's shortened the next support call).
I gave Vodacom support the two sites; they also could not access them (they weren't down, I was connected to them via a VPN during the call)

I'm asking for help, but mostly I'm asking, WHY???
Click to expand...
It's perfectly fine at my end. I had a similar issue with a different site (private), changing the DNS helped. So, try a custom DNS from Mulvad, Quad 9, or some other provider.
 
I have a same situation, a domain seems blocked on the Vodacom network..It works on other ISPs .I have tried different VodaSIMs, DNS and devices as well but same outcome
 
Routing can be an issue also.

If tracert isn't getting all the way to the expected endpoint... as a test you could try install WARP (go to 1.1.1.1 in your browser) turn it on and select the DNS and WARP option

1763193184557.png

If it's routing this could help. We've had numerous people getting very high ping to local game servers because their routing was whacky for some reason and this is faster than taking a number and getting in line at your ISP.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X