ftp://1a20.com/: Googlebot can’t access your site

Well, this is new for me. I didn’t google also crawl ftp not just http, and in fact I think google crawl a lot of other ones as well. I don’t understand why would google want to crawl via ftp? Very interesting. However I don’t have any files via ftp for google to crawl, so I think I will just ignore this then, http is good enough for contents.

From: “wmt-noreply@google.com” <wmt-noreply@google.com>
Sent: Saturday, February 15
Subject: [Webmaster Tools] ftp://1a20.com/: Googlebot can’t access your site

Google Logo
ftp://1a20.com/: Googlebot can’t access your site

Over the last 24 hours, Googlebot encountered 1 errors while attempting to access your robots.txt. To ensure that we didn’t crawl any pages listed in that file, we postponed our crawl. Your site’s overall robots.txt error rate is 100.0%.
You can see more details about these errors in Webmaster Tools.
Recommended action
If the site error rate is 100%:
Using a web browser, attempt to access ftp://1a20.com/robots.txt. If you are able to access it from your browser, then your site may be configured to deny access to googlebot. Check the configuration of your firewall and site to ensure that you are not denying access to googlebot.
If your robots.txt is a static page, verify that your web service has proper permissions to access the file.
If your robots.txt is dynamically generated, verify that the scripts that generate the robots.txt are properly configured and have permission to run. Check the logs for your website to see if your scripts are failing, and if so attempt to diagnose the cause of the failure.
If the site error rate is less than 100%:
Using Webmaster Tools, find a day with a high error rate and examine the logs for your web server for that day. Look for errors accessing robots.txt in the logs for that day and fix the causes of those errors.
The most likely explanation is that your site is overloaded. Contact your hosting provider and discuss reconfiguring your web server or adding more resources to your website.
If your site redirects to another hostname, another possible explanation is that a URL on your site is redirecting to a hostname whose serving of its robots.txt file is exhibiting one or more of these issues.
After you think you’ve fixed the problem, use Fetch as Google to fetch ftp://1a20.com/robots.txt to verify that Googlebot can properly access your site.
Learn more in our Help Center.
Got feedback? Leave it here. Be sure to include this message ID: [WMT-94051]
Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 | Unsubscribe.