I am on a computer running a newly installed Debian 11 that is connected to Ethernet. When I try to ping a Web site that uses HTTPS, or load it with w3m, it just loads forever. However, when I use ping or w3m to connect to Web sites that use HTTP, it works (only some HTTP Web sites seem to work though, and the only ones that I have been able to connect to are wa.gov and motherfuckingwebsite.com). Also, when I ping the IP address of any Web site, regardless of whether it uses HTTP or HTTPS, I actually get a response, which seems to indicate that this may be a problem with the DNS.

Here is my /etc/resolv.conf file (I modified this file a lot trying to fix the problem, right now it's using a Quad9 DNS server. I also don't know if my router's IP address should be in this file, but it was there originally and removing it did not fix the problem)

what you are trying to do is have a nameserver to your router and your router is where you put the DNS ips.

see
https://support.quad9.net/hc/en-us/a...20-3-Cinnamon-

so I think resolv.conf should read the gateway to your router....not sure if yours is correct as you have not named your router
I have a dlink so mine is
then login to your router
dlink is http://192.168.1.1/page/login/login.html

then find your DNS settings for me its Internet -> primary and secondary DNS settings
copy and paste the correct ips, without "nameserver" into those boxes and save

1 members found this post helpful.

Just use dig to make sure the nameserver works:

dig @192.168.1.1 -t a www.google.com

and so forth. If it doesn't respond, there isn't a nameserver at the ip.

You can use curl or wget to test the https (less overhead), to debug it. I suspect it might be an SSL or CA problem is https does not work. Just "curl https://www.google.com" and see the output.

I couldn't get anything to work, so I reinstalled Debian with the "standard system utilities" (it was already a fresh install of Debian, so reinstalling it didn't really have any consequences), and now everything works fine.