ProxyLens support

Get unstuck faster with focused ProxyLens support.

Find guidance for setup, HTTPS inspection, mock rules, breakpoints, API playground workflows, MCP support, licenses, and billing. When you need us, send the details that help us reproduce the issue quickly.

Email: support@xeontech.in Priority: Pro and Team customers

Contact XeonTech

The form opens a prepared email so no message disappears into an unconfigured backend.

Prefer email? Reach us directly at support@xeontech.in.

Before contacting support

Send the details that make the issue reproducible.

Good support starts with clear evidence. These details help us understand your setup, the affected request, and the expected result.

computer

Environment

  • macOS version and device type.
  • ProxyLens version and plan type.
  • Whether the issue happens in one app or multiple apps.
fact_check

Reproduction

  • Steps that trigger the issue.
  • Expected behavior and actual behavior.
  • Request method, path, status code, and timing when relevant.
privacy_tip

Redaction

  • Remove passwords, API keys, tokens, cookies, and private keys.
  • Mask customer names, emails, IDs, and production payloads.
  • Share a minimal sample whenever possible.

Troubleshooting

Common setup checks for capture and HTTPS inspection.

If ProxyLens is not showing traffic, start with the basics: confirm the app is using the macOS proxy settings, check whether HTTPS inspection is enabled for the traffic you intend to inspect, and verify the local certificate trust flow.

check_circleConfirm traffic is routed through the local proxy

check_circleTrust the local certificate only for debugging traffic you control

check_circleCheck whether the app uses certificate pinning or a custom network stack

Support checklist
rule Capture setup
proxy: enabled
certificate: trusted for debug target
domain filter: review exclusions
app behavior: check certificate pinning
next step: reproduce with one request

Frequently asked questions

Useful answers before you write in.

Why do I need to trust a certificate for HTTPS?

HTTPS encrypts traffic. ProxyLens can only show decrypted bodies when you explicitly trust its local certificate for debugging.

Is captured traffic uploaded to XeonTech?

No. Capture and inspection happen locally on your Mac. Only send sessions or logs to support when you choose to.

Why is an app missing from capture?

Check proxy settings first. Some apps use certificate pinning or custom network stacks that may require extra setup or cannot be decrypted.

Can I use ProxyLens for QA scenarios?

Yes. Conditional mocks are built for testing rare backend states, failures, empty payloads, auth expiry, and release regressions.

How do Team seats work?

The Team plan includes five activations with shared billing. Contact us for invoices, POs, or larger rollouts.

What should I include in a bug report?

Include macOS version, ProxyLens version, repro steps, expected behavior, actual behavior, and redacted sample traffic when relevant.

Can you help write a mock rule?

Yes. Send the request pattern, the response you want to return, and the condition that should trigger the mock.

Can I share a saved session?

Yes, but review and redact sensitive values first. Share only the session details needed to reproduce the issue.

Do you support purchase orders?

Contact us for Team purchases, invoices, purchase orders, tax details, or larger rollout questions.

Support expectations

We aim for practical, reproducible answers.

We may ask follow-up questions, request redacted logs, or suggest a smaller test case. Pro and Team customers receive priority, and all users should avoid sending secrets or unredacted production data.

mail Email support Review features arrow_forward