Troubleshoot runners in Postman

If you experience an issue with a runner, the following troubleshooting steps may help you identify and resolve the issue.

Authentication error in the Postman CLI

If the Postman CLI returns an authentication error, make sure you have the correct runner ID and key. Learn how to view the runner ID. You may need to reset your runner key if you didn’t store it in a secure location for later.

Learn more about using the Postman CLI to set up a runner in your internal network.

Firewall blocks outgoing connections

If your organization operates behind a firewall, your IT team may need to allowlist the *.postman.com domain.

To learn more, see Use Postman behind a firewall.

Proxy server blocks outgoing requests

If you route runner traffic through a proxy server, ensure your authorization service allows you to make requests to the domain. The authorization service decides which requests from the runner are allowed or blocked, based on the domains your organization configured. If the request is blocked, you’ll receive the Request blocked by runner proxy error. Your IT team may need to configure the authorization service to allow requests to the domain.

Learn more about setting up a runner to use a proxy server.

The runner doesn’t start

If a runner doesn’t start in your internal network, verify the following:

• Confirm that the runner is correctly set up and running in your internal network.
• Check your monitor’s configuration to verify that the monitor is linked to the correct runner.
• Check that the machine hosting the runner is online and accessible.
• Confirm that the runner ID and key are correct. You may need to reset your runner key if you didn’t store it in a secure location.

If this didn’t resolve your issue, contact Postman support.