Setting up a proxy in KDE

Comments: 1

KDE, short for K Desktop Environment, is a Linux desktop environment that provides a graphical user interface shell. Configuring a private proxy in KDE can be done either through the system interface or via the terminal. This enables you to route your Internet traffic, bypass regional restrictions, change your IP address to access blocked platforms, and surf the web anonymously.

Step-by-step guide on how to set up a proxy in KDE

  1. Open system settings.

    1.png

  2. Navigate to the “Network” section.

    2.png

  3. Find the “Proxy” tab and choose “Use manually specified proxy configuration”. Enter the IP-address and port of the proxy server. KDE supports HTTP, HTTPS, and SOCKS protocols.

    3.png

  4. For private proxies, enter your username and password in the authorization window that appears during the first connection after setup.

    4en.png

Setting up a proxy in KDE via terminal

  1. Open the terminal using the key combination “Ctrl+Alt+T”.
  2. Configure the HTTP/HTTPS proxy using the http_proxy and https_proxy environment variables. Use the following commands, replacing username, password, your_proxy_address, and port with your proxy details:

    5.png

  3. Configure a SOCKS proxy using the all_proxy=socks5:

    6.png

  4. Reboot the terminal or run source ~/.bashrc to apply the changes.
  5. Check if the configured proxy is working using the “curl” command with the “-x” options. Replace “example.com” with the address of the site you want to open:

    7.png

How to Properly Configure Different Proxy Types in KDE

When configuring proxies in the KDE environment, it’s important to understand that KDE itself does not impose strict limitations. It relies on Linux system-wide network settings, which means standard HTTP, HTTPS, and SOCKS proxies are fully supported.

  • ISP proxy — suited for system-level configuration and long-term stable operation, where a fixed IP and predictable connectivity matter.
  • Residential proxy — used when simulating normal user traffic is important and block risk must be reduced.
  • Mobile proxy — relevant for scenarios with frequent IP changes and a higher trust level from websites.
  • Datacenter IPv4 or IPv6 proxy — applied to technical tasks, testing, or automation, where speed and scalability are critical.

Static types are best configured at the system level. Dynamic ones are less suitable for full system-wide configuration. Frequent IP rotation can disrupt active connections and system services. For these cases, it’s better to use proxy managers or per-application settings, allowing traffic to be routed selectively and IP changes to be handled without breaking the entire system.

The setup is complete, and you can now use KDE proxies to access previously inaccessible resources and bypass other restrictions.

Comments:

1 comment

Vasya
Found:
```
kwriteconfig5 --file kioslaverc --group "Proxy Settings" --key "ProxyType" 1
kwriteconfig5 --file kioslaverc --group "Proxy Settings" --key "httpProxy" "http://127.0.0.1:10809"
kwriteconfig5 --file kioslaverc --group "Proxy Settings" --key "httpsProxy" "http://127.0.0.1:10809"
kwriteconfig5 --file kioslaverc --group "Proxy Settings" --key "NoProxyFor" "localhost,127.0.0.1,192.168.0.0/16"
dbus-send --type=signal --dest=org.kde.kded5 /kded org.kde.kded5.reloadConfiguration
```

And question:
Why GUI is not configured to execute `dbus-send` when config is changed?