Troubleshooting

Nothing shows up

• Recording may be paused. The toolbar says Recording paused; click Resume recording (⌘/Ctrl+P).
• A filter may be hiding it. The count reads "N of M" when a search or quick filter is on. Clear the search box and choose All.
• The program isn't using the proxy. Use a browser or terminal Wirescry opens, or set the program up. Some programs ignore proxy settings altogether.
• The port changed. Without a fixed port, Wirescry takes the first free one from 8000, so it can differ from last time. Check the toolbar, or fix the port.

HTTPS fails with a certificate error

The program doesn't trust Wirescry's certificate. Use a browser or terminal Wirescry opens, or trust the certificate. If you used Reset certificate, everything set up by hand needs the new one.

Some programs pin their own certificates and refuse any other; Wirescry can't decrypt those.

A TLS failure in the Status column is different: it's about the server's certificate, as Wirescry saw it. The detail pane says what was wrong, for example expired, self-signed, or for another host name.

A request failed

Select it: the detail pane explains the failure in plain language, with the original error. When requests fail lists each kind. If the server never answered, the client got a 502 from Wirescry, labeled "sent by Wirescry".

Port already in use

If you choose a port another program is using, Wirescry says so and stays on the port it had. If a port you fixed is taken by the time Wirescry starts, its proxy can't start: quit the other program, then click Restart proxy.

The proxy stopped

If the proxy stops unexpectedly, Wirescry restarts it and keeps your list, with earlier requests dimmed (why). If it keeps stopping, the toolbar says Proxy stopped; click Restart proxy, and Show log for the cause.

A terminal tool still doesn't show up

Check What's covered. The usual causes:

• On macOS, the system's own Python or Ruby (/usr/bin/python3, /usr/bin/ruby). Use one from Homebrew, pyenv, python.org, uv, rbenv or asdf.
• Go on Windows reads only the Windows certificate store: trust the certificate.
• Node.js 23, or any version before 22.21, ignores proxy variables.
• Python aiohttp needs trust_env=True.

Reporting a problem

Help → Report a Problem… opens the issue tracker on GitHub. Please say which version you have (About Wirescry) and your system, and attach the relevant part of the log (Help → Show Log File). Read it first: it includes the host names of requests that failed.