Bugzilla – Bug 15432
Proxy settings not reset
Last modified: 2010-04-08 17:24:43 UTC
Not certain that this is a fundamental bug - or simply a request for better logging. - Michael Herger sugesting in forum that I raise this. Error in server.log - variations on a theme of Connect timed out: Bad file descriptor Problem traced to: SQC was picking up a disabled IE/Win proxy setting. I had set up a local proxy for a while - but disabled it. However, SQC continued to use it. A reboot later and I did not restart my local proxy server because I knew that I didn't need it any more ... but had not realised that SQC was still using it. Couple of days later ... enabled debug logging in SQC and saw: Slim::Networking::Async::HTTP::new_socket (74) Using proxy localhost:8080 to connect Restarted local proxy server and all is well. So - did I set it up in SQC some time ago and forget about it ... (I see it in SQC settings/advanced/network/proxy) or did SQC (or installer) copy it when it was enabled and not notice it was disabled? Registry shows that proxy is disabled: HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings\ProxyEnable=0 and HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings\ProxyServer=localhost:8080 If not a bug - in that perhaps it was me who put the proxy setting in SQC and forgot all about it - then how about putting the fact that a proxy is attempting to be used in the logs at start-up - or on network comms failures.
== Auto-comment from SVN commit #29758 to the slim repo by michael == == https://svn.slimdevices.com/slim?view=revision&revision=29758 == Fixed Bug: 15432 Description: if network accesses fail and a proxy is configured, log some hint for the user. This should help troubleshooting networking issues.
Paul - we can't really reset the proxy settings, as we can't know whether this is what the user wants. But adding some hint to the error message should help you recognize the issue when it happens. FYI: I've been a victim of this issue myself. I've been blaming the latest AV update for the trouble, but forgot that I've been testing some proxy issues at some point...
*** Bug 15025 has been marked as a duplicate of this bug. ***
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!