My Unit Is Stuck at Around 400 Kbps, How Can I Fix It?

If your unit successfully streams, but seems to be stuck at around 400 Kbps (for instance, it sends 395 Kbps, 380, etc.) and the stream doesn't really arrive to your target destination, here are the two most common issues that might cause that!

LRT Is Not On (most common)

You can see this "Stuck at" behavior if you accidentally did not enable LRT for the unit.  The reason is, without LRT on, the unit tries to send RTMP directly from the unit.  If you were using a SRT destination type, that will cause this behavior of stuck at a low bandwidth.  Make sure you have successfully purchased either an LRT subscription, or a Solo PRO Connect subscription (which includes LRT), and that on the dashboard, you have toggled LRT on and selected a Zone to use when streaming:

Your Destination Failed to Send to the Unit

A bit less common, and a bit more complex cause, if the unit itself never received the destination.  This can be caused by a temporary network failure, or more often caused by the unit being on an older firmware version that may include a known issue with the command and control connection.  Make sure you are on the latest firmware for your unit type, and then follow these steps.

1. If any destination appears on the dashboard, click the red X next to that destination to clear it:

2. Then, while the unit is online and not streaming, just set the destination again - you can use the saved destination if the destination is a type that gets saved, or just follow the steps you used before for your destination type:

Now try your stream again!