cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This page is no longer active

close

   

For up-to-date information and comments, search the EE Community or start a new topic.

Some websites unable to load but fine through a VPN

LesleyCr
Investigator
Investigator

Hello,

I have a bit of an odd problem.  There are some websites that I am unable to access through my 4GEE router.  These are not websites that should be content locked (which I have turned off and tested).

I can access these websites if I use a VPN or if I hotspot through my phone.  For example I can't access thepositivebirthcompany.co.uk  My neighbour who also has 4GEE wifi can't access it either.  However I can access it through a VPN.

What is goign on here and can I fix it?
Thanks

15 REPLIES 15
bristolian
Legend
Legend

Hi @LesleyCr 

 

I've tested loading thepositivebirthcompany.co.uk over an EE mobile connection and it loads ok for me. What happens for you?

 

Running a tracert might identify where a hold-up is.

Northerner
Grand Master
Grand Master

Hi @LesleyCr 

 

Have you deactivated content lock?

 

Try logging into your MyEE app then - Settings - Content Lock - change this to off. Then restart your device.

It should now work.

Thanks,

 

 




To contact EE Customer Services dial 150 From your EE mobile or 0800 956 6000 from any other phone. You can call Freephone +44 800 079 8586 on Skype

EE standard opening hours are 8am to 10.30pm every day.

If I put the sim from my router into my phone I can access the site no problem so there must be something happening at the router level thats preventing access.  The connection just times out, every time - it is only an issue when accessing through the router.  I'm sure this won't be the only site I have an issue with too.

Content lock is off - I have tested it.  If I take the sim from my router and put it in my mobile phone I have no issue accessing the site.  This is definitely a router level issue.

Tagging this one for @XRaySpeX who is a lot more knowledgable on the 4G routers.

XRaySpeX
Grand Master
Grand Master

That site is not IPv6 compliant: 

Tested on   Fri, 26 Jun 2020 13:38:36 GMT
AAAA DNS record   no AAAA record
IPv6 web server    
IPv6 DNS server    

This website is not ready for IPv6


It is anticipated that the pool of unutilized IPv4 addresses will be depleted in a short time. This would imply that the Internet would not be able to continue to grow as easily as it has been growing and that it would become more difficult to incorporate new users, devices, services, applications and generally speaking, the innovation in Internet.

The deployment of IPv6 is essential to avoid reaching this situation, and it is the only practical solution to IPv4 exhaustion.

It might be an EE IPv6 issue. EE has introduced IPv6 on its mobile network, but it doesn't fall-back to IPv4 nicely. Can you change the Profile/APN on your EE devices to APN Protocol = IPv4 only?

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC => 2014: EE 20 Meg WBC => 2020: EE 40 Meg FTTC => 2022: EE 80 Meg FTTC (no landline number)

Thanks everyone.


I ran a traceroute to the site in question and this is what it returned.  I'm officially at the limits of my knowledge here so help is appreciated!

traceroute to thepositivebirthcompany.co.uk (198.185.159.144), 64 hops max, 72 byte packets
1 openwrt (192.168.1.1) 3.920 ms 3.688 ms 3.704 ms
2 192.168.225.1 (192.168.225.1) 6.062 ms 5.359 ms 6.106 ms
3 * * *
4 10.248.27.141 (10.248.27.141) 30.119 ms 30.355 ms 31.058 ms
5 10.247.83.171 (10.247.83.171) 28.235 ms 30.958 ms 31.005 ms
6 * * *
7 10.247.83.193 (10.247.83.193) 31.511 ms 27.728 ms 32.334 ms
8 10.247.83.186 (10.247.83.186) 32.717 ms 38.556 ms 29.784 ms
9 87.237.20.108 (87.237.20.108) 30.435 ms 31.397 ms 29.300 ms
10 87.237.20.77 (87.237.20.77) 41.684 ms 45.872 ms 40.191 ms
11 akamai.prolexic.com (195.66.224.31) 36.625 ms 60.669 ms 61.617 ms
12 po110.bs-a.sech-lon2.netarch.akamai.com (72.52.60.192) 39.795 ms 38.882 ms 39.752 ms
13 a72-52-1-137.deploy.static.akamaitechnologies.com (72.52.1.137) 41.384 ms 42.544 ms 40.723 ms
14 ae120.access-a.sech-lon2.netarch.akamai.com (72.52.60.197) 36.484 ms 38.290 ms 41.928 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * 198.185.159.144 (198.185.159.144) 115.126 ms *

Yes, the traceroute is done entirely over IPv4 but it doesn't prove anything.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC => 2014: EE 20 Meg WBC => 2020: EE 40 Meg FTTC => 2022: EE 80 Meg FTTC (no landline number)

Thanks @XRaySpeX  I did this but still having the same issue.  Changed Data connection > connect IP mode to IPV4

(tried to upload a screen shot but its not having it!)