Error Code Keeps Reoccurring: PLYB-122

Again, only having Fios installed for a week, there are numerous issues. Freezing at various times (sporadic); Some pixilation and the inevitable Error Code: PLYB-122.

* Exactly what is that error code: PLYB-122?

Verizon stated it was PLYB-123 and never heard of PLYB-122. Another Verizon representative stated they never heard of it. And, another Verizon representative stated it was PLYB-123 and not PLYB-122 when in fact it was PLYB-122. This error code has been associated by a 'loose' connection as stated by Verizon. However, there was no loose connection. In being in the electronics arena for over forty years, I find Fios support truly lacking in any knowledge and it really seems that the alleged troubleshooters are merely trying to pass off comical solutions. That is the world we live in as I expected nothing less.

Accepted answers

Albrean_VZ

Hi Synoptic, sorry you are experiencing this issue. Error code PLYB-122 happens when your fiostv+ client can't currently communicate with the DVR. Please visit our contact us page to connect with technical support to troubleshoot this issue.

All comments

Ccanino53

@Synoptic12
wrote:
Again, only having FIOS installed for a week, there are numerous issues. Freezing at various times (sporadic); Some pixilation and the inevitable Error Code: PLYB-122.
* Exactly what is that error code: PLYB-122?
Verizon stated it was PLYB-123 and never heard of PLYB-122. Another Verizon representative stated they never heard of it. And, another Verizon representative stated it was PLYB-123 and not PLYB-122 when in fact it was PLYB-122. This error code has been associated by a 'loose' connection as stated by Verizon. However, there was no loose connection. In being in the electronics arena for over forty years, I find FIOS support truly lacking in any knowledge and it really seems that the alleged troubleshooters are merely trying to pass off comical solutions. That is the world we live in as I expected nothing less.

If you checked for tightness, there is a possibility one of the connectors was installed incorrectly, or a bad splitter was used. All the splitters should be MoCa 2.0 certified, if not the installer used the wrong splitter and it should be replaced. Also look for open ports on a splitter and use a terminator if found. You could also try running this and see what it comes up with:

Main Menu > Customer Support > Top Support Tools > Fix FiOS TV Issues

Synoptic12

"If you checked for tightness, there is a possibility one of the connectors was installed incorrectly, or a bad splitter was used".

* No, there is nothing wrong with any connectors and there is no 'bad splitter'.

"Also look for open ports on a splitter and use a terminator if found".

* There are 'no' open ports.

Ccanino53

@Synoptic12
wrote:
"If you checked for tightness, there is a possibility one of the connectors was installed incorrectly, or a bad splitter was used".
* No, there is nothing wrong with any connectors and there is no 'bad splitter'.

"Also look for open ports on a splitter and use a terminator if found".
* There are 'no' open ports.

If it isn't a physical connection issue, then it has to be an equipment issue. Try powercycling everything, powering up the router first, then the boxes. If that doesn't work you could have a bad VMS box or a bad ONT. Contact support on "X" or try https://www.dslreports.com/forum/vzdirect.

Synoptic12

"If it isn't a physical connection issue, then it has to be an equipment issue. Try powercycling everything, powering up the router first, then the boxes. If that doesn't work you could have a bad VMS box or a bad ONT".

* Verizon replaced the entire box inclusive of the ONT. I really do not know what the router has to do with the TV.

Gillville7764

I'm having the same issue, despite my Wi-Fi signal being strong.

How is there no one at Verizon that has any clue what this error means? Obviously a developer put that in the box intentionally. It doesn't get there by mistake.

Really poor internal communication from Verizon on this.

Ccanino53

@Gillville7764
wrote:
I'm having the same issue, despite my Wi-Fi signal being strong.
How is there no one at Verizon that has any clue what this error means? Obviously a developer put that in the box intentionally. It doesn't get there by mistake.
Really poor internal communication from Verizon on this.

Are you having these problems on a mini or on the VMS box? If it is a mini is it connected via WiFi or cable?

MLeo19

Same error code- PLYB-122.

We were told by an off duty Verizon tech guy it's plain & simple bad equipment.

Ours was installed by Verizon in December, and they had a lot of issues, had to replace the VMS box 3x before it worked. Too many issues with this company. I was on the phone with them or chatting DAILY the first 3 months after installation!

SMACKATTACK

Can someone from Verizon please respond to this PLBY_122 issue? I spent three hours today calling tech support and probably another 16 hours over the past 6 months. I even called to cancel my service but was told that I would be charged for the remaining months on my contract - for a service that doesn't work! This is crazy. Verizon shouldn't be sending out equipment to customers when they don't even know what these error codes mean. Please, I’m begging. Someone at Verizon must have a solution. Crazy.

Ccanino53

I'll run this by tech support and see if they have an answer. Meanwhile post here and see if they can help:

https://www.dslreports.com/forum/vzdirect

Ccanino53

@SMACKATTACK
wrote:
Can someone from Verizon please respond to this PLBY_122 issue? I spent three hours today calling tech support and probably another 16 hours over the past 6 months. I even called to cancel my service but was told that I would be charged for the remaining months on my contract - for a service that doesn't work! This is crazy. Verizon shouldn't be sending out equipment to customers when they don't even know what these error codes mean. Please, I’m begging. Someone at Verizon must have a solution. Crazy.

