Hi Steven,
This turned out to be an issue with the password protection on our page. When that was removed, the problem was resolved.
Thanks!