[Plugin: Google XML Sitemaps] A problem notifying Google

pchamp
(@pchamp)

16 years, 9 months ago

I just moved a site from one host to another, and upgraded to Google Sitemap Generator 3.1.5. I’m running WordPress 2.8.4. Now I get the following when I generate a map:

“The last build succeeded, but the file was deleted later or can’t be accessed anymore. Did you move your blog to another server or domain?
There was a problem while notifying Google.”

Bing and Ask.com were notified successfully.

When I look in the debug function, I see this in the Errors section:

Notice: WP HTTP API Web Request failed: name lookup timed out in /home/mavisc5/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2303
Notice: Failed to ping Google: in /home/mavisc5/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2206

sitemap.xml and sitemap.xml.gz exist with 666 permissions. ‘Write a gzipped file’ is unchecked. There are no robots.txt files anywhere in the site. The automatic detection section of the plugin’s settings has the correct (new) path and URL for the sitemap.

Is there something else I needed to do when I moved from one host to another to keep everything working? It worked fine on the old host.

Thanks!
Peggy

Viewing 8 replies - 1 through 8 (of 8 total)

nielskreijveld
(@nielskreijveld)

16 years, 9 months ago

I would like to know this too, as I get the same message. I’ve moved to a new domain too. However, I don’t get any errors when I run the debug function, but I still get the notice at the top of the page when I manually rebuild the sitemap.

Arne
(@arnee)

16 years, 9 months ago

Hi,

the error comes from the WordPress API and says that it can’t resolve the IP address of google.com. Looks like there is something wrong with the configuration of your webserver.

redgsr1
(@redgsr1)

16 years, 9 months ago

I have not changer my server at all and just updated to the latest version on this plugin getting the same error…

“The last build succeeded, but the file was deleted later or can’t be accessed anymore. Did you move your blog to another server or domain?”

Thread Starter pchamp
(@pchamp)

16 years, 9 months ago

I don’t think it’s my server. I’m a web designer and have quite a few clients – and my own site – on this web host. Every time I update this plugin to 3.1.5 on one of my clients’ sites, it stops working properly, even when it’s the only change I’ve made.

The latest one I tried says:
“The last build succeeded, but the file was deleted later or can’t be accessed anymore. Did you move your blog to another server or domain?”

Here the Google notification succeeded, but the Ask.com one failed. And I haven’t moved or done anything else to this blog.

Any other ideas?

Peggy

redgsr1
(@redgsr1)

16 years, 9 months ago

Something is wrong with the plugin it’s not the server – I am getting the same error. This plugin always has some sort of error.

railcrew
(@railcrew)

16 years, 9 months ago

I just updated to 3.1.5 too and get the message…”The last build succeeded, but the file was deleted later or can’t be accessed anymore. Did you move your blog to another server or domain?”… all were notified successfully though. gonna try rolling back to previous version… let you know…

railcrew
(@railcrew)

16 years, 9 months ago

rolled back to 3.1.2, problem solved… something wrong with the update(?)

Arne
(@arnee)

16 years, 9 months ago

Hi,

the new version includes a new check if the sitemap files are still readable when you view the admin page. The previous version did not include this check. Could somebody else confirm that this message appears by mistake?

Thanks,

Arne