topic Re: ERR_ADDRESS_UNREACHABLE in Network

ERR_ADDRESS_UNREACHABLE

Pivic — Tue, 19 Sep 2023 10:32:22 GMT

Hi,

For a few weeks now I have been having issues accessing certain websites when on mobile data.

I'm getting the error "ERR_ADDRESS_UNREACHABLE" or "ERR_TIMED_OUT". But the websites work fine when I use WiFi or VPN with mobile data.

I tried to reset the APN, clear browser data, tried other browsers... to no avail..

How can I fix this? Is the problem coming from Three?

Thanks,

Re: ERR_ADDRESS_UNREACHABLE

JonathanB — Fri, 22 Sep 2023 16:50:15 GMT

Hi @Pivic,

Is the issue a constant one, or does it happen randomly/intermittently? Are you able to confirm if anyone else is having the same issue when connecting to these sites from Three?

We'll need to know what websites we're discussing to look into this further and confirm if there's a general issue on the network.

Thanks,
Jonathan

Re: ERR_ADDRESS_UNREACHABLE

Pivic — Tue, 26 Sep 2023 14:02:22 GMT

Hi Jonathan,

Thank you for looking into it. Someone else on Three has the same issue as me. It is constant.

One example of a website that doesn't load is: http://www.hughleoncontrols.co.uk/

Thanks,

Re: ERR_ADDRESS_UNREACHABLE

JonathanB — Wed, 27 Sep 2023 13:58:42 GMT

Hey @Pivic,

I've tried this from a Three connection over 4G just now and it can connect okay. Is this still persisting now?

The error could be down to network congestion if the request is timing out. Are you trying from multiple locations, and anything showing on our Network Status Checker to say we're experiencing issues?

If your phone/coverage allows you to test, I'd try checking if the issue is specifically over 3/4/5G too?

Thanks,
Jonathan

Re: ERR_ADDRESS_UNREACHABLE

Pivic — Wed, 04 Oct 2023 08:46:24 GMT

Hi Jonathan,

Thanks for the tips!

I can never access that website on my mobile data. And this has been consistent for a few months. At different locations in the UK.

I have now tried what you advised! I changed to "3G/2G (autoconnect)" and everything works!

The website doesn't work on 5G/4G autoconnect though

Because I can never access the website on 5G or 4G it doesn't sound like a congestion problem.

The network status checker returns no problem.

Any idea?

Thanks!

Re: ERR_ADDRESS_UNREACHABLE

JonathanB — Fri, 03 Nov 2023 17:02:47 GMT

Hey @Pivic,

Have you seen any improvement with this in the meantime, or is it still only connecting over 3G? has popped up on the community recently. Do you think it seems similar to that issue? Does the page load on 4/5G if you try refreshing a couple of times?

Thanks,
Jonathan

Re: ERR_ADDRESS_UNREACHABLE

pivic1 — Sat, 15 Jun 2024 08:30:46 GMT

Hi Jonathan,

Sorry for the late reply, i didn't see your post!

I still have the same issues. Everytime I want to load a certain website, I need to go on 2G/3G, or Wifi.

The 4G and 5G will not allow me to load the website that I mentioned above. It gives me ERR_TIMED_OUT. I tried in different places in the UK, always the same behaviour.

Thanks,
Alex

Re: ERR_ADDRESS_UNREACHABLE

PeteG — Sun, 16 Jun 2024 15:20:30 GMT

Hello.

In my checking, it looks like the page that was provided as an example is having an issue with IPV6 enabled.

To confirm, could you please go into your phone APN settings and create a new APN with the APN restricted to IPV4 only?

The APN can be named anything, and the only settings you'll need to put in are to set the APN to three.co.uk then go down to APN Protocol and set that to IPV4.

Could you test the website that was linked above with and without the change, and then if you have any other websites where you were having the issues, could you test those and let us know if those are working as well?

Pete.

Re: ERR_ADDRESS_UNREACHABLE

pivic1 — Tue, 18 Jun 2024 17:03:01 GMT

Hi Pete,

Thank you!

I tried it and it fixed it! It works perfectly with the APN set as IPV4!

Thank you!!

Re: ERR_ADDRESS_UNREACHABLE

JonathanB — Wed, 19 Jun 2024 09:00:26 GMT

Hi @pivic1,

That's fantastic news! I've marked Pete's response as a solution, in case it goes on to help anyone else out down the line. 🙂

Thanks for bearing with us on this issue, and coming back to confirm the solution worked for you.

Thanks,
Jonathan