A somewhat cryptic answer from tech:

PLYB_122 is the client reporting that it is not able to reach the VMS4100ATV. So either the VMS is dropping offline, or it is not activated; or perhaps a token refresh type issue.

Are you using a 3rd party router by any chance?

lgibson3925

I too have had this error since I was forced to send my old box in and update to this new equipment. No one can give a straight answer, I have spent countless hours on the phone with them and chatting online to no avail. Rebooting everything works for a day if I am lucky but I should not have to reboot every other day. Please fix this. You are going to lose a ton of customers.

arizonakay

My new error code is PLYB_100

”Channel Not Available”

ArpitKuzo31

Is anyone found real solution?

Albrean_VZ

Jpod1

Same issue here- PLYB-122.. Just upgraded to new equipment and this started happening. It’s unacceptable for the cost of this service. We will be switching services if this continues

Synoptic12

Over one year and experiencing the "same" problem {PLYB-122}. In addition there are various screen messages across the screen:

1.) Please wait while trying to tune channel.

2.) Finish setting up tv.

I've tried 'resetting several times to no avail. I've disconnected the router and set top box (new box) with no change. And, there are three round white circles at the bottom left screen continually going left to right (non-stop).

Again, over one year without any success in rectifying the problem by Verizon. Verizon is due to arrive tomorrow. I've been on the phone with Verizon for well over three hours speaking to various people accopnpanied by a supervisor named George. To say the least I've never had any issues with Cox for over thirty years (the family). I did not make the decision to switch rather other family members. One of the Verizon customer service personnel if not two stated it was a frequency issuse of the box not communicating with the device.

I tried inquiring of the reason via telephone and one advisor said it may need an 'extender'. Actually, that is convoluted as we've had Verizon for a little over a year with no real issues of the signal irrespective of the PLYB-122 code which allegedly states that the code is a 'frequency' issue according to George 'Supervisor'.

* At this point, there is no signal at all, none; rather the three solid white dots moving from left to right or vice versa. I've tried all resets to no avail. Reset all applicable settings adjoined to any faults including updates and "none" were successful. The Wi-Fi connection showed a 'good' signal. I'm miffed at this point. The only conclusion is that it may be that 'wonderful' set top box most likely "Made in China" which will be the demise of this nation. All replies are appreciated.

*** Addendum:

The VMS while checking keeps buffering so that may be the issue, unsure.

The TV has gone out at usually the same time (7:30-8:30 PM) and came back usually within a few hours but it has now been about 24 hours and the TV is "OUT"!

** I do not know whether it is relevant but when 'troubleshooting' the VMS the VMSI 0265 keeps buffering and will not show successful.

Synoptic12

Thanks for that valuable info.

Ccanino53

Hopefully the tech that comes will be able to sort it out for you. Sounds like some bad equipment.

BGR1960

Experiencing these exact same issues and pains Synoptic12 for a couple months (since upgrading to these "new and improved" wireless set top boxes). Have tried this MoCA adapter thing that was suggested but has not helped. Next trying a splitter with amplifier but not holding my breath. Verizon going down hill very fast!!!

Synoptic12

I agree with you. The new 'wireless' set top boxes really require better circuitry.

Irish_Whiskey

I may have a solution. I have two TVs. One worked perfectly. The other constantly froze and disconnected with the PLYB_122 error code. In comparing Network Status settings I noticed that the good TV was connected to "MyWifi-TV". The PLYB_122 error TV was connected to "MyWifi". There was no "-TV" in the connection name.

I did the following on the problem TV: go to Settings. Select Network Status. Select Network Setup. Press "OK" on Network Setup. Select the current wifi network and press OK. Scroll down and select "Forget Network". This will remove the current wifi connection and start the auto-connect process.

I waited about 30 seconds and then used the back arrow to go back to the Network Status screen. The connection now showed as "MyWifi-TV". I exited and resumed watching TV. There has been no buffering, disconnecting, or error codes since. Granted, it's only been a few days without issue, but previously the PLYB_122 error was daily and constant, so I think I may have solved it.

If your Network Status wifi connection name shown on your TV doesn't have "-TV" at the end of it , try the above. Hope it works for you.

RKM77

After months of agony, we seem to have fixed the notorious PLYB_122 error we were having in our house. We noticed that the streaming box closest to the Verizon G3100 router never had issues but the streaming boxes that were connecting to a WiFi access point in another part of the house (which was connected to the Verizon router through the house's ethernet wiring) kept having connectivity issues even though the WiFi signal from the access point was strong and had 2.4 and 5 GHz. We realized that our access point was older (pre-WiFi 6) and decided to replace it with a new WiFi 6 access point (Verizon G3100 router uses WiFi 6) and these streaming boxes work perfectly now. If your streaming box is connecting to a pre-WiFi 6 access point, we suggest upgrading the access point to WiFi 6, it worked for us.

This is the access point we bought...

https://www.amazon.com/dp/B0CNSCVXZN?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

Plekcebo767

This new equipment push seems rushed and forced upon us. Nothing but trouble, service, and picture quality is worse. Buggy software, hardware...poor design (all grey minimal lights remote). Overly complicated guide and navigation. Google forced down our throats every 2 minutes. All this and more increases each month. I also think it killed my Roku TV somehow. It was working fine until the new setup, and it gradually died after numerous issues connecting with the new equipment.