Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
Recently I have been getting a lot of logins fail with "not supported method". This is with internet explorer 9 and from the main myverizon page. e.g.. Going initial to http://www.verizon.com/myverizon . Tried clearing cache but it didn't help. Usually I have to jump to another page such as the forum pages and do the signon there.
I've been having the same issue......only with Google Chrome. I don't typically have an issue with IE, but it is a bit cumbersome to have to open another browser just to be able to log into my Verizon account........
Reports are they put in a fix yesterday. We'll see if it works. So far haven't seen the "not supported method" or some of the other fluky things today.
tns, is this a "Verizon" fix that you are referring to? My sign in is now working, too.
Yes, verizon fix. Based on comment from Microsoft on their fix, their was a need to respond to a indicator that a response was split across mutliple responses. Essentially a partial response was being assumed to be a complete response (which before the microsoft fix it was), but a inicator showed additional info was in anther packet.
Looks like the problem was introduced with the Microsoft fix KB2585542. Not sure if Chrome might have done something sooner that causes it to have a problem, or if the Microsoft code is used by Chrome. It is a fix related to a problem in the underlying SSL/TLS but is causing trouble in lots of places.
Apparently Verizon has now made changes that at least fix IE. Need to hear from Chrome users.
tns, are you aware if Verizon ever acknowledged this patch issue for its customers that use IE?
They acknowledged a problem but I didn't see them say details.
Several other sites and some VPN acknowledged a problem introduced with the Microsoft fix, and have fixed it or stated they are working on it.