// settings

Settings, Proxy & Certificates

Open Settings with Ctrl/Cmd+, or Settings in the main menu. There is no Save button — every change applies immediately.

General

Appearance

  • Language — English, Deutsch, Français, Italiano, Español, or Português (Brasil)
  • Theme — Light, Dark, or System (default)
  • Accent Color — green (default), teal, blue, indigo, purple, yellow, orange, red, or pink
  • Layout — Stacked (default) or Side by side; see Layout

Requests

  • HTTP Version — Auto (default) negotiates HTTP/2 or HTTP/1.1 with the server; HTTP/1.x forces HTTP/1.1; HTTP/2 uses HTTP/2 without negotiation, so servers that only speak HTTP/1 will fail
  • Request Timeout — in milliseconds; 0 (default) means no timeout
  • Verify SSL certificates — on by default. Turn it off for self-signed certificates in development; it applies to HTTP, WebSocket, SSE, gRPC, MQTT, and GraphQL subscriptions
  • Automatically follow HTTP redirects — on by default. Turn it off to inspect a redirect response itself
  • History Limit — how many requests history keeps (default 100, minimum 10)

Proxy

  1. Open the Proxy tab and turn on Enable Proxy
  2. Either turn on Use System Proxy, or choose a Type (HTTP, HTTPS, SOCKS4, or SOCKS5) and enter Host and Port
  3. If the proxy needs credentials, turn on Authentication and enter a username and password
  4. List hosts that should skip the proxy in Bypass List, separated by commas
  5. Click Test Connection to check the proxy

Bypass list rules

  • localhost, 10.0.0.5 — that exact host
  • *.example.com — example.com and all of its subdomains
  • .example.com — subdomains only
  • Matching ignores case. IP ranges (CIDR), ports, and other wildcards are not supported

What goes through the proxy

  • HTTP and GraphQL requests, SSE, OAuth 2.0 token requests, and pm.sendRequest in scripts
  • WebSocket and GraphQL subscriptions — through HTTP or HTTPS proxies only; with a SOCKS proxy, add the host to the bypass list
  • gRPC and MQTT connect directly and ignore the proxy

Use System Proxy reads the HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY environment variables, and on macOS and Windows also the system settings. On Linux, desktop proxy settings (GNOME, KDE) are not read — set the environment variables or configure the proxy manually. While a proxy is active it is shown in the status bar.

The proxy password is stored in Resonance’s local settings file (readable only by you), not in the OS keychain.

Client Certificates (mTLS)

Present a client certificate to servers that require mutual TLS, or trust a private CA, per host.

  1. Open the Certificates tab and click Add Certificate
  2. Enter the Host, e.g. api.example.com — or api.example.com:8443 to match one port only
  3. Choose the Certificate (PEM) and Private Key (PEM, unencrypted), and optionally a CA Bundle (PEM, optional)
  • Files must be PEM. The certificate may include its chain; the key must be unencrypted (PKCS#8, PKCS#1 RSA, or SEC1). PKCS#12 (.pfx/.p12) files and encrypted keys are not supported — convert them with openssl first
  • An entry with only a CA Bundle trusts that CA for the host without sending a client certificate. CA certificates are added to the system roots, not used instead of them
  • Hosts match case-insensitively and exactly — no wildcards or subdomains. A bare host matches every port; don’t include default ports such as :443
  • Only the file paths are stored; the files are read on every request, so renewed certificates are picked up automatically
  • Used for HTTP, GraphQL, SSE, WebSocket, GraphQL subscriptions, gRPC, and MQTT. Turn an entry off with Enabled without deleting it

Secrets & the OS Keychain

Secrets are kept in the OS keychain — Keychain on macOS, Credential Manager on Windows, Secret Service (GNOME Keyring or KWallet) on Linux — and written to collection files and exports as empty values, so a collection can be committed safely.

  • Variables — click the lock on a row in Manage Environments or a collection’s Manage Variables. Secret values are masked; use the eye button to show one
  • Credentials — tokens, passwords, API key values, OAuth 2.0 secrets and tokens, AWS secret keys, and MQTT passwords are always stored as secrets
  • A credential field that contains a {{variable}} is saved as written — a good pattern is {{token}} in the auth field and token as a secret environment variable

If no keychain is available, secrets are stored unencrypted in a local file readable only by you; the status bar shows Secrets unencrypted, and they move into the keychain once one is available. The Flatpak uses the desktop secret portal; the Snap needs snap connect db-mobile-resonance:password-manager-service.

Updates

  • Check for updates on launch — off by default; when on, a notification appears if a new version is out
  • Check for Updates — checks now, then Install & Restart downloads and installs the update
  • Self-updating applies to the AppImage, the Windows installer, and the macOS app. Flatpak, Snap, Homebrew, Scoop, and .deb/.rpm installs are updated by their package manager instead, and the tab says so

Troubleshooting

Requests fail with a certificate error

  • For a private CA, add a CA Bundle entry for the host instead of turning off Verify SSL certificates
  • Note that a CA bundle is ignored while verification is off

Requests time out behind a corporate proxy

  • Use Test Connection to check the proxy, and add internal hosts to the bypass list

Next Steps