- I have reviewed the upgrade guide and post-upgrade troubleshooting guide
- I have reviewed the board FAQ
- I looked at similar topics before opening this one
I upgraded from F32->F33 last night (Cinnamon DE), and now various system apps are having trouble with internet connectivity.
- I am no longer able to connect to my VPN provider via the Network Manager. The VPN Type is a pre-made OVPN file. When I turn it on, it just stalls at “Connecting”.*
- I cannot check for updates, neither via Gnome Software nor
dnf update. The former just spins during “Refreshing”, the latter gets stuck at 0% on the progress bar that displays while checking the various repos. It never times out, however, and I have to break out of it via Ctrl+C or Ctrl+\ to make it stop.
- Firefox will not load any page. Again, it does not throw an error like it would if I tried opening a page with WiFi off, it simply stalls infinitely while trying to do the domain lookup.
Not all programs are having this problem. HexChat, Thunderbird, and even Falkon seem to work fine, and on Falkon I can load the same URLs that Firefox is failing to load. I was able to get Firefox to work agains by enabling DNS over HTTPS in the settings, which is just throwing the effort onto a third-party provider, from what I understand; so it’s not really a permanent fix.
Troubleshooting So Far
*Here is what I see regarding the VPN when I try to connect and then run
Jan 17 13:16:53 malebolge nm-openvpn: RESOLVE: Cannot resolve host address: VPNDOMAIN.com: (Name or service not known)
systemd-resolvd is running:
[admin@malebolge ~]$ systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-01-16 22:59:33 EST; 15h ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1259 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 9375) Memory: 15.3M CPU: 2.004s CGroup: /system.slice/systemd-resolved.service └─1259 /usr/lib/systemd/systemd-resolved Jan 16 22:59:33 malebolge systemd: Starting Network Name Resolution... Jan 16 22:59:33 malebolge systemd-resolved: Positive Trust Anchors: Jan 16 22:59:33 malebolge systemd-resolved: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jan 16 22:59:33 malebolge systemd-resolved: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.> Jan 16 22:59:33 malebolge systemd-resolved: Using system hostname 'malebolge'. Jan 16 22:59:33 malebolge systemd: Started Network Name Resolution.
resolvectl seems to be able to query:
[admin@malebolge ~]$ resolvectl query fedoraproject.org fedoraproject.org: 2605:bc80:3010:600:dead:beef:cafe:fed9 -- link: wlp2s0 2605:bc80:3010:600:dead:beef:cafe:feda -- link: wlp2s0 2604:1580:fe00:0:dead:beef:cafe:fed1 -- link: wlp2s0 2620:52:3:1:dead:beef:cafe:fed6 -- link: wlp2s0 2610:28:3090:3001:dead:beef:cafe:fed3 -- link: wlp2s0 2620:52:3:1:dead:beef:cafe:fed7 -- link: wlp2s0 220.127.116.11 -- link: wlp2s0 18.104.22.168 -- link: wlp2s0 22.214.171.124 -- link: wlp2s0 126.96.36.199 -- link: wlp2s0 188.8.131.52 -- link: wlp2s0 184.108.40.206 -- link: wlp2s0 220.127.116.11 -- link: wlp2s0 18.104.22.168 -- link: wlp2s0 22.214.171.124 -- link: wlp2s0 126.96.36.199 -- link: wlp2s0 -- Information acquired via protocol DNS in 15.7ms. -- Data is authenticated: no [admin@malebolge ~]$ resolvectl dns Global: Link 2 (wlp2s0): 10.0.0.1
10.0.0.1 is the correct IP to hit my router.
[admin@malebolge ~]$ resolvectl domain Global: Link 2 (wlp2s0): ~.
I can’t tell from the above command if I’m literally supposed to put “domain” in there or substitute a domain, e.g.
Finally, resolve.conf looks correct for systemd-resolve (based on my googling, anyway):
[admin@malebolge ~]$ ls -l /etc/resolv.conf lrwxrwxrwx. 1 root root 39 Jan 16 22:00 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf [admin@malebolge ~]$ tail /etc/resolv.conf # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad
With a working browser and e-mail client, I can still get work done, but I still want to get this resolved as soon as possible, as it would be hazardous if I am unable to update my system any further. I’m looking for further troubleshooting advice. I don’t know enough about DNF to be able to post relevant logs here to demonstrate the updating problem, but I’ll follow any commands provided.
Thank-you in advance!