Start with the YouTube server URL and stream key saved in Larix, then check the selected transport and whether your phone can send data to YouTube. The title alone does not identify a cause: the device, app version, network and exact error message are not known.
Work through the checks in order, changing one thing at a time. A Larix connection error, a missing YouTube preview and a connected but unhealthy stream are different states, and Live Control Room can help distinguish them.
Identify what is failing
Before changing settings, note what you see in Larix and in YouTube Live Control Room. Does Larix show an error immediately, keep trying to connect, or say that it is connected? Does YouTube receive a preview? These observations narrow the next check without proving a root cause on their own.
Record the exact Larix error text rather than reducing it to “not working”. Also note the phone model, operating system, Larix version, selected protocol and whether you are on Wi-Fi or mobile data. You may need those details if the basic checks do not resolve the problem; they are not supplied by the question, so a particular cause cannot be diagnosed in advance.
Use the Control Room state to separate connection from stream health. If YouTube receives a preview, the encoder has reached YouTube, even if the stream is not yet healthy or live. If Larix reports a connection error and Control Room receives nothing, start with the URL, key, protocol and outbound path rather than changing video quality settings.
A useful troubleshooting note can be brief: time of attempt, exact error, network in use, and whether a preview appeared. If you repeat a test, change just one setting and add the outcome. That makes it easier to tell a failed credential check from a network change or an unrelated stream-health warning.
Verify the current YouTube URL and key
Open the intended stream in YouTube Live Control Room and check the current encoder settings. YouTube treats the server URL and stream key as separate values for encoder setup. Copy the values for the stream you mean to start; an old saved connection or a key belonging to another stream may not be appropriate for this attempt. See YouTube’s encoder setup instructions for where those values fit in the workflow.
In Larix, the connection can be configured as a complete Connection URL. Softvelum documents the structure as the server or application URL followed by the stream key. Its documentation shows an RTMP example, but that example is illustrative, not a guarantee that the same URL is current for every channel or transport. Use the stream-specific URL YouTube shows for your selected stream, and take care not to add spaces, omit characters or paste the key into the wrong field. The Larix documentation explains its URL format.
If Larix has separate fields, enter the server URL in the server field and key in the key field. If it expects one combined URL, follow its current field format rather than pasting a combined address into a server-only field. Check for leading or trailing spaces when copying, and confirm that the channel and live event selected in Control Room are the ones you intend to use.
Do not assume that a key visible in an old screenshot, note or saved profile is still the right value. If the key was replaced or reset, update the Larix connection to match the current Control Room value. Keep the key private: anyone with access to it may be able to send a stream to the channel. Do not include it in a public support post or a screenshot sent to someone who does not need it.
If you have multiple Larix profiles, label them clearly so that a devotional channel, shop stream or other feed is not accidentally using another channel’s settings. A profile name does not validate the key, but it reduces confusion when you return to a saved connection after a break.
Check the transport and complete address
Compare the protocol selected in Larix with the URL supplied for the stream. A correct key paired with a mismatched protocol or incomplete address can still fail to connect. Do not replace the address with a generic example just because it looks familiar; use the current value in Live Control Room and make sure Larix is configured to use the same transport.
YouTube recommends RTMPS, the secure extension to RTMP, and Larix lists RTMPS support. YouTube’s RTMPS guidance covers the secure ingest connection and troubleshooting. This is a protocol check, not a diagnosis: seeing a timeout or SSL-related message does not tell you by itself which field or network condition is responsible.
For an SSL error or a connection timeout, recheck the URL and protocol first. YouTube’s guidance discusses port 443 for some SSL errors and recommends confirming that an encoder supports RTMPS if timeouts continue. Follow the current instructions for the selected stream and app; do not make unrelated router or phone changes before checking these explicit settings.
If you change from one transport to another, update the protocol and address consistently, then make a fresh attempt. Record which combination you tested. Avoid changing the key, protocol, network and encoding settings all at once, because a successful retry would not show which change mattered.
Test the phone’s outbound connection
A local picture in Larix does not prove that data is reaching YouTube. YouTube advises checking the outbound internet connection when an encoder appears to work locally but the stream does not arrive reliably. The phone may have a usable connection for browsing while the route or upload capacity needed for a live feed is intermittent.
First try a controlled test on the current network: keep the same Larix profile and stream settings, then observe whether the error and Control Room state change. If practical, compare with a different network, such as mobile data instead of Wi-Fi, without altering the stream URL or key. A different result is evidence that network conditions may be involved, but it still does not identify a particular router, provider or phone fault.
Check that the phone has a stable internet connection and is not moving between access points or losing mobile coverage during the test. If other uploads also fail or stall, investigate the connection with your internet provider. YouTube’s live-stream troubleshooting guide recommends checking encoder output and outbound connectivity when stream delivery remains a problem.
Larix has retry-related settings, including reconnect timing and network-presence controls, as described in the Larix FAQ. These settings influence how it behaves after a connection loss; they do not replace a correct YouTube URL and key or make an unreachable server reachable. A longer retry loop can mean more repeated attempts, not a successful ingest.
If you run a channel that must stay on continuously, a phone-based connection also depends on the phone remaining powered, connected and available to stream. For the separate problem of maintaining a stream through a household internet outage, see how to keep a 24/7 lecture stream running during internet outages in India. That is a continuity question, not a substitute for confirming this connection’s URL and protocol.
Refresh the key when startup errors call for it
YouTube’s troubleshooting advice specifically recommends getting a new stream key in Live Control Room and updating the encoder when a third-party encoder errors while starting. Follow that instruction when the error occurs at startup and the earlier URL and field checks have not resolved it. Copy the replacement into Larix, making sure the rest of the connection still uses the correct server URL and protocol.
Refreshing the key is a targeted troubleshooting step, not a universal cure. The title provides no error text, so it cannot establish that the key is the problem. A timeout, SSL error, outbound connectivity issue or a stream that reaches YouTube but is unhealthy may need a different check. If you refresh the key, keep a record that the profile was updated, but do not expose the key itself.
After updating it, make one new connection attempt and observe both apps. If Larix now connects and a YouTube preview appears, the attempt has progressed, though you should still confirm stream health before treating the job as complete. If the same error remains, move back to the error-specific URL, protocol or network checks rather than repeatedly creating keys without new evidence.
Retry and monitor Control Room
Make the next test from a known configuration: current URL and key, supported transport selected consistently, and a network that can send outbound data. Keep the phone awake and the app in the expected state for the test. Watch Larix for its connection result and Control Room for an incoming preview or status change.
If the preview appears but YouTube marks the stream unhealthy, the connection has been established; now investigate stream configuration and the warnings shown in Control Room. YouTube’s encoder settings guide covers supported protocols, codecs and recommendations such as constant bitrate and keyframe intervals. Its bitrate recommendations vary with resolution, frame rate and codec, so use the relevant official guidance and the upload capacity you can actually measure rather than guessing a high target.
Do not conflate a connected preview with a stream that is live to viewers. Follow the status in Control Room and the controls for the selected event. If the stream looks and sounds sound in Larix but delivery is absent or unreliable at YouTube, return to outbound connectivity. If no preview arrives and Larix shows an SSL or timeout error, return to URL and protocol checks. These branches make the next test more useful than changing every encoder setting at once.
For an always-on channel, a phone is often the right tool for a temporary mobile broadcast, but it leaves the stream dependent on that handset and its connection. If your actual problem is keeping a fixed video running while your computer is off, StreamNeo removes the need to leave that computer broadcasting: you upload the video and connect it to your YouTube stream key, then the channel can run without the handset staying online. For other approaches to a continuous channel, compare a VPS loop with a streaming service; the right choice depends on whether you need a live phone camera or a file-based loop.
If the issue persists, share the exact Larix message, device platform and app version, selected protocol, and whether Control Room received a preview when asking for support. Redact the stream key and any private channel details. Those facts let app support or YouTube support work from the observed failure rather than from a guess based on the word “not connecting”.
For creators considering a file-based channel rather than a mobile camera feed, how to start a YouTube stream automatically after an Azure VM reboot covers a different operating pattern. It is not a Larix fix; it helps you decide whether the phone workflow fits the channel you are trying to run.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why does Larix say it cannot connect?
The message alone is not enough to identify the cause. Check the current YouTube URL and key, the transport selected in Larix, and whether the phone can send data outbound; use the exact error to decide which branch to investigate next.
Should I refresh my YouTube stream key?
YouTube recommends refreshing the key when a third-party encoder errors while starting, then updating the encoder. It is a relevant step for that situation, not proof that every connection failure is caused by the key or that a new key will fix every failure.
What if Larix connects but YouTube shows no preview?
Check the status and selected event in Live Control Room, then confirm the stream-specific URL, key and protocol in Larix. If the encoder looks healthy locally but delivery does not arrive, test outbound connectivity; do not treat a local preview as proof that YouTube is receiving the feed.
What information should I provide for support?
Include the exact error text, phone platform and model, Larix version, transport and whether Control Room received a preview. Keep the stream key private, and say which checks you have already made so support can avoid repeating them.