“Starting” is a status, not a diagnosis. To find why a Castr YouTube stream appears stuck, check the path in order: encoder, Castr source ingest, Castr’s YouTube destination, then YouTube Live Control Room.
Write down the exact status and error text you see at each stage before changing settings. Castr receiving a source feed does not necessarily mean that YouTube has begun broadcasting, and a YouTube prompt such as “connect your encoder to go live” is not the same status as Castr’s source status.
Record what each screen says
Open the Castr stream dashboard and note the source status, whether a preview is visible, and whether the stats bar has appeared. Castr’s setup guide describes the source moving from Connecting to Connected when Castr locks onto the incoming feed. Record the precise wording rather than summarising both states as “starting”. A status can mean different things in different products, and the title of this article does not establish which stage is waiting.
Next, note whether the YouTube destination is enabled or connected in Castr, and whether the intended channel or event is selected. Then open YouTube Live Control Room for the relevant broadcast and record whether it shows a preview, asks you to connect an encoder, or is waiting for you to click Go live. Include any error text verbatim, along with the time you observed it and your time zone.
These observations form a simple decision path. If Castr has not changed from Connecting and has no preview or stats, investigate the encoder-to-Castr connection first. If Castr shows the source but the destination is inactive, inspect that destination’s method and settings. If YouTube shows a preview but the scheduled event has not gone live, follow the Live Control Room sequence. The YouTube live streaming guide can help if you need to distinguish an encoder feed from the separate act of starting a YouTube broadcast.
| What you observe | Where to check next |
|---|---|
| Castr source remains Connecting; no preview or stats | Encoder output, server URL, stream key, protocol and network path to Castr |
| Castr source is Connected; YouTube destination is inactive | Destination toggle, selected channel or event, and connection method |
| Castr source and destination appear active; YouTube has no preview | Correct YouTube event, server/key details if entered manually, and current status messages |
| YouTube preview appears for a scheduled stream; broadcast is pending | Follow Live Control Room’s on-screen steps, including Go live when prompted |
| Source status or health changes repeatedly | Encoder stability, bitrate and dropped-frame data, network conditions, and Castr’s live status page |
This table is a routing aid, not a promise that one symptom always has one cause. For example, a missing preview could reflect a wrong destination configuration even when the source is flowing, while a source that repeatedly disconnects calls for encoder and network checks before you revisit YouTube.
Confirm the encoder is sending
Start with the software or hardware that produces the stream. Confirm that it is running, is streaming rather than merely open, and is sending to the current Castr server URL and stream key. If your Castr setup uses a selected region or protocol, verify that the encoder is configured for those values. A key copied from an earlier test, another region, or a different destination can make it appear that the encoder is active while the intended Castr source receives nothing.
Do not regenerate or replace credentials just because the screen says “starting”. First compare the configured server and key with the values shown for this specific Castr source. If you do change a value, update the matching field in the encoder and check the result in Castr before changing anything else. Keeping one change at a time makes it easier to identify which stage moved.
Check the encoder’s own output state and any logs it exposes. Does it report that it connected to the server, or does it show an authentication, connection, or network error? The encoder can report that it is sending while Castr still has not locked onto a usable feed, so use Castr’s source status and preview as the receiving-side evidence. In Castr, look for the transition from Connecting to Connected and check whether the stats bar becomes active. Castr’s guide to starting a live stream covers the basic path of putting the Castr server details into an encoder; the same distinction is useful whether your encoder is on an old laptop or another machine.
If the encoder is sending but Castr never shows a source, check the selected protocol and region as well as the exact values. Avoid assuming that a YouTube stream key belongs in the encoder when the encoder is meant to send to Castr: in that arrangement, the encoder should send to Castr, and Castr handles the onward YouTube destination separately. If you are not sure which key belongs in which field, pause and identify each connection in the dashboard before trying again.
Check whether Castr receives the source
Castr’s source status is the key dividing line between the input side and the onward destination. If it says Connecting and no preview or stats appear, the destination is not yet the first question to answer. Confirm the encoder is addressing the intended Castr source, then examine whether the feed is reaching it steadily. If the status becomes Connected, Castr has locked onto the source; continue down the path rather than treating that state as proof that YouTube is live.
When Castr does show a source but it repeatedly drops, inspect its Health Charts for bitrate changes and dropped frames. A feed that appears briefly and then vanishes is different from one that never arrives. Record the times of the drops and compare them with encoder logs or network changes. That timeline can help distinguish a sustained connection problem from an isolated interruption.
Castr’s troubleshooting guidance recommends upload capacity at least 1.5 times the stream bitrate. Its example is a 5,000 Kbps stream with 7,500 Kbps (7.5 Mbps) upload capacity. Treat those as Castr’s guidance and example, not a measurement of your connection or a guarantee that a particular stream will remain stable. If the link is shared, other uploads, cloud backups, or video calls can use capacity while the channel is running.
Where the computer or encoder supports it, a wired Ethernet connection can reduce the variability associated with Wi-Fi. It is a useful network check, not a fix for an incorrect key, disabled destination, pending YouTube broadcast, or service incident. You can also close bandwidth-heavy applications and choose an ingest location near the broadcaster if that choice is available in your setup. Castr says SRT may be worth considering when RTMP is unstable because it can recover from packet loss automatically; changing protocol is a deliberate test, so confirm that both ends support and are configured for the same choice.
Castr also publishes encoder recommendations: H.264/AVC video, AAC audio, constant bitrate (CBR), a two-second keyframe interval, and 1920×1080 or 1280×720 resolution. It suggests 30 FPS, or 60 FPS if the connection can support the higher bitrate; listed video bitrate guidance is 3,500–6,500 Kbps for 1080p and 2,500–4,000 Kbps for 720p, with 128 Kbps stereo audio. These are Castr’s recommendations, not universal requirements or settings independently tested for your equipment. If the feed is stable and Castr reports Connected, avoid changing encoding settings simply to address a YouTube destination or control-room state.
Verify Castr’s YouTube destination
Once Castr shows the source, inspect the destination that sends it onward. Castr documents two ways to set up YouTube: connect through the YouTube API and choose an event, or enter a YouTube streaming server and key manually. Identify which method you used, then check that the intended YouTube channel or scheduled event is still selected and that the destination is enabled.
With the API method, check that the channel connection remains in place and the intended event is chosen. With manual server-and-key entry, compare the values against the specific YouTube stream you intend to use. Do not treat a successful Castr source connection as validation of these separate destination values. If you edited the description while using the manual method, Castr’s guide notes that you need to make that description change in YouTube.
Castr’s specific troubleshooting tip is to turn destinations off while the source is offline, then turn them on again after the encoder source is live. If you follow that sequence, observe each state: first make sure Castr has the source, then re-enable the intended destination and check whether its status changes. It is a targeted check for the hand-off, not a reason to keep toggling a destination whose selected event or credentials are wrong. Castr’s YouTube connection instructions describe the documented connection methods.
If the destination looks connected but YouTube still has no preview, check that the destination points to the event open in Live Control Room. A mismatch between a scheduled event and a different stream’s key can leave the right-looking screens open for the wrong broadcast. Confirm the event name and channel in both places rather than relying on a general “connected” label.
Complete YouTube’s Live Control Room steps
YouTube Live Control Room is a separate stage from Castr’s source and destination. For a scheduled stream, the encoder feed must reach YouTube and produce a preview, and you may still need to start the broadcast in YouTube. YouTube Help instructs: “In Live Control Room, wait for the stream preview to show up, and then click Go live.” Starting the encoder, or seeing Castr’s source as Connected, is not proof that this final step has been completed.
Open the correct scheduled event and watch for its preview. If YouTube says “connect your encoder to go live”, treat that wording as a YouTube-side prompt: check whether the correct destination is sending to that event and whether YouTube has received the feed. Do not read it as Castr’s Connecting status. If a preview appears, follow the controls shown for that event, including Go live when it is available and appropriate.
YouTube Help says that enabling live streaming for the first time may take up to 24 hours. If you have not enabled live streaming on the channel before, account for that official guidance rather than repeatedly changing Castr’s configuration. Check YouTube’s current help page and the account’s own notices; do not assume this is the explanation if the channel has streamed live previously or the screen gives a different error. The guide to prerecorded lectures on a 24/7 stream is useful background on the difference between a video source running continuously and a YouTube live event being active.
Run a private test to isolate the stage
A controlled test can show where the hand-off changes, but it will not prove that a public scheduled event is configured correctly. If your channel and YouTube’s current options allow it, create or select an appropriate private test event. Confirm the event’s visibility before sending anything, and use a short test rather than changing a live broadcast unexpectedly. Private testing is for checking the path, not a substitute for reviewing the event’s audience and settings before the real stream.
Run the test in order. Start the encoder, then wait for Castr to show Connected and for its preview or stats to appear. Check that the Castr YouTube destination is enabled and points to the test event. Finally, look for the preview in the test event’s Live Control Room and complete the on-screen go-live step if the test requires it. Write down the status at each point. If the Castr source is the first stage that fails, return to the encoder and ingest checks. If the source is present but the destination is not, revisit the connection method and event. If the preview appears but the event remains pending, the remaining action is in YouTube’s control room.
Keep the test narrow: use the same encoder, Castr source, protocol, and network you intend to use, changing only the destination event if needed. A test from a different computer or connection can verify that some configuration works, but it cannot rule out a problem on the original machine or network. When the test succeeds, confirm the real event is selected before broadcasting. The continuous Hindi video playlist guide may help if your content is a repeating programme, but playback continuity and the event’s go-live state are still separate checks.
Check service and network conditions, then escalate
If the source status or health charts point to instability, check Castr’s published status page at the time you are troubleshooting: status.castr.com. A previous all-services-online snapshot only records conditions at that earlier moment; it does not establish the current state. Likewise, an incident notice is useful context but does not by itself identify what happened to your particular stream. Castr says its ingests are redundant and can be rerouted automatically if an ingest fails, but that is not a promise that every source, destination, or YouTube issue will resolve automatically.
If the encoder reaches Castr, the destination appears correctly configured, and the problem persists, send Castr support a concise diagnostic record. Include the date and time with time zone, Castr source or region, protocol, encoder software and relevant output status, and the exact Castr source status. Add whether a preview and stats appeared, what the destination showed, the exact YouTube Live Control Room wording, and whether YouTube showed a preview. Include relevant Health Charts observations and the steps you have already tried. Avoid sending a stream key or other credentials in an ordinary support message; use a secure method if support specifically requests sensitive information.
This record is more useful than “it is stuck on starting” because it tells support which hand-off has been observed. If the encoder reports sending but Castr remains Connecting, say so. If Castr is Connected while YouTube shows no preview, report that different state. If the preview appears and YouTube awaits Go live, say that clearly. The VPS versus cloud streaming overview can help you think about the operating arrangement for a continuous channel, but it does not replace this stage-by-stage evidence when a current stream fails.
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
Does “starting” mean Castr is broken?
No. “Starting” alone does not tell you whether the encoder has reached Castr, whether Castr’s YouTube destination is active, or whether YouTube is waiting for a control-room action. Check and record the status at each stage before deciding where to troubleshoot.
Castr says Connected. Why is YouTube not live?
Connected indicates that Castr has locked onto a source feed; it does not establish that the intended YouTube destination is enabled or that a scheduled broadcast has been started. Check the destination’s connection method and event, then inspect the preview and any pending action in YouTube Live Control Room.
YouTube says “connect your encoder to go live”. Is that Castr’s status?
No. That wording is a YouTube Live Control Room prompt, not the name of Castr’s source status. Check whether Castr receives the encoder feed and whether its destination is sending to the specific YouTube event that is open.
What should I send Castr support?
Send the time and time zone, region or source, protocol, exact statuses and errors, whether Castr showed a preview or stats, whether YouTube showed a preview, and relevant health-chart observations. Include the checks already made, but do not put a stream key in an ordinary support message.