Currently my internet provider is Lebara, in UK.
Previous days internet seemed to work just fine.
Today I’ve been having a recurring issue which affects both laptops and smartphones connected to the WiFi (fwiw, I don’t have a wired connection, nor an ethernet cable to try connect via that to the router), where I can access some sites but not others, and I see absolutely no commonality between the two categories. See below for a few examples.
I say “recurring” in the sense that when it happens, I can just disconnect my laptop from the WiFi, connect it to, say, the smartphone’s data connection, and then back to the WiFi, and the issue is gone. I’ve just performed once more this manouver successfully. I haven’t tried yet with disconnecing the smartphone from the WiFi and reconnecting to it afterwards without intervening on the laptop.
I am “guilty” of levity in the following senses:
- playing around with the settings of the modem, but only to the extent you can see at this previous question of mine, i.e. only to attempt setting port forwarding;
- updating the firmware of the router, which is a TP-Link Archer MR600.
Maybe some of this might have had some nasty effect I don’t understand.
Here’s a few examples of sites I can access to:
- https://superuser.com/ (indeed, I’ve just asked this question), https://stackoverflow.com/, and other sites of this network,
- https://www.facebook.com/
- https://www.google.com/
- https://www.google.co.uk/imghp?hl=en&tab=wi&ogbl
- https://keep.google.com/u/0/
- https://github.com/
- https://codeberg.org/Aster89
- https://bank.barclays.co.uk/olb/authlogin/loginAppContainer.do#/authentication
- https://www.deviantart.com/aster1989
- https://www.tesco.com/
and sites I can’t access to:
- https://bbs.archlinux.org/
- https://wiki.archlinux.org/
- https://hoogle.haskell.org/
- https://www.hackerrank.com/dashboard
- https://asciinema.org/
In the latter case, after quite a few seconds (minutes?) I get this error
This site can’t be reached
hoogle.haskell.org’s server IP address could not be found.
Try:
Checking the connection
Checking the proxy, firewall and DNS configuration
ERR_NAME_NOT_RESOLVED
