Check if there’s a proxy configured in the system:
set | grep -i -e proxy; \
gsettings list-recursively | sort | grep -i -e org.gnome.system.proxy
Uhm… I did not configure a proxy. Anyway, here is the result:
gsettings list-recursively | sort | grep -i -e org.gnome.system.proxy
org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host ''
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1']
org.gnome.system.proxy mode 'none'
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0
org.gnome.system.proxy use-same-proxy true
1 Like
didnt either
org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host ''
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1']
org.gnome.system.proxy mode 'none'
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0
org.gnome.system.proxy use-same-proxy true
1 Like
Ok, so no proxy. I think I run out of ideas…
1 Like
The only weird thing is this:
It sounds like you have some Chrome policies configured.
Check this URL:
chrome://policy
I just wanted to jump in and say that I’m experiencing the same issue. I have a Dell XPS 13 from early 2019.
This is exactly the same machine I have! Could it be hardware related? Maybe a driver problem?
This is currently the default for Chrome on linux. To disable it I searched for “how to disable your browser is managed by your organization” and the instructions worked on earlier versions of chrome.
On the one installed now [Google Chrome 87.0.4280.66 (Official Build) (64-bit)] it is a bit different. Clicking on the menu link (dots on far right of address bar) I see a management link at the bottom of that menu. Clicking it and takes you to the chrome://management page and following the bread crumbs takes you to the chrome://policy page.
There I see 2 policies that are managed by fedoraproject.org.
I am not sure where those policies came from but they seem to be the only ones there and I certainly don’t mind having fedora project whitelisted.
The continued search however revealed this as a potential fix if you wish that policy disabled.
**NOTE 1:** If you are using **Linux** operating system, all policies applied in Chrome can be found under following folder:
**/etc/opt/chrome/policies**
Delete the above mentioned folder to get rid of the "Managed by your organization" message in Chrome.I’m not sure if my issue is related or not. For myself, the issue occurs with addresses at a remote work location and in conjunction with a split-tunnel VPN. Also, it seems to apply only to Chrome & Firefox browsers. Both claim that they cannot resolve the DNS:
This site can’t be reached Check if there is a typo in my-server.my-office.com. DNS_PROBE_FINISHED_NXDOMAIN
and
Hmm. We’re having trouble finding that site. We can’t connect to the server at my-server.my-office.com.
However I just installed Midori web browser and it can resolve these URLs just fine. Likewise command line tools resolve these addresses fine as well.
My nameservers are listed as expected in /etc/resolv.conf with the office’s nameservers first, followed by public DNS.
I am starting to think that this might not be a DNS issue. I said before that rebooting switched Chrome/Chromium from not working to working, but that’s not exact
Logging out and back in is enough to switch Chrome back to work! How can this happen?
This issue sounds like your internal DNS isn’t being exempted from the trr lookups through DNS over HTTPS. For Firefox in
about:config, make sure you include your internal domains in
network.trr.excluded-domains=
Did you do an update from Fedora 32 or install 33 clean? I did an update and I’m thinking it might be worth trying a clean install.