Forum Discussion
John_Heyer_1508
Jan 12, 2015Cirrostratus
I opened a support case and they confirmed it's been reported by a few customers and is likely a bug. The suggested work-around is put !AES-GCM in the cipher string.
Another work-around I discovered was prefer 256-bit AES over 128-bit. The major browsers don't support 256-bit AES-GCM, so they'll negotiate regular AES and essentially you'll never see the issue.