Comment 27 for bug 844369

This issue still pops up quite often for me too, however, it does seem that it works the next automatic try or thereafter. Maybe it's because of a server load issue, rather than a client issue?