Why isn’t Hoverfly matching my request?

When Hoverfly cannot match a response to an incoming request, it will return information on the closest match:

Hoverfly Error!

There was an error when matching

Got error: Could not find a match for request, create or record a valid matcher first!

The following request was made, but was not matched by Hoverfly:

    "Path": "/closest-miss",
    "Method": "GET",
    "Destination": "",
    "Scheme": "http",
    "Query": "",
    "Body": "",
    "Headers": {
        "Accept-Encoding": [
        "User-Agent": [

The matcher which came closest was:

    "path": {
        "exactMatch": "/closest-miss"
    "destination": {
        "exactMatch": ""
    "body": {
        "exactMatch": "body"

But it did not match on the following fields:


Which if hit would have given the following response:

    "status": 200,
    "body": "",
    "encodedBody": false,
    "headers": null

Here, you can see which fields did not match. In this case, it was the body. You can also view this information by running hoverctl logs.

Why isn’t Hoverfly returning the closest match when it cannot match a request?

Hoverfly will only provide this information when the matching strategy is set to strongest match (the default). If you are using the first match matching strategy, the closet match information will not be returned.

How can I view the Hoverfly logs?

hoverctl logs

Why am I not able to access my Hoverfly remotely?

That’s because Hoverfly is bind to loopback interface by default, meaning that you can only access to it on localhost. To access it remotely, you can specify the IP address it listens on. For example, setting to listen on all network interfaces.

hoverfly -listen-on-host