Set GNOME’s Manual SOCKS Proxy with gsettings

For a SOCKS service already listening on 127.0.0.1:1080, GNOME needs both the endpoint and manual proxy mode. Run these settings as the desktop user whose applications should use them.

Keep the previous values

Read and note the current mode, SOCKS host and port before changing them:

gsettings get org.gnome.system.proxy mode
gsettings get org.gnome.system.proxy.socks host
gsettings get org.gnome.system.proxy.socks port

Set the endpoint and select it

gsettings set org.gnome.system.proxy.socks host '127.0.0.1'
gsettings set org.gnome.system.proxy.socks port 1080
gsettings set org.gnome.system.proxy mode 'manual' 

Use the real listener address and port if they differ. These commands configure clients; they do not start the SOCKS server. Repeat the readback commands to confirm the saved values, then make a new request in an application that follows GNOME's proxy settings.

If the browser still uses HTTP

SOCKS is the default for protocols without a specific proxy. Inspect the protocol-specific entries:

gsettings get org.gnome.system.proxy.http host
gsettings get org.gnome.system.proxy.http port
gsettings get org.gnome.system.proxy.https host
gsettings get org.gnome.system.proxy.https port
gsettings get org.gnome.system.proxy.ftp host
gsettings get org.gnome.system.proxy.ftp port

An HTTP, HTTPS or FTP entry can take precedence for its traffic. HTTP can also serve HTTPS when no separate HTTPS endpoint is configured. Keep intentional overrides; change a stale entry only if the intended policy is SOCKS for that traffic.

Restore the desktop policy

Put back the saved SOCKS host and port and the previous mode. If the original mode was none, selecting none disables desktop proxy use while retaining endpoint values. auto uses the configured automatic-policy URL; manual selects stored endpoints.

Check the result in the application you intend to use. A program with its own proxy or environment configuration can choose another route.