It should be fixed now; it was addressed ~30 minutes ago from the time of this post by one of our techy guys.
To reply you must either login or sign up.
