Getting this error in the manager: XML tag name mismatch (expected LI)

Has anyone else gotten this error? It's just started happening after I updated their site to Revolution 2.2.4

PHP Version 5.3.6-6~dotdeb.1
mysql 5.1.57

Error text:
XML tag name mismatch (expected LI)
ERROR
The requested URL could not be retrieved

while trying to retrieve the URL http://www.astrabridal.co.nz/connectors/system/registry/register.php
The following error was encountered
Zero Sized Reply
Squid did not receive any data for this request



My clients are getting an error in various places (randomly) in the manager of their live site. It does NOT stop them doing anything, but it's occurred on login, adding images and creating new news resources.

They are using Firefox and IE on a PC. I am on a

oops, posted before finishing. I am on a Mac, accessing from a different country, and i've never seen the error. I am not sure if this is ISP related, modx related, or server/hosting related. Would appreciate it if anyone has a clue what it might be.

I don't think this is a problem with MODX itself, but rather with the server.

https://www.google.com/search?q=squid+did+not+retrieve+any+data&aq=f&sugexp=chrome,mod=12&sourceid=chrome&ie=UTF-8#hl=en&sugexp=les%3B&gs_nf=1&tok=VBMF-QdqP1MZi0kV0eEiaQ&pq=squid%20did%20not%20retrieve%20any%20data&cp=17&gs_id=k&xhr=t&q=squid+did+not+receive+any+data+for+this+request&pf=p&sclient=psy-ab&oq=squid+did+not+recieve+any+data&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=4f21c71138c3d6ce&biw=1413&bih=868&bs=1


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Considering that only the clients are getting the error, while rachelmarama1 is not, it's more likely that it's the client's ISP or a local (to the clients) network proxy server that's causing the problem.

I ran across the same issue once when a client was out of town and using a hotel wifi hotspot. He got quite irate because I wasn't fixing the error. I don't know if he ever did understand that it wasn't his site, it was the hotel's hotspot service that was causing the problem.