This turned out to be a server issue. Sorry for the confusion.

Thanks, Steve. All is good now!