In previous versions it was impossible to know what was happening with users since we
did not have any message from the lower level software layer (xmlrpc). So, I decided
to show to the user the content of this exception. Unfortunately at this time I can
not handle all possible exceptions to show to users only nice self-explanatory
messages. Worst: I am not sure if I can map all messages. 

I tested the condition "proxy enable but no configured+postupdate" and the message
was "errno socket error (61,'')". Yes, it is a debug message, but it is clear (for me):

61 : ECONNREFUSED : An attempt to establish a connection was rejected. This error
typically occurs with TCP when no passive open on the address is pending on the peer
system.

I will put this issue as low priority until I have time to test all conditions and
map all messages.

Thanks
This way, I can say to the user "please, check your proxy or access point".