I’m trying to get Konqueror to connect to my proxy as I’ve already done for Vivaldi. It was easy enough with Vivaldi as it’s Chrome based and just needs the --proxy-server flag enabled:
I noticed that Konqueror seems to have its own Proxy Server settings, yet whenever I set these in the Settings, Konqueror never actually connects to the proxy server:
Any advice on how to get Konqueror to connect to the proxy server?
A couple of things are worth checking before assuming the proxy configuration dialog is broken.
First, which Konqueror backend are you using? Modern Konqueror can use either KHTML/KIO components or QtWebEngine-based components. If you’re using WebEnginePart, the proxy behavior is different because QtWebEngine does not always honor KDE’s KIO proxy settings. In fact, KDE developers and users have repeatedly noted that many QtWebEngine/Chromium-derived applications ignore KIO proxy configuration and instead rely on their own proxy handling.
Second, verify that the SOCKS proxy itself is actually reachable from the machine. For example:
curl --socks5-hostname 127.0.0.1:1081 https://ifconfig.me
If that fails, the issue is not Konqueror.
Third, try setting the proxy in KDE System Settings > Network > Proxy rather than only inside Konqueror. Historically, Konqueror’s proxy page is effectively a frontend for KDE’s global KIO proxy configuration, and there have been multiple reports over the years of proxy settings appearing to save correctly but not being applied as expected.
Also check whether hostname resolution is occurring through the SOCKS proxy. Some SOCKS setups work only when remote DNS resolution is enabled. A quick test is to compare access by hostname versus direct IP address.
Finally, if your goal is to tunnel all WebEngine traffic through a SOCKS proxy, launching the browser with explicit Chromium-style proxy arguments may be more reliable than relying on the KDE proxy dialog. If the traffic is coming from QtWebEngine rather than KIO, the GUI proxy settings may simply never be consulted.
Can you post:
With that information it should be possible to determine whether this is a configuration issue, a DNS-through-SOCKS issue, or a QtWebEngine/KIO proxy limitation.
