Configure trusted reverse-proxy handling safely

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Allow forwarded connection information only from approved proxy addresses.

What this guide helps you do

Allow forwarded connection information only from approved proxy addresses. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

1. Use the supported Pixie CRM release or workflow that produces this security control.
2. Check the expected protection through an authorised test.
3. Record the result in the deployment or security audit evidence.

Fields and options

• Trusted proxy addresses/ranges
• Approved forwarded headers

Rules and limits

• List only the actual reverse proxy or load balancer addresses as trusted.
• Verify scheme and client-address handling through the proxy.
• Verify spoofed forwarded headers from an untrusted direct request are ignored.

Check it worked

• The protection is active without weakening another security control.

Security, audit and troubleshooting checks

• Use the exact authorised account, role and record before saving or sending.
• Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
• Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
• Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Related guides