This might be related to the HTTP => HTTPS redirection we started to enforce yesterday. I disabled it for the time being. Can you confirm that it works, now?