Yesterday I updated to Mollom 6.x-2.6 while at the same time also applying the latest Drupal 6 security update. Now Mollom no longer connects to the Mollom servers, giving the following error message:

"The Mollom servers could not be contacted. Please make sure that your web server can make outgoing HTTP requests."

I have checked with my ISP but they have had no updates and there is no issue that would stop the server making outgoing HTTP requests. I have also waited five hours in case the Mollom servers are down but they do appear to work. Until this is solved Mollom effectively becomes useless.

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

+1. I updated the core and Mollom yesterday too.

Now I get this: API keys could not be verified.
Error 900: Network error.

And about hundred spams as a side effect.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

I get about 2-4 spam comments per minute, so just had to disable comments for the time being - even with moderation that is impossible to handle...

aspatz’s picture

aspatz CreditAttribution: aspatz commented

Hello,
i had the same problem, after updating to the current drupal 6 core release (Drupal core 6.29) and updating Mollom 6.x-2.6.
The two errors occure:
==============================
Retrieved new CAPTCHA
Error 900: Network error.

API keys could not be verified.
Error 900: Network error
==============================
I verified the API Keys. They are valid.
Please help. I was overflowed with spam.
Kind regards, Arnold

patten’s picture

patten CreditAttribution: patten commented

same here, on a D6 and D7

JamesOakley’s picture

JamesOakley
he/him/his
Primary language English
Location Kent, UK
CreditAttribution: JamesOakley commented
Status: Active » Closed (duplicate)

This sounds like a duplicate of #1608844: Timeout contacting Mollom servers (network error 900)

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Closed (duplicate) » Active

First of all thank you for pointing me to the other bug report; I have applied the fix suggested there and it works, so this is a duplicate. However, will marking it as a duplicate really ensure the issue is resolved? After all the other bug is listed in relation to the D7 version. I'd hate this to be lost and not updated in the new D7 and D6 versions...

JamesOakley’s picture

JamesOakley
he/him/his
Primary language English
Location Kent, UK
CreditAttribution: JamesOakley commented
Status: Active » Closed (duplicate)

Please don't take this as an edit-war. I'm setting this back to "Closed (duplicate)", but it's the last time I'll do this - if you feel it should stay open, just set it back to Active and I'll leave it like that.

If this issue is truly the same, then we can leave it to the other issue. Yes, the other issue is set to 7.x-2.x. But the Mollom 6.x release won't get lost in this. The Drupal workflow is to work on the highest version first. Solve it for Drupal 8, then backport to Drupal 7, then to Drupal 6. Drupal 6 is still a fully supported version, so after the other issue solves this for Drupal 7, the issue will be set to "needing backport", and the fix will be applied to Drupal 6.

One could argue I should set the other issue to 8.x. But there isn't an 8.x-2.x-* branch for Mollom yet, so it is on the highest version available.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Thanks, James. That's all I wanted to ensure. Apologies if it was unnecessary.

JamesOakley’s picture

JamesOakley
he/him/his
Primary language English
Location Kent, UK
CreditAttribution: JamesOakley commented

No apology needed - the Drupal site is (or should) be a place where we can discuss the best way to move things forwards, not a place where we shoot each other down for things!