I experienced the same problem... stumbled upon this thread and quickly realized I was not alone. I, too, tried calling the bogus automated customer service line. It advised me to use internet explorer, which I tried against my better judgement. I can expect problems in chrome from time to time, but I've never had any trouble at all with firefox. But as advised, I took a shot with IE and was still running into the same problem.
I even purposely entered the wrong password to see if the error message would change, which it did... so that gave me some hope.
I have an older Chase pay card and used to access account info via a different URL (myaccount.chase.com) than "ucard" so I ended up calling the number listed on the back of my card, rather than the number provided by ucard. It is also an automated service, but you CAN get through to an actual human! If anyone needs that number, it's 1.866.399.2976.
I was told to go to Internet Explorer, yet again and to type the URL directly, rather than going through a search engine. This is a general practice to follow at all times anyway... accessing through search engines could open you up to phishing and other security risks. I can only assume it was just sound advise on his end. I can't imagine that it's performance would be dependent on traffic source... but again, direct is a safer bet anyway.
ALWAYS verify SSL certificates! That is one big advantage of the migration to ucard, because the old site lacked encryption of extremely important data.
I had done the exact same thing on my first [unsuccessful] attempt with IE. For whatever reason, it FINALLY worked! I was FINALLY able to get through! Since I had already attempted the same thing multiple times in multiple browsers, I can't imagine that the error solved itself organically during my brief conversation with customer support... especially since this thread is seemingly ongoing and widespread.
So, use internet explorer (I'm guessing 9 is your best bet, but some earlier versions may be alright)
Type the URL directly
If that doesn't work, definitely give them a call. It didn't work for me on my first attempt(s), but i was able to access before even hanging up the phone with customer support.
I got so caught up that I almost forgot to come back to this thread! Today was the first time I had been on this site and I did find a little comfort in knowing that I wasn't the ONLY one having this problem! I hope my input can be of help to everyone else!
