Fixed IndexNow error: [500] An unexpected error occurred

I

ivp

Active member
Affected version
2.3.5
Sporadically seeing the following error:

Code: 
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:
Seeker-Smith

XF 2.3 Thread 'indexnow server error'

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)...
  • Like
 
Might be part of this.

Chromaniac

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

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...
 
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.
 
Last edited:

Similar threads

Seeker-Smith
  • Question Question
XF 2.3 indexnow server error
Replies
3
Views
137
ichpen
ichpen
Abraham54
  • Question Question
XF 2.3 IndexNow error: [403] Site Verification is not completed.
Replies
8
Views
119
Abraham54
Abraham54
Dzgsm
  • Solved
XF 2.3 Unexpected IndexNow Timeout Error
Replies
1
Views
41
Chromaniac
Chromaniac
B
Fixed IndexNow error: The key field is required.
Replies
18
Views
459
Naz
Naz
GameNet
ErrorException: XF\Job\VerifyEmailDkim: [E_WARNING] dns_get_record(): An unexpected server failure occurred. src/XF/Repository/EmailDkimRepository.php
Replies
0
Views
27
GameNet
GameNet
Back
Top Bottom