Yeah but it doesn't happen in Chrome, that's what I'm using now. I think its because https is not integrated into chrome like it is in FF.
no, it is. as i said, i get a similar message in Chrome.
i would rather suspect one of your regular malware infections changed a few phishing-related security settings on all your installed browsers and the (maybe even clean) install of the new FireFox version fixed that at least for this browser.
but the bottom line is: there is no point in trying to connect via https when WC does not support it anyways. just go to http://www.wincustomize.com