It is likely an issue with the SSL certificate not being re-issued for the new server. In addition, there is (or should be) a setting that forces non-secure access (http://) to to secure access (https://). If he hasn't already resolved this, I'll work with him to get it fixed.

He's been on vacation and I'm working tomorrow morning at 5am (PT), so hang in there please. Might take a day.

-- barry