TLDR; something is blocking some (but not all) flatpak connections to the internet, I dont know how to diagnose.
Since a couple of weeks ago I have been experiencing this problem and it is a strange one. I am not sure if it is silverblue, flatpak or the apps.
Platform: Fedora SIlverblue 34 (pre-release)
In flatpaked web browsers (edge, Firefox from Flathub) I cannot access certain urls such as https://www.bbc.co.uk and others seem to be missing some stylesheets (I havent checked but I suspect from CDN’s).
I get a server not found error.
For the normal firefox that is part of silverblue, the same urls work.
I have no proxy and AFAIK no non default settings that would involve connections.
How do I even go about trying to figure out where the problem lies?
EDIT - just checked flatpaked ungoogled-chromium and beta chrome, both display bbc.co.uk but with incomplete style sheets.
Yeah, a few of us on the Cockpit team who are using the Firefox flatpak on F34 beta Silverblue noticed the same issue. It looks like it’s related to the split-dns of Fedora?
That’s why some sites don’t work, and others have broken CSS (due to having CSS and/or JS hosted from another site).
A workaround, for the time being, is to enable DoH (DNS over HTTPS) in Firefox. Hopefully they fix this soon, as I don’t want to use Cloludflare, but my own pi-hole DNS server at home.
Note: It’s most obvious in Firefox in a Flatpak, but I’m also seeing the same issue with the Epiphany Technology Preview as a Flatpak too. (The difference is that Firefox has the DoH workaround, so it’s possible to keep using it by changing the DNS server it uses.)
(Not sure where the bug is, but it’s not in Firefox, as Epiphany is also affected, so it must be in Flatpak or systemd-resolved or how they talk to each other).
Note: This isn’t Silverblue-specific. I upgraded my personal laptop to F34 beta too, and (unlike my work laptop) it’s not (yet) running Silverblue (due to a Silverblue installation bug).
This moves the old symlink from systemd’s @ ../run/systemd/resolve/stub-resolv.conf to networkmanager’s @ ../run/NetworkManager/resolv.conf and then restarts your network to make it active.
Be sure to do the symbolic link relatively like this, else it may otherwise break toolbox/podman containers.
To reset to normal, remove the resolve.conf file and move the resolve.conf-old back to resolve.conf… then restart network again.