There are a lot of possible tests to troubleshoot this. My concern is that we're now two pages into a solved thread with no diagnostic information beyond a QSI. The site can be "accessed". Does that mean it loads in a browser? What does it mean when that site cannot be "accessed"? Are there error messages? What do they say? What does a traceroute look like? What are the responses from the DNS resolvers? Is there a transparent bridging situation at play here? Have you configured any kind of HTTP or SOCKS proxy? The list goes on.FullScale4Me wrote: Sun Feb 18, 2024 8:17 pm This sounds more like the browser headers returned to the webserver are being evaluated against a local block list.
With a few 10s of years of website building experience, this does NOT sound like any ISP interference. Banking sites do this all the time. They are usually more polite about it and ask you to use a different browser and/or OS. Not an MX 21 issue IMHO.
A possible good test would be to install the same version of web browser as used on MX 19 on MX 21.
There are an incredible number of changes between Debian releases, and many more MX changes on top of those. "Why does one system work and the other doesn't?" is not a fair question to ask if you can't or won't provide details that explain the situation. Without concrete definitions of what "works" and "doesn't work", we're left with speculation.