XF 2.2 Error submitting sitemap to Bing

JoyFreak

JoyFreak

Well-known member
Just had this error logged in the Admin CP. It only occurred once, earlier today. Any concerns or can be ignored?
Code: 
Server error log
GuzzleHttp\Exception\ClientException: Error submitting sitemap to https://www.google.com/webmasters/tools/ping?sitemap=https%3A%2F%2Fwww.joyfreak.com%2Fsitemap.php: Client error: `GET https://www.google.com/webmasters/tools/ping?sitemap=https%3A%2F%2Fwww.joyfreak.com%2Fsitemap.php` resulted in a `429 Too Many Requests` response: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head><meta http-equiv="content-type" content="te (truncated...) src/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Generated by: Unknown account Dec 13, 2021 at 8:22 AM
Stack trace
#0 src/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 src/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 src/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), NULL)
#3 src/vendor/guzzlehttp/promises/src/TaskQueue.php(48): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}()
#4 src/vendor/guzzlehttp/promises/src/Promise.php(248): GuzzleHttp\Promise\TaskQueue->run(true)
#5 src/vendor/guzzlehttp/promises/src/Promise.php(224): GuzzleHttp\Promise\Promise->invokeWaitFn()
#6 src/vendor/guzzlehttp/promises/src/Promise.php(269): GuzzleHttp\Promise\Promise->waitIfPending()
#7 src/vendor/guzzlehttp/promises/src/Promise.php(226): GuzzleHttp\Promise\Promise->invokeWaitList()
#8 src/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending()
#9 src/vendor/guzzlehttp/guzzle/src/Client.php(131): GuzzleHttp\Promise\Promise->wait()
#10 src/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request('get', 'https://www.goo...', Array)
#11 src/XF/Sitemap/Builder.php(508): GuzzleHttp\Client->__call('get', Array)
#12 src/XF/Sitemap/Builder.php(432): XF\Sitemap\Builder->sendPing()
#13 src/XF/Sitemap/Builder.php(73): XF\Sitemap\Builder->completeBuild()
#14 src/XF/Job/Sitemap.php(27): XF\Sitemap\Builder->build(2.79395)
#15 src/XF/Job/Manager.php(260): XF\Job\Sitemap->run(8)
#16 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 8)
#17 src/XF/Job/Manager.php(118): XF\Job\Manager->runJobEntry(Array, 8)
#18 src/XF/Admin/Controller/Tools.php(122): XF\Job\Manager->runByIds(Array, 8)
#19 src/XF/Mvc/Dispatcher.php(352): XF\Admin\Controller\Tools->actionRunJob(Object(XF\Mvc\ParameterBag))
#20 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(ThemeHouse\UserCriteria\XF\Admin\Controller\Tools), NULL)
#21 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(ThemeHouse\UserCriteria\XF\Admin\Controller\Tools), NULL)
#22 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#23 src/XF/App.php(2351): XF\Mvc\Dispatcher->run()
#24 src/XF.php(517): XF\App->run()
#25 admin.php(13): XF::runApp('XF\\Admin\\App')
#26 {main}
Request state
array(4) {
  ["url"] => string(24) "/admin.php?tools/run-job"
  ["referrer"] => string(120) "https://www.joyfreak.com/admin.php?tools/run-job&only_id=104412&_xfRedirect=%2Fadmin.php%3Ftools%2Frebuild%26success%3D1"
  ["_GET"] => array(1) {
    ["tools/run-job"] => string(0) ""
  }
  ["_POST"] => array(3) {
    ["_xfRedirect"] => string(58) "https://www.joyfreak.com/admin.php?tools/rebuild&success=1"
    ["_xfToken"] => string(8) "********"
    ["only_ids"] => string(6) "104412"
  }
}
 
Solution
Chris D
So to be clear this is an issue solely on the Bing end and can be safely ignored.

I don’t know how you go about reporting issues to Bing but it’s likely that enough people need to make them aware and hopefully that will prompt them to turn it off and on again.

Hopefully this isn't a planned closure of the sitemap ping endpoint. If it is, I can't see it documented anywhere...

It seems Bing are going all-in on their IndexNow protocol but I can't see them doing away with sitemaps just yet.

Does anyone actually have a Bing Webmaster Tools account? If so, please open a ticket or send them an email regarding this or please look for any further clues about what might be going on.

Cheers :)
Sort by date Sort by votes
Just posting this Bing sitemap server error info here (before I delete them)...in case it helps with anything that may pop up in the future.

I received Bing sitemap submit server errors on:

12-24-21
12-27-21
12-29-21
12-31-21
1-3-22

As can be seen from the dates...still getting these errors as of the date of this post. I know it's already been mentioned that this is not a Xenforo issue...but a Bing issue.:)
 
Upvote 0 Downvote
The sitemap always works. It's always there and search engines still know where to find it. The "ping" which tells Bing that it has been updated does not work, but also, for the reasons mentioned, probably doesn't cause any issue. It can be safely ignored.
 
Upvote 1 Downvote
ActorMike said:
Can someone explain, does the sitemap still work intermittently on the days there are no errors? I got another error yesterday as well.
Click to expand...
It will produce an error every time the cron runs to rebuild the sitemap, which isn’t daily, it’s every few days if you haven’t edited it.
 
Upvote 1 Downvote
djbaxter said:
On a positive note, given that Bing shares the tiny bit of the search market left after Google, it's likely that only about 3 or 4 of your forum members or potential members are affected. :)
Click to expand...
I just had a member join and responded to our auto welcome stating they found us through Bing.lol

Illustration- 3% of 1 million dollars is still 30,000! :-) Every little bit counts!


bing-search.webp
 
Upvote 0 Downvote
Still getting this error. Oddly, I don't get any error with any other site than the one using Xenforo. (I have a Vanilla, Wordpress and PHPBB site and none of them get an error submitting site maps to Bing.)
 
Upvote 0 Downvote
Since changing the Bing submission URL to the one specified by @Chris D, have had NO MORE SUBMISSION ERRORS. This for two different XenForo forums.

I highly recommend that folks just change the damn URL, and stop complaining. That solves the problem, and the fix takes all of 1 minute.
 
Upvote 1 Downvote
It's unlikely to be the same error because that workaround URL is currently working and serving requests whereas the original one isn't.

If you can post the exact error message/stack trace we can comment further.
 
Upvote 0 Downvote
Chris D said:
I said it was a workaround rather than a permanent fix.
Click to expand...
Why is changing the ping URL as seen below only considered a workaround? Does it still function as intended and submit the ping for the sitemap or does it just avoid getting the server log error message?

Also, what is the $ removed on the workaround URL?

PS for those new to XF the setting is at /admin.php?options/groups/sitemap/#sitemapAutoSubmit

Old URL:
http://www.bing.com/ping?sitemap={$url}

Workaround URL:
https://bing.com/webmaster/ping.aspx?sitemap={url}


Tested by running the Build Sitemap Cron at /admin.php?cron/
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

Garfield™
  • Solved
XF 2.2 GuzzleHttp\Exception\ClientException: Error submitting sitemap to
Replies
15
Views
1K
Black Tiger
Black Tiger
rickhz
  • Question Question
XF 2.2 Sitemap issue
Replies
1
Views
256
nodle
nodle
Ozzy47
Server Error Upgrading To Latest Version
Replies
6
Views
402
Chris D
Chris D
maszd
  • Question Question
XF 2.2 Server error submitting sitemap
Replies
7
Views
855
Black Tiger
Black Tiger
gerryvz
  • Question Question
XF 2.2 Google Sitemap Submission Error
Replies
7
Views
1K
gerryvz
gerryvz
Top Bottom