I enabled IndexNow today as I had only just come across this feature.

It's now logging consistent errors:

403 invalid_api_key Array
(
    [host] => www.XXX.com/forums/
    [key] => b0742bd1dded481993be712b9deXXXX
    [keyLocation] => https://www.XXX.com/b0742bd1dded481993be712b9de6XXXX.txt
    [urlList] => Array
        (
            [0] => https://www.XXX.com/forums/topic/534459-wtb-exposure-2510-integrated-amplifier/
        )

)

I can see the file being referenced above in the key location has the wrong path.

That file is present at /forums/ but not at the base level as the error log shows.

As there are no settings related to this integration, I cannot address it?

There are no settings.

I'm going to investigate this on your community right now.

I've disabled it for now to avoid filling up the error log.

Thanks for bringing the issue to our attention. I have pushed a fix which is awaiting review.

 

13 hours ago, Daniel F said:

I have pushed a fix which is awaiting review.

For those not familiar, what does this actually mean? It will be included in a future patch or minor update? Or is it something we can obtain soon, separately? Should we just leave IndexNow disabled until that happens? Can we get some clarity for those that are not developers or inside the 'Team' please?

9 hours ago, Emediate said:

For those not familiar, what does this actually mean? It will be included in a future patch or minor update? Or is it something we can obtain soon, separately? Should we just leave IndexNow disabled until that happens? Can we get some clarity for those that are not developers or inside the 'Team' please?

This would mean it will be available in a future release, likely the next monthly release.

On 3/10/2022 at 1:55 AM, Emediate said:

That file is present at /forums/ but not at the base level as the error log shows.

The file needs to be placed at the root level, per https://www.indexnow.org/documentation

Nope, disregard.

Edited March 12, 20222 yr by bassangler

A patch has now been released to resolve this issue. Please visit support in your admin CP, and select to apply the optional patches present to resolve this.