Choose your cart
Choose your cart
Receive up to $500 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $500 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 12/23/22 and 2/16/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met. Excludes Verizon Prepaid plans.
$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.
Lumia 735. I am unable to access My Verizon Mobile using the app. It has never successfully connected, always returning "The connection to the server was unsuccessful"-- not particularly helpful. OS is Win 8.1 update 2. All other functionality on the phone appears to work-- although web traffic is slow.
Oiboy, being able to use the mobile application while on the go can certainly come in handy. When you attempt to use the application are you connected to the data network or WiFi? What zip code are you located in?
ChrisM_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!
Mysteriously, without any known action on my part, the app started working on the day after I posted the issue. At the same time, the Verizon voicemail app started working too. When they started working, and previously when they weren't, both were using WiFi instead of cellular. The area code was 94611. Even though I can't explain it, no further action seems required. Since the failure was always returning the unhelpful 'server error' message, my best guess is that there actually was a problem with Verizon's end.