Skip to content

Troubleshooting

Reqly for Windows is in beta, and its installer isn’t signed yet, so Windows may warn you when you open Reqly.App-win-Setup.exe. Click More info, then Run anyway. See Install Reqly.

“Waiting for you to allow Reqly’s helper…” Reqly needs its helper to set your proxy. In System Settings, open General › Login Items & Extensions, and turn on Reqly under Allow in the Background. Capturing starts as soon as you do.

“Port 9090 is in use by another app.” Another app listens on Reqly’s port. In Settings › General, choose another Proxy port, then start capturing again.

“Reqly couldn’t reach its helper.” Try again. If it keeps happening, stop capturing, click Remove Helper… in Settings › General, and start capturing again. macOS may ask you to allow the helper again.

“Reqly’s helper is missing from the app.” Your copy of Reqly is incomplete. Download it again.

  • Check that Reqly is capturing. The status bar says Capturing on port and the port.
  • Some apps, such as command-line tools, don’t use your computer’s proxy settings. Point them at Reqly yourself, at 127.0.0.1 and Reqly’s port, or use a reverse proxy.
  • A request that shows as Encrypted connection passes through without Reqly reading it. Decrypt its host to see inside.

While Reqly decrypts a host, a request can fail because the app didn’t accept Reqly’s certificate:

  • Your computer, phone, simulator or emulator doesn’t trust Reqly’s current certificate, for example after you made a new one. Install it again: see Decrypt HTTPS, Phones and tablets and Simulators and emulators.
  • The app accepts only its own certificate. Stop decrypting its host: right-click the request, and choose Stop Decrypting followed by the host on the Mac, or Stop decrypting on Windows. Its traffic then passes through encrypted.
  • On Android 7 and later, apps trust a certificate you installed only if they opt in. Debug builds of your own apps can.

“The server’s certificate isn’t valid, so Reqly didn’t send the request.” Your computer doesn’t trust the certificate the server sent. If it’s your own server, with a certificate of its own, make your computer trust that certificate: on the Mac, in Keychain Access; on Windows, in its certificate manager, certmgr.msc, under Trusted Root Certification Authorities.

“The server asked for a client certificate, and Reqly has none for this host.” Add the certificate in Settings › Client Certificates on the Mac, or Settings › Client certificates on Windows. See Connections.

When you install Reqly’s certificate, Windows shows a warning of its own and asks you to confirm. That’s expected: the certificate is one Reqly made just for you, and it never leaves your PC. Confirm, and Reqly can decrypt the hosts you choose.

If you turned it down, Settings › HTTPS says Windows doesn’t trust the Reqly certificate, and Reqly decrypts nothing. Click Trust certificate…, and confirm this time.

Windows asks you to confirm again when you remove the certificate, or uninstall Reqly.

  • In the Devices window (⇧⌘D), check that Allow Devices on This Network is on, and that Reqly is capturing.
  • If macOS asked whether Reqly can accept incoming network connections, the answer has to be Allow. You can change it in System Settings › Network › Firewall.
  • The device has to be on the same network as your computer.
  • “Another app uses port 9090 on the network, so devices can’t connect.” Choose another Proxy port in Settings › General.

Reqly’s helper puts your proxy settings back when Reqly stops capturing, quits or crashes. If Reqly says Reqly couldn’t put your proxy settings back, quit Reqly, and its helper puts them back.

Choose Help › Report a Problem… on the Mac, or Help › Report a problem… on Windows, to open an issue on GitHub, with your versions of Reqly and of macOS or Windows filled in.

If Reqly quits unexpectedly, it offers to report it the next time it opens. Reqly opens the issue in your browser for you to read, change and submit. Nothing is sent until you do.