Hi and thank you for your work on this module. Many appreciate it.

I have received messages from Mollem.com (below) regarding "sending invalid IP addresses to the Mollom servers".

I am confused if this relates to Boost or Rackspace Cloud, and I am not sure how to test. I wrote Mollem last week but have not received a response.

Can anyone offer some guidance and tips on how I can test this myself?

Thanks, Jerry

~~~~~~~~~~~~~~
Hello xx,

we just noticed that something might be wrong with your server configuration at ....

Your site is sending invalid IP addresses to the Mollom servers. Mollom uses IP address information to maintain IP address reputations, and uses those reputations to help block spammers. Because your site is sending us invalid IP addresses, Mollom is less effective in blocking spam on your site. Sending Mollom the right IP addresses is important, so we highly recommend that you look into this problem. I included some technical details below.

In most situations, this problem is caused by the fact that your site is running behind an HTTP accelerator (e.g. Varnish), a reverse proxy (e.g. Squid), a load balancer (e.g. Nginx), or a content delivery network (e.g. Akamai). When one or more of those are incorrectly configured, the Mollom plugin installed on your site will send internal IP addresses (e.g. 127.0.0.1, 10.0.1.1 or any other LAN address) instead of the actual IP addresses of your site's visitors. It is important to send the visitor's IP address so make sure things are properly configured.

In addition, content management systems like Drupal provide a configuration setting that should be used to instruct Drupal about the fact that your site is running behind an HTTP accelarator, a reverse proxy or a load balancer. This is an explicit setting to prevent IP spoofing attacks -- if you don't configure your content management system correctly, it will continue to use the wrong IP address. That or your site is vulnerable to IP spoofing attacks and that is affecting Mollom's efficiency on your site. Make sure that you upgrade to the latest version of the Mollom plugin, and that your content management system is configured properly because it will affect more than just the Mollom plugin. (If you are using Drupal 6 or later, search your settings.php file for 'reverse_proxy'. If you are using Drupal 5, you need to make some custom changes to your setup.)

If you have questions about Mollom, suggestions for improvement, or if we can offer any assistance please don't hesitate to contact support at support@mollom.zendesk.com. When you do, please mention your site's public key (xxx).

--
Dries Buytaert
Co-founder Mollom
http://mollom.com
~~~~~~~~~~~~~~

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Postponed (maintainer needs more info)

My guess is it has to do with the cloud. Nothing is in front of Apache, thus the IP address shouldn't be changed. Look into the admin/reports/dblog and look at the IP address stored in each entry, they should be different. If they are not then you need to edit your settings.php file and add in the IP address (it should be the same for every entry, and the IP should be a computer in the cloud)

Add to the bottom of your settings.php file:

$conf = array(
  'reverse_proxy' => TRUE,
  'reverse_proxy_addresses' => array('10.0.0.1',),
);

Replace 10.0.0.1 with the upstream IP address from within the cloud.

Dries’s picture

Dries CreditAttribution: Dries commented

I don't think Boost can be the source of this problem.

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno as a volunteer commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

I am closing this issue, as it has been created for a release that is now not supported.