Browsers Not Won't Connect to Web [Solved]

[YnysSci]

I hadn't used my Framework laptop in a couple months, then used the updates available as shown in the system tray recently.

Currently:
Xfce Ver 4.18
Kernal Ver 6.1.0-26-amd-64
Framework 64 with AMD Ryzen 5

The next time I logged in I tried all my browsers but cannot now connect to the internet (including Firefox and Cromite). I have checked my wi-fi and verified it connects.

Has anyone reported this behavior after the upgrade? If not related, any suggestions to get my connection back?

I've already tried turning my firewall off and on but made no difference with either setting.

[Kermit the Frog]

Code: Select all

echo 'nameserver 1.1.1.1' | sudo tee /etc/resolv.conf

Then open any web page right after doing that.
This is temporary (for that session only) to test. In case that works we'll go on to make it permanent.

[YnysSci]

Kermit
I tried the entry exactly as given. It prompted me for my password which I entered. I then displayed "nameserver 1.1.1.1". However my browsers still do not connect.

[DukeComposed]

I tried the entry exactly as given. It prompted me for my password which I entered. I then displayed "nameserver 1.1.1.1". However my browsers still do not connect.

That's what you'd expect from running this command:

Code: Select all

echo 'nameserver 1.1.1.1' | sudo tee /etc/resolv.conf

You can verify that it worked by running "cat /etc/resolv.conf" and confirm it says "nameserver 1.1.1.1". Then test if you can resolve arbitrary FQDNs by trying to run "ping -c 4 www.google.com" or "ping -c 4 www.mxlinux.org". Just as important when changing resolv.conf is that the URL is able to be resolved to an IP address than the ability to actually get a ping from that endpoint.

[YnysSci]

DukeComposed
The cat command gave me another IP address and not the 1.1.1.1 address. I should have stated that I have another laptop running Windows and do not have an issue connecting to the web. I'm using it to reach this forum. I also tried the ping command for mxlinux.org and received "Name or service not known".

[DukeComposed]

The cat command gave me another IP address and not the 1.1.1.1 address. I should have stated that I have another laptop running Windows and do not have an issue connecting to the web. I'm using it to reach this forum. I also tried the ping command for mxlinux.org and received "Name or service not known".

So you didn't update resolv.conf. All the "tee" program does is print its input and write it to a file. In this case one part of that worked (printing "nameserver 1.1.1.1") and the other one (actually editing /etc/resolv.conf) didn't.

Make a backup of your resolv.conf and edit it manually. Something like this.

Code: Select all

$ sudo
Enter sudo password: ******
# whoami
root
# cd /etc
# cp resolv.conf resolv.conf.backup
# cp resolv.conf resolv.conf.new
# featherpad resolv.conf.new

< Replace "nameserver something" with nameserver 1.1.1.1 and save >

# mv resolv.conf.new resolv.conf
# cat resolv.conf
# ping -c 4 www.google.com

[Kermit the Frog]

... The cat command gave me another IP address and not the 1.1.1.1 ...

That's normal if the Network Manager was restarted or if you logged out then in.

[YnysSci]

DukeComposed:
I successfully made the backup/copy of the resolv.conf and the edit you gave. It did confirm I was pointing to 1.1.1.1 with the cat command. However when I tried the "ping -c 4 www.google.com" it responded "ping: www.google.com: Name or service not known". I tried my browsers and still not connecting as well.

Any other suggestions of why my browsers are blocked?

[Kermit the Frog]

What happens if you open a terminal and :

Code: Select all

sudo nala upgrade

?.. Does it do it? Maybe it's not just browsers.

[DukeComposed]

I successfully made the backup/copy of the resolv.conf and the edit you gave. It did confirm I was pointing to 1.1.1.1 with the cat command. However when I tried the "ping -c 4 www.google.com" it responded "ping: www.google.com: Name or service not known". I tried my browsers and still not connecting as well.

It's not your browsers. Let's unpack why we're asking you to edit /etc/resolv.conf in the first place.

Machines don't naturally know what google.com is and there's no way to connect to a Google server without knowing its IP address. So a few decades ago they developed the Domain Name Service which maps IP addresses like 1.1.1.1 to a fully qualified domain name like "one.one.one.one". If the ping command is giving you a "Name or service not known" error it means that this DNS lookup function on your machine is broken.

Every network needs to have a resolving DNS server and you probably have one or two that your ISP controls and it's most likely that those DNS servers are what your Windows machine is using.

The /etc/resolv.conf file on your box is how your machine knows which DNS server to use. "nameserver 1.1.1.1" tells your machine to contact the public DNS server at 1.1.1.1, so even if your ISP's DNS servers are down, or if your machine has messed up how it figures out which servers those are, you can always use 1.1.1.1.

If /etc/resolv.conf contains one line and it's "nameserver 1.1.1.1" and you still can't ping www.google.com, then one of a few things is true: (a) the /etc/resolv.conf file is incorrect or not being used as expected, (b) your machine is not connected to a valid network, (c) DNS lookups to 1.1.1.1 are being administratively blocked on your network, or (d) 1.1.1.1 is down.

(d) is highly improbable. (c) is unlikely unless you or someone else has enabled a packet filter on your LAN to block outbound DNS requests to arbitrary DNS servers. Hotels and airports do this all the time to enforce use of their captive portals. (b) is unlikely, assuming you know what your own home network looks like. That leaves (a), which we can test by removing "nameserver 1.1.1.1" from /etc/resolv.conf and replacing it with the IP address from your Windows machine. You can find your DNS settings in Windows from a command prompt by running "ipconfig /all" and looking for the "DNS Servers" entry or entries.

Using "nameserver 1.1.1.1" is supposed to be easy because it's quick to remember and works just about everywhere. In this case, you want to find the IP address of the DNS servers your Windows system uses, pick one, and put that into /etc/resolv.conf where 1.1.1.1 is. This will eliminate (d) and (c) by using a known good DNS server that one of your functional machines is already using. This will at the very least narrow down the possibilities to (b) you have link-layer network connectivity problems or (a) resolv.conf is busted.