By playdreamer on

I get an a error like this when I try to update certain feeds in the aggregator:

warning: fsockopen(): unable to connect to www.domain.dom:80 in /home/user/www/drupal/includes/common.inc on line 226.

I am not sure what the problem is as the feeds are validating OK, they are from my own blog:

http://www.snowgo.com/index.xml (RSS 2.0)
http://www.snowgo.com/index.rdf (RSS 1.0)

I also wanted to include the feed from the blogs page on my Drupal site (http://www.snowblogs.net/blog/feed) in the aggregator but trying to update that gives me a similar error.

I would be grateful if someone else could test these feeds so that I can figure out whether the problem is with the feeds or my Drupal installation. And if anyone can shed any further light on the problem that would be nice!

Comments

mcd’s picture

mcd commented

The feed is fine, and I've had no trouble incorporating my blog feed into my aggregator page, so I'm assuming that there's something funky about your Apache or PHP configuration that's preventing Drupal from making http connections to its own domain. I'd look around your htaccess and php.ini files to see where "domain.dom" is coming from.

playdreamer’s picture

playdreamer commented

mcd, thanks for checking the feed.

The "domain.dom" in this case is snowgo.com, its another (virtual) domain on the same hosting account as my Drupal site and it turns out that both sites are on a machine which is behind a load balancer and cannot therefore access themselves.

Fortunately, my host was able to provide an alternative URL that works.

tejaswi.manjunath@tejas.in’s picture

tejaswi.manjunath@tejas.in commented

i am having the same problem - Aggregator can't update feeds !!!!!!!!!

bottasini’s picture

bottasini commented

Many webhosts have the function fsockopen() disabled for security reasons, therefore all the software (Drupal module aggregator included) that use that function cannot work there. I do not know why fsockopen() may be a dangerous function but I faced this limitation on several hosts.

Therefore it is not a Drupal problem but a hosting problem.