Fixed Error submitting the sitemap to Bing

[RisteDimitrievski]

Affected version

2.2.8 Patch 1

The actual URL that has been pass to submit sitemap to Bing is incorrect URL, for this reason we get exception

• GuzzleHttp\Exception\ClientException: Error submitting sitemap to https://www.bing.com/ping?sitemap=https://test-instance.ristedimitrievski.mk/sitemap.php: Client error: GET https://www.bing.com/ping?sitemap=https%3A%2F%2Ftest-instance.ristedimitrievski.mk%2Fsitemap.php resulted in a 410 Gone response
• src/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113

If we open the link https://www.bing.com/ping?sitemap={$url} , change variable $url to your own URL and you will see that the link to submit sitemap is invalid. The actual url would be: https://bing.com/webmaster/ping.aspx?sitemap={$url}

Tips to resolve this bug:

Change the default URL for submitting sitemap to Bing webmaster to https://bing.com/webmaster/ping.aspx?sitemap={url}

 

[Old Nick]

Hello : https://xenforo.com/community/threads/error-submitting-sitemap-to-bing.201222/post-1553764

 

[Chris D]

That isn't really the recommended workaround as the ping.aspx link apparently does something different.

Essentially, Bing currently no longer supports sitemap pings.

This is workedaround in XF 2.2.9 already so there will no longer be an error displayed.

 

[Old Nick]

@Chris D I have now an error with Google... Is it the same cause ?

• GuzzleHttp\Exception\ConnectException: Error submitting sitemap to https://www.google.com/webmasters/tools/ping?sitemap=https://regionalis.fr/sitemap.php: cURL error 6: Could not resolve host: www.google.com (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
• src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:185
• Généré par: Compte inconnu
• le 28 Mars 2022 à 07:06

#0 src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(149): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array)
#1 src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(102): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#2 src/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#3 src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(28): GuzzleHttp\Handler\CurlHandler->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#4 src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(51): GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#5 src/vendor/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php(37): GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#6 src/vendor/guzzlehttp/guzzle/src/Middleware.php(30): GuzzleHttp\PrepareBodyMiddleware->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#7 src/vendor/guzzlehttp/guzzle/src/RedirectMiddleware.php(70): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#8 src/vendor/guzzlehttp/guzzle/src/Middleware.php(60): GuzzleHttp\RedirectMiddleware->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#9 src/vendor/guzzlehttp/guzzle/src/HandlerStack.php(67): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#10 src/vendor/guzzlehttp/guzzle/src/Client.php(277): GuzzleHttp\HandlerStack->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#11 src/vendor/guzzlehttp/guzzle/src/Client.php(125): GuzzleHttp\Client->transfer(Object(GuzzleHttp\Psr7\Request), Array)
#12 src/vendor/guzzlehttp/guzzle/src/Client.php(131): GuzzleHttp\Client->requestAsync('get', Object(GuzzleHttp\Psr7\Uri), Array)
#13 src/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request('get', 'https://www.goo...', Array)
#14 src/XF/Sitemap/Builder.php(508): GuzzleHttp\Client->__call('get', Array)
#15 src/XF/Sitemap/Builder.php(432): XF\Sitemap\Builder->sendPing()
#16 src/XF/Sitemap/Builder.php(73): XF\Sitemap\Builder->completeBuild()
#17 src/XF/Job/Sitemap.php(27): XF\Sitemap\Builder->build(7.15229)
#18 src/XF/Job/Manager.php(260): XF\Job\Sitemap->run(7.88814)
#19 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 7.88814)
#20 src/XF/Job/Manager.php(86): XF\Job\Manager->runJobEntry(Array, 7.88814)
#21 job.php(43): XF\Job\Manager->runQueue(false, 8)
#22 {main}

array(4) {
["url"] => string(8) "/job.php"
["referrer"] => string(22) "https://regionalis.fr/"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}

 

[Paul B]

It's a different error: cURL error 6: Could not resolve host: [URL='http://www.google.com/']www.google.com[/URL] .

 

[Old Nick]

Thanks. So what i have to do ? It's a curl error ?
These last days i had some curl errors, 3 or 4 occurred when i tried to like or edit a thread.

 

[Silmarillion]

That isn't really the recommended workaround as the ping.aspx link apparently does something different.

Essentially, Bing currently no longer supports sitemap pings.

This is workedaround in XF 2.2.9 already so there will no longer be an error displayed.

And what should you do if you are still using an older XF version?

 

[Kirby]

And what should you do if you are still using an older XF version?

Remove the ping URL from the options; all that 2.2.9+ does as a workaround is to skip pinging Bing.

 

[markoroots]

The best solution to fix the problem, is to remove the Bing url to ping the sitemap, from the Admin control panel and do in this way as Bing says.

 

[JackieChun]

That isn't really the recommended workaround as the ping.aspx link apparently does something different.

Essentially, Bing currently no longer supports sitemap pings.

This is workedaround in XF 2.2.9 already so there will no longer be an error displayed.

What is the recommended solution for XenForo 2.1.8? I don't see an option to stop "pinging" Bing, only an option to stop submitting the sitemap to Bing altogether (by removing the URL).

 

[Chris D]

That is the same thing. Remove the URL and XF will no longer try to ping it.

 

[JackieChun]

That is the same thing. Remove the URL and XF will no longer try to ping it.

I assume "pinging" used to happen when the dynamic sitemap was updated with new thread/keyword URLs? What are the SEO repercussions of stopping the pinging? Any information on how often Bing will retrieve the new URLs from your sitemap if you just submit the sitemap via Bing webmaster tools?

 

[Chris D]

Pinging is the same as submitting.

The SEO repercussions are minimal but the specifics will be down to Bing. I'm not sure if it's documented.