Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

I am getting an error in the console, and the game.
Painsley Lytton
Registered User
Join date: 10 Mar 2007
Posts: 1
03-24-2007 12:59
2007-03-24T19:35:51Z INFO: LLUserAuth::authenticate: uri=https://login.agni.lindenlab.com/cgi-bin/login.cgi
2007-03-24T19:40:52Z ALERT: LLXMLRPCTransaction CURL error 52: Empty reply from server
2007-03-24T19:40:52Z ALERT: LLXMLRPCTransaction request URI: https://login.agni.lindenlab.com/cgi-bin/login.cgi
2007-03-24T19:40:52Z INFO: Processed response: 52
2007-03-24T19:40:52Z WARNING: Alert: [ErrorMessage]
2007-03-24T19:40:52Z WARNING: Alert: Unable to connect to Second Life.
2007-03-24T19:40:52Z Despite our best efforts, something unexpected has gone wrong.
2007-03-24T19:40:52Z
2007-03-24T19:40:52Z Please check www.secondlife.com/status and the Second Life
2007-03-24T19:40:52Z Announcements forum to see if there is a known problem with
2007-03-24T19:40:52Z the service.
2007-03-24T19:40:52Z WARNING: Unknown control type web_browser

This showed up in the console, and i got the same message on the actual there client.
Alderic LeShelle
Registered User
Join date: 28 Dec 2006
Posts: 104
03-24-2007 23:52
From: Painsley Lytton
2007-03-24T19:35:51Z INFO: LLUserAuth::authenticate: uri=https://login.agni.lindenlab.com/cgi-bin/login.cgi
2007-03-24T19:40:52Z ALERT: LLXMLRPCTransaction CURL error 52: Empty reply from server
2007-03-24T19:40:52Z ALERT: LLXMLRPCTransaction request URI: https://login.agni.lindenlab.com/cgi-bin/login.cgi
2007-03-24T19:40:52Z INFO: Processed response: 52


Login server didn't respond correctly - usually because of being a bit stuffed. Though there may be some other reasons...

* Firewalled?
* Misconfigured proxy settings? (YES, the environment variables http_proxy and https_proxy ARE honored)
* Misconfigured proxy?
* Proxy not passing through the login request?

You may try using the given URL in your favourite browser - it should respond with a "405 Method not allowed". If it does not, check your network settings first.
But if it does, there's still the possibility of a proxy passing through ordinary HTTP-Requests but not the XML-RPC request the login server wants to see.