Bugzilla – Bug 15025
bad proxy setting causes "connect timed out" message (was: Unable to login to mysqueezebox.com through squeezeserver)
Last modified: 2010-03-02 22:31:27 UTC
Ive just installed Version: 7.4.2 - r29092 @ Sat Oct 31 04:00:55 PDT 2009 on a fresh install of kubuntu 9.10 I can log on to www.mysqueezebox.com through a browser, however not through squeezeserver. After entering email and password in squeezecenter and pressing apply I immediately see "Invalid mysqueezebox.com username or password." error message. In server.log (attached) I see corresponding entries [09-11-02 20:22:31.8605] Slim::Networking::SqueezeNetwork::_error (447) Unable to login to SN: Connect timed out: [09-11-02 20:23:54.7050] Slim::Networking::SqueezeNetwork::_error (447) Unable to login to SN: Connect timed out: [09-11-02 20:31:01.0495] Slim::Networking::SqueezeNetwork::_error (447) Unable to login to SN: Connect timed out: "timed out" seems unlikely to be accurate - the log entry (and then error message) appear instantly. The mysqueezebox.com user name is squeeze@tarind.com
Could be this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/417757 ?
No difference after switching to a local resolver, which I believe eliminates that ubuntu bug.
Created attachment 6255 [details] server.log
Andy notes that this is often due to network problems. He wants to fix the error message.
Created attachment 6293 [details] strace of squeezeboxserver while failing to login to SN Ive tried using strace on the squeezeboxserver process while submitting this form. Output attached. A couple of things stand out: 1. It reads the whole of /etc/services. I wonder what it is looking for? 2. There is no outgoing network activity during this period. I wonder if it has cached some error from a previous access?
Michael/Andy: does the attached trace log help at all? Please let me know what testing you would like me to do. I was able to log in from my ubuntu VM just fine, so am unable to replicate this issue yet. Toby: when you installed SBS, did you install in the 'default' location or choose a different install location?
Try enabling network.asyncdns and network.asynchttp debug logging.
Aha! With network.asyncdns and network.asynchttp debug logging enabled, the log showed it was trying to use a proxy. Sure enough, there is a web proxy set in the server settings, but in hostname:port format, not the xx.xx.xx.xx:yyyy format as suggested in the help. I'm not sure how the proxy setting got there; I dont remember doing that manually :-( mysqueezebox login works after changing that hostname to ip address, or after blanking this setting (I dont really need squeezeboxserver to be using the proxy). Thanks for your help
Great, we definitely need to improve the error messages there...
*** This bug has been marked as a duplicate of bug 15432 ***