FAQ

Common install and day-to-day issues. If you’re still stuck, contact support through the channel where you obtained DevPeek.

Linux won’t start after install

On Debian/Ubuntu, if the .deb from a GUI store does nothing, try: (1) run /opt/DevPeek/devpeek or devpeek in a terminal for errors; (2) use sudo apt install ./devpeek_*.deb; (3) install missing GTK/notification runtime deps.

Why is my phone missing from debug?

The device must use DevPeek as its proxy and produce at least one HTML document response. It must also download and trust the DevPeek CA—otherwise you only see CONNECT/opaque rows.

Why are scripts/styles missing in preview?

Preview honors the site’s CSP; blocked resources fail in the mirror by design—compare on a real device if unsure.

SSL is `*` but I still see tunnels

Confirm the client points at DevPeek and that SSL proxy enabled is on. Hosts outside the allowlist or traffic that bypasses the proxy (e.g. some HTTP/3 paths) may stay encrypted.

Breakpoints never fire

Did you enable a rule group from the menu? Without a group or with breakpoints off, nothing pauses.
Manual rules: Req/Res toggles; auto-breakpoint tamper vs pause logic.
Script rules: does `pause` return correctly? Any syntax errors in the script log?

Auto-update fails

Check network access to the vendor’s update endpoint; some internal/offline builds ship without auto-update. Disk permissions, free space, or security tools can also block downloads.

Extension cannot reach desktop DevPeek

Ensure DevPeek is running and firewalls allow loopback to the collaboration port. If you changed the collaboration HTTP port, set the same value in the extension popup. Escalate via your vendor channel if it persists.

Compliance

DevPeek can MITM, rewrite, and forward traffic. Use it only on systems you are allowed to test

Back to docs home or download home.

FAQ