A Dacast stream that is not showing on YouTube can disappear at more than one point in the delivery path. Check Dacast Preview first, then the saved YouTube destination in Dacast, and finally YouTube’s incoming preview and Go live state.
Do not start by replacing equipment or changing random URLs. The useful question is where the feed stops: before Dacast receives it, between Dacast and YouTube, or inside YouTube’s live event controls.
Locate the break in the stream path
For a Dacast Simulcast setup, the expected path is:
encoder → Dacast channel → Dacast Simulcast destination → YouTube event → public YouTube live page
The encoder is the software or device sending your video. It uses the server or publishing URL and stream key shown for the Dacast channel. Dacast then forwards the received feed to the YouTube destination that you have configured in its Simulcast settings. YouTube receives that forwarded feed in the live event associated with its own stream key.
That means the same symptom can have different causes. A blank Dacast Preview points towards the encoder-to-Dacast part of the path. A working Dacast Preview with no YouTube incoming preview points towards the saved destination, the YouTube key, or the hand-off between the two services. An incoming YouTube preview that is not public may simply need the event owner to select Go live.
Use this order rather than checking every setting at once:
| What you can see | What it confirms | Where to investigate next |
|---|---|---|
| Dacast Preview is blank | Dacast is not displaying the expected incoming feed | Encoder URL, encoder key and the current Dacast channel configuration |
| Dacast Preview is playing | Dacast is receiving a feed | Saved YouTube Simulcast destination and its stream key |
| YouTube shows an incoming preview | YouTube is receiving the forwarded feed | Event status, scheduled time and the Go live action |
| YouTube is live but viewers see a different state | The event may be configured differently from the feed you tested | Correct YouTube event, visibility and public watch page |
These are diagnostic inferences from the documented workflow, not guarantees. Dashboard labels can vary by account or product version, so use the values currently displayed in your channel and event.
If you are actually sending your encoder directly to YouTube, this path is different. In that case, Dacast Preview is not the relevant first test because the encoder is not using Dacast as its ingest destination. Confirm the workflow before changing a server URL or key.
Check Dacast Preview first
Open the Dacast channel and use its Preview or share playback option while the encoder is running. Dacast’s live streaming walkthrough describes previewing the feed as part of testing the live setup.
Give the preview enough time to establish playback, then check whether it shows the current programme rather than an old still image or an empty player. If you are running a devotional loop, for example, look for the current bhajan or visual scene. If you are sending a local news loop, confirm that the current graphic or clip is visible. This simple check tells you more than the public YouTube page at this stage.
A blank or stalled Dacast Preview means YouTube is not yet the first place to troubleshoot. Dacast has not demonstrated that it is receiving the intended encoder feed, so changing the YouTube stream key will not repair this particular break. Move to the encoder configuration and the channel’s current ingest details.
A playing Dacast Preview narrows the next check. It shows that the encoder is reaching Dacast and that Dacast can play the received feed. It does not, by itself, prove that the YouTube destination was saved correctly or that the intended YouTube event is receiving the feed.
Record what you see before making changes. Note whether the preview is blank, delayed, frozen, showing the wrong content or playing normally. If you need support later, this observation is more useful than saying only that YouTube is missing the stream.
If Dacast Preview is empty, check the encoder URL and key
First open the Dacast channel’s current encoder configuration. Compare its displayed publishing or server URL and stream key with the values entered in your encoder. Do not rely on a URL copied from an older tutorial, another channel or a search result.
The stream key must belong to the Dacast channel you are testing. Check for missing characters, accidental spaces and a key copied for a different event. If your encoder has separate fields for the server URL and key, make sure the URL has not been pasted into the key field or vice versa.
There is an important detail when Simulcast or a multi-destination arrangement has been enabled. Dacast says that creating a multi-destination setup changes the ingest URL used by the encoder. Its guide states, “When setting a Multistream destination, the ingest destination URL CHANGES.” The example address in that guide is not a universal value for every channel. Use the current URL shown in your own Dacast configuration.
After enabling or changing Simulcast, reopen the encoder settings rather than assuming the previous Dacast address remains valid. Update only the Dacast ingest details that the current channel displays, then start the encoder again. Watch Dacast Preview after the change.
Also check the encoder’s actual output state. A scene may be visible inside the encoder while the encoder is not sending, is paused, or is sending to a different profile. Confirm that the profile is live, the intended input is selected and the connection is not reporting a key or connection error. If you use OBS for a loop, the guide on looping multiple videos on YouTube Live with OBS may help with the content side, but it does not replace checking the Dacast destination configured in OBS.
If Dacast Preview remains empty after matching the current URL and key, avoid changing several fields at once. Capture the exact encoder message, the time of the test and the Dacast preview state. Then check whether the encoder can maintain its connection and whether the channel selected in Dacast is the one you opened for preview.
If preview is live, verify the YouTube Simulcast destination
When Dacast Preview is playing, open the channel’s Engagement or Simulcast settings and inspect the YouTube destination. The destination should be present, associated with the intended YouTube account or event workflow, and saved after the stream key was entered.
Do not assume that opening a YouTube live event automatically adds it to Dacast. Dacast’s multi-destination setup guide describes adding YouTube as an external destination and entering the YouTube stream key. Follow the current labels in your Dacast account, then save the destination before retesting.
Check these points in order:
- The YouTube destination exists in the Dacast channel’s Simulcast settings.
- It is saved, rather than only entered in an unsaved form.
- The stream key belongs to the YouTube event you are currently viewing.
- The destination is not pointing to an old event or an unrelated channel.
- The Dacast encoder is still using the current Dacast ingest URL after the Simulcast configuration was created.
Dacast’s Simulcast workflow forwards the feed that Dacast is receiving to the configured destination. It does not remove the need to configure the YouTube event correctly. YouTube still controls the receiving event, its preview and the action that makes the broadcast public.
If you have more than one YouTube event, use an identifying note while testing. For example, create or select the event for “Tuesday evening bhajan loop” and compare that event’s key with the key saved in Dacast. This avoids testing Dacast against one event while watching another in YouTube Studio.
Do not edit the Dacast encoder URL to a direct YouTube URL merely because YouTube is not showing a preview. In a Dacast-forwarded setup, the encoder should first reach Dacast. Direct YouTube streaming is a different workflow and should be treated as such, not mixed into the same test.
Confirm the YouTube stream key
Open YouTube Live Control Room for the intended event and display the current stream settings. YouTube’s guide to creating a live stream with an encoder explains the role of the stream key and server details in an encoder workflow.
For Dacast Simulcast, the YouTube key is used as the external destination key in Dacast. It is not normally the key that you paste into the encoder when the encoder is sending to Dacast. The encoder keeps the Dacast URL and Dacast key; Dacast’s YouTube destination holds the YouTube key.
Compare the key saved in Dacast with the current key for the YouTube event. If the key has been regenerated, revoked or replaced, the old value in Dacast will no longer identify the intended receiving event. YouTube’s troubleshooting guidance recommends obtaining a new key and updating the relevant configuration when a stream-key error is reported.
Take care with reusable keys and event-specific keys. The correct choice depends on how you created the YouTube live event and what YouTube currently displays. The key must match the event you are monitoring, not simply a key that worked for a previous broadcast.
If you generate a new key, update the saved YouTube destination in Dacast, save it, and then retest while Dacast Preview remains live. Avoid changing the Dacast encoder’s key at the same time unless Dacast’s own current configuration shows that it has changed. Otherwise you may create two separate changes and lose track of which link was repaired.
Keep keys private. Do not paste them into a public support post or include them in a screenshot. When escalating, redact the value and provide the key’s label, the event name and the exact error instead.
Check Live Control Room preview and the Go live action
With Dacast Preview playing and the YouTube destination saved, return to YouTube Live Control Room. Look for an incoming preview on the specific event associated with the key in Dacast. YouTube may take a short period to display the incoming feed, so distinguish an initial wait from a persistent absence.
If the preview appears, inspect the picture and audio before publishing. A preview confirms that YouTube is receiving a feed, but it does not necessarily mean viewers can already watch the event. For a scheduled stream, YouTube’s encoder workflow can require the owner to select Go live after the incoming preview is available.
This is a common point of confusion for an always-on channel. The encoder can be running, Dacast Preview can be playing and YouTube can show an incoming image while the public watch page is not yet live. Check the event state and the available action in Live Control Room rather than restarting the encoder repeatedly.
If YouTube shows a stream-key error, follow that message’s key checks. If it shows a connection, timeout or RTMPS-related error, consult YouTube’s RTMPS connection guidance and identify which service is making the connection. In a Dacast-forwarded setup, YouTube is receiving the connection from the Dacast destination, not directly from the computer running your encoder. Do not apply direct-encoder URL changes blindly to Dacast’s Simulcast path.
YouTube’s live stream troubleshooting page is useful for matching the displayed message to the next check. Follow the wording shown in your Live Control Room instead of treating every missing stream as a stream-key problem.
If the event is live in Control Room but absent from the expected public page, check that you are viewing the same event, channel and visibility setting. A live control room can be healthy while a bookmarked page points to an older broadcast. For a channel that runs continuously, keep a record of the current event link so that operators do not test an outdated watch page.
Retest after correcting the failing link
Once you identify the failing link, change the smallest number of settings needed. A useful retest has three observations:
- The encoder reports that it is sending to the current Dacast configuration.
- Dacast Preview displays the expected current content.
- YouTube Live Control Room receives the feed on the intended event and shows the correct event state.
Start with the first observation and wait for Dacast Preview. If Preview is still empty, stay with the encoder-to-Dacast investigation. If Preview is healthy, move to the saved YouTube destination and key. If YouTube receives the preview, complete the Go live step when the event requires it.
Do not judge the result only from the public watch page. It is the last part of the path and can conceal whether the problem is an ingest failure, an unsaved destination, the wrong event or an unpublished preview. Testing each checkpoint gives you a clear stopping point.
For a 24/7 channel, keep a short handover note containing the Dacast channel name, the YouTube event name, the date of the last successful test and the location of the current preview. Do not record the actual stream keys. This makes the next overnight check quicker without exposing credentials.
If the same failure returns after the configuration matches the current dashboard values, contact the relevant support team with facts rather than guesses. Include the Dacast Preview state, the YouTube event state, the exact error text, whether the event is scheduled or already live, and the time of the test. State whether the encoder connects to Dacast or directly to YouTube.
That distinction matters because Dacast and YouTube are responsible for different links in the chain. It also prevents a support response about direct encoder settings being applied to a Dacast-forwarded workflow. The continuous YouTube livestream with FFmpeg on Windows in India guide is relevant if you later decide to examine a direct encoder setup, but that is a different delivery path from the Simulcast flow described here.
If the content itself is a prerecorded loop, keep the playback test separate from the delivery test. A working source file does not prove that the destination is receiving it. Likewise, a healthy destination does not confirm that the file has the rights or settings you need for your particular channel. For a channel built around worship or devotional programming, you may also want the practical scheduling notes in how to schedule a continuous worship stream on YouTube, while keeping this diagnostic sequence for delivery failures.
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 should I check Dacast Preview before YouTube?
Dacast Preview tests whether the encoder has reached Dacast at all. If it is empty, the first checks are the Dacast URL, key and current channel configuration, rather than the YouTube event.
Dacast Preview works, but YouTube shows nothing. What should I check?
Inspect the saved YouTube destination in Dacast and compare its key with the intended YouTube event. Then open that event in Live Control Room and check for an incoming preview, rather than relying only on the public watch page.
Does an incoming YouTube preview mean the stream is public?
Not always. A scheduled event may show an incoming preview while still requiring the owner to select Go live. Check the event state and the action shown in Live Control Room.
Should I put the YouTube URL into my encoder?
Only if you have confirmed that you are using a direct YouTube encoder workflow. With Dacast Simulcast, the encoder sends to Dacast, while the YouTube stream key is configured as the saved external destination in Dacast.