McBuff

Thanks itman. . .right in front of my face!! That fixed it. . .except the wildcard Adorama gave me .adorama.com/* didn't work. The Eset instructions said the proper rendering should be *adorama.com* That one worked!

Here's what the Adorama rep emailed me. Adorama says: "Our IT team is still currently working on this with ESET. In the meantime, ESET technical support shared that adding the website wildcard .adorama.com/* in the exclude SSL section should make the website accessible again. " I have no idea what it means. Adding "the wildcard?" Where is the "exclude SSL section?". . .no clue. . .perhaps someone can make sense of this for me. . or give it a try to see if it works. . .honestly it would seem Adorama would be a little more motivated to fix this. . .especially this time of the year.