Confirmed IndexNow error: [500] An unexpected error occurred

[ivp]

Affected version

2.3.5

Sporadically seeing the following error:

ErrorException: IndexNow error: [500] An unexpected error occurred. Please try again later. src/XF/Error.php:81

Stack trace
#0 src/XF.php(266): XF\Error->logError('IndexNow error:...', false)
#1 src/XF/IndexNow/Api.php(86): XF::logError('IndexNow error:...')
#2 src/XF/IndexNow/Api.php(34): XF\IndexNow\Api->request('/?key=...', Array, 'IndexNow error:...')
#3 src/XF/Job/ContentIndexNow.php(84): XF\IndexNow\Api->index('https://forum...')
#4 src/XF/Job/Manager.php(275): XF\Job\ContentIndexNow->run(8)
#5 src/XF/Job/Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
#6 src/XF/Job/Manager.php(89): XF\Job\Manager->runJobEntry(Array, 8)
#7 job.php(46): XF\Job\Manager->runQueue(false, 8)
#8 {main}

Request state
array(4) {
  ["url"] => string(8) "/job.php"
  ["referrer"] => string(64) "https://forum.../threads/abc.123/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

I am not the only one:

XF 2.3 Thread 'indexnow server error'

Dec 24, 2024

I'm getting server errors on one site and not the other. Something I'm missing in the setup?

• ErrorException: IndexNow error: [500] An unexpected error occurred. Please try again later.
• src/XF/Error.php:82

Stack trace

#0 src/XF.php(266): XF\Error->logError('IndexNow error:...', false)
#1 src/XF/IndexNow/Api.php(86): XF::logError('IndexNow error:...')
#2 src/XF/IndexNow/Api.php(34): XF\IndexNow\Api->request('/?key=XXXXXXXXX...', Array, 'IndexNow error:...')
#3 src/XF/Job/ContentIndexNow.php(84)...

• Seeker-Smith
• Replies: 3
• Forum: Troubleshooting and problems

• 

 

[ivp]

Now seeing hundreds of:

ErrorException: IndexNow error: [429] We're sorry, but you have sent too many requests to us recently. src/XF/Error.php:81

 

[Chromaniac]

did you move around a lot of threads using something like batch update threads?

you can logically disable indexnow option if you really do not care about what it offers!

 

[ivp]

Didn't use batch update. Just having a large forum.

 

[webbouk]

I'm getting the same occasional error, perhaps 1 in 600 posts, with no specific reason

 

[Mr Lucky]

I get this when using batch update threads. Does it indicate a problem?

 

[Chromaniac]

Might be part of this.

Fixed Thread 'IndexNow: Avoid sending requests when user is just moving threads from one node to another'

May 16, 2024

So, I have been having an issue where posts from one user were not marking threads as unread in some nodes. I couldn’t find any reason for this behaviour, so I decided to create a new node and migrate all threads from old node to new one. This appears to have solved the problem for now.

But this did cause another problem. Server error log ended up with tons of entries related to IndexNow. I imagine that all threads moved from old node to new one created IndexNow requests which seems pointless as thread URLs and content remains same. The only thing changed was probably the meta data which...

• Chromaniac
• indexnow
• Replies: 1
• Forum: Resolved bug reports

 

[ForumDevs]

We are also getting the same error. Maybe @Chris D can have a look at this.

 

[ibnesayeed]

In addition to the atomic notifications, IndexNow protocol allows for batched updates, which can be helpful in reducing the number of HTTP requests to IndexNow servers. Another possibility is to partition notifications and send them to different IndexNow-supporting search engines, which they internally synchronize among each other within a few seconds.

 

[Jeremy P]

These are usually just intermittent issues with the IndexNow service. It may be reasonable for us to make the requests retry on failure to handle that a little more gracefully, but it's not typically indicative of a major problem.