Same thing happened on my end, and I haven't made any major change in my installation—apart from updating to 1.10.

But then again, I've downloaded updates to the blacklist without any problems at all (at least three times) since I upped to b2evo 1.10 (which was like 1 or 2 weeks ago).

Maybe there's an error in the new blacklist file that causes b2evo to choke on it... who knows.

Anyone has a better idea of what may be wrong?

I have the feeling that this is a b2evolution.com issue. It has happened before only the error message was different.

I also think it's a b2evo problem as it has worked fine a day or 2 ago, and I've made no changes in quite a while.
also fails on updating the bl:

from blacklist updater:
Remote error: Invalid return payload: enable debugging to examine incoming payload (XML error: Invalid document end at line 2) (2)

Latest update timestamp: 2007-08-24 01:55:09
Requesting abuse list from antispam.b2evolution.net...

Anyone have an update on this issue.

It isn't a HUGE deal, but It would be great if it would go away. :)

http://www.thechumslick.com

Me 2.

Remote error: Invalid return payload: enable debugging to examine incoming payload (XML error: junk after document element at line 2) (2)

Debug:

antispam_poll:

---GOT---
HTTP/1.1 200 OK
Date: Thu, 06 Sep 2007 05:31:57 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.3 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
X-Powered-By: PHP/5.2.3
Connection: close
Content-Type: text/html

<br />
<b>Catchable fatal error</b>:  Object of class xmlrpcval could not be converted to string in <b>/home/antispam/public_html/b2evocore/_functions_xmlrpcs.php</b> on line <b>458</b><br />

---END---

HEADER: Date: Thu, 06 Sep 2007 05:31:57 GMT
HEADER: Server: Apache/1.3.37 (Unix) PHP/5.2.3 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
HEADER: X-Powered-By: PHP/5.2.3
HEADER: Connection: close
HEADER: Content-Type: text/html

XML error: junk after document element at line 2

Using 1.10.2 Version from scratch. Hope this helps. ;)

So...any solution???

I'm getting the same thing, not just updating list, but whenever I ban any domain.

i've just updated to 1.10.2 a couple of days ago, and getting the same error.

any solutions?

I upgraded as well, and am getting the same error

I cannot report abuse either

Baz

My b2evolution Version: Not Entered

want to update my spam list and I get this error:

Entfernter Fehler: Invalid return payload: enable debugging to examine incoming payload (XML error: junk after document element at line 2) (2)

any idea?

http://b2evolution.net/news/2006/05/12/the_new_central_antispam_blacklist#c17377 ;)

¥

@ ¥åßßå
I am running with 1.10.2 and one week ago everything worked fine. now it does not work anymore

It's nothing to do with the version of evo you're running ;)

Comment from: Francois PLANQUE [Member] Email · http://fplanque.net/
There is currently a problem with the server. We're working on it.

¥

http://b2evolution.net/news/2006/05/12/the_new_central_antispam_blacklist#c17377

(doesn't look like any developers read this forum :):):))

[originally posted to 2.0 bugs -- not a bug.. moved, tacked onto the other posts.]

Getting this for antispam update

Remote error: Invalid return payload! enable debugging to examine incoming payload. (XML error: Invalid document end at line 2) (2)

Going on for a week already I think.

Got this error while trying to Update Spam list from server

Remote error: Invalid return payload! enable debugging to examine incoming payload. (XML error: junk after document element at line 2) (2)

Any news on this being fixed?

I just installed the latest stable Florida version and am getting the same error.

It looks like it's being worked on, so I'll not worry about it for now.

I've been getting the same errors here when ban a URL or keyword and send it to the central blacklist and also when I request an update from the list via the link.

Hopefully this will be resolved soon :D

Everything is working fine now :D

Not for me....

John wrote:

Not for me....

Sorry to hear that :(
I have version 1.10.2 When I click "Request abuse update from centralized blacklist!" the incoming data updates the spam list like before.

Maybe you need to upgrade? Try logging out/in again... just an idea.

Maybe it's just an issue with b2 2.0.1 :)

It works on my test 2.0.1.alpha ;)

¥

Remote error: Invalid return payload! enable debugging to examine incoming payload. (XML error: Invalid document end at line 2) (2)
Latest update timestamp: 2007-08-24 01:55:09
Requesting abuse list from antispam.b2evolution.net...

I must need that essential bit called "test" for my 2.0.1 alpha.... :)

maybe they changed something :p I'll go check ;)

¥

*edit*
Hmmm, can't see anything obvious

I'll wait until 2.0.2 :)
Thanks for looking. I read your water cooler story while waiting :)

It doesn't look pretty but it works like a dream ;)

¥

Yabba, would it make any difference if I uninstalled and reinstalled the antispam plugin ?
The version dates for all the antispam files I could find are the same so it does appear there is no update...
Maybe it's just an anti Australia thing :)

It might help, but I don't have the antispam plugin installed, so you might want to try an update whilst it's uninstalled

¥

Made no difference..
I'll see what happens when 2.0.2 comes out

hah hah!!!
It was the "leave Australia till last" regional delay bug :)
The thing just decided to start working

Yeah, we weren't sure how to break the news to you ;)

¥

Hooray it's working again.