A Cesbo Astra stream can be restarted with its Streams API, but the command only restarts an enabled Astra stream from its stored configuration. It does not enable a disabled stream or prove that YouTube has resumed receiving a healthy feed.
First confirm that you are using Cesbo Astra and identify the correct stream ID. After sending the restart request, check Astra’s runtime status and then check the separate YouTube event in Live Control Room; those are different parts of the recovery.
Confirm that this is Cesbo Astra
“Astra” can refer to different products and deployments. The procedure here is specifically for Cesbo Astra, whose official Streams API documentation describes a restart-stream command. Do not try it against another application just because its name includes Astra, or assume that commands documented for one Astra version or installation match yours.
You also need access to the relevant Astra control interface and permission to issue control requests. The API describes restart as a control operation. If you did not configure the installation, ask its administrator to confirm the product, API access details, and stream ID rather than guessing at an endpoint or making changes to a production service.
Identify the particular stream that sends the feed to YouTube. Astra’s stream methods use a stream id; installations can contain multiple streams, outputs, or channels. Use the configured stream information to establish which ID belongs to the affected YouTube output. A name such as “Bhajan Live” may help you locate the entry, but the request needs the ID, not a guessed name.
Keep the scope of the operation in mind. The restart command acts on Astra’s stream and its stored configuration. It does not edit the YouTube event, replace a stream key, change an output URL, or tell you whether viewers can see the result. A familiar feed-management workflow is not the same as a single end-to-end restart; for broader context, see how cloud YouTube loop services handle reconnection.
Check the stream’s enabled state
Before issuing a restart, inspect Astra’s stored configuration and confirm that the stream is enabled. The documented behaviour is narrow: an enabled stream is stopped and started again using its stored configuration; a disabled stream is left disabled. The command is not an enable operation, even if the API replies ok.
This distinction matters when a channel has been intentionally paused, when a previous operator disabled an output during maintenance, or when a configuration change left the stream off. Restarting a disabled entry will not restore transmission. Find out why it is disabled, and use the appropriate authorised control or configuration process if you intend to enable it. Do not treat repeated restart requests as a substitute for checking state.
Also verify that the chosen ID is the stream you mean to affect. A stream ID pointing to a different output can restart the wrong service without fixing the YouTube destination you are troubleshooting. If several streams have similar names, compare their configured output destinations or ask the administrator who maintains them.
It can help to note the current state before acting: stream enabled or disabled, whether it appears to be running, and which output it is configured to use. That gives you a simple before-and-after record. It is especially useful if you need to ask someone else to investigate, because “YouTube is offline” alone does not show whether the issue lies in Astra, the encoder connection settings, or the YouTube event.
Send the restart-stream API request
For an enabled Cesbo Astra stream, send a POST request to the Astra control endpoint /control/ with the restart-stream command and the stream ID. The request body is JSON. Replace the example ID below with the confirmed ID for the output you intend to restart:
POST /control/
Content-Type: application/json
{"cmd":"restart-stream","id":"a001"}
The a001 value is only an example, not a recommended or universal stream ID. Use the ID from your own Astra configuration. Send the request through the control access method set up for your installation; the path shown is not a public YouTube endpoint. Do not paste credentials or a real stream key into a shared chat, support post, or screenshot.
The command requests a restart from the stream’s stored configuration. It does not revise that configuration, so a wrong YouTube ingest address or obsolete stream key remains wrong after the restart. It also does not notify clients that anything has changed. If an operator has recently updated settings, check that the intended settings were saved before restarting.
Treat this as a deliberate recovery action, not a harmless status query. A stop-and-start cycle can briefly interrupt the stream and can affect anyone watching the output. If the channel is carrying a local news loop, a scheduled devotional programme, or another time-sensitive feed, consider whether another operator is already handling the incident before issuing the command. Coordination avoids multiple people making changes at once.
Interpret the response carefully
A successful response is {"restart-stream":"ok"}. That tells you Astra accepted the restart request; it is not proof that YouTube is receiving video and audio, that an event is live, or that viewers can watch. A request using an unknown ID returns an error. If you receive an error, verify the ID and the request format, and check that you are using the correct Astra control endpoint and permissions.
Cesbo’s documentation says, “An enabled stream is stopped and started again from its stored configuration.” Read that as a statement about Astra’s stream, not YouTube’s event. The same documentation says a disabled stream is left alone. Therefore, ok by itself does not establish that a disabled stream became active, and the response does not report whether YouTube has resumed its ingest.
Use the separate runtime check for a running stream to inspect its status. Astra documents a check-stream operation; the returned runtime information can include whether the stream is onair, the active input, and the latest analyser sample for each input, including bitrate and error counters. These are clues about Astra’s path and inputs. They do not replace checking the YouTube destination.
A “stream not found” result from the runtime check needs careful reading. The documented check can return that result when a stream is disabled or not running, so it is not simply a verdict that the stream ID does not exist in stored configuration. Revisit the enabled state and whether the stream actually started, then use the stored stream information to confirm the ID.
If a request times out or your client does not display a clear response, avoid firing off repeated restarts without checking state. First determine whether Astra received the request and whether the stream is already running. When you cannot see the control result, ask the installation administrator to inspect it rather than risking additional interruptions.
Verify the feed in YouTube
Astra and YouTube expose different parts of the broadcast path. Once Astra’s runtime check indicates that the stream is carrying an active input, open the correct event in YouTube Live Control Room and check its current state and incoming preview or health indicators. YouTube’s encoder setup guidance explains that an encoder uses the YouTube stream URL and stream key to connect. Use the current values associated with the event you intend to run.
If the stream key was reset or replaced, update the encoder’s configured key with the current one. The key is a secret connection credential: do not include it in screenshots, notes shared publicly, or a troubleshooting article. Check the destination URL as well as the key; restarting a stream cannot correct an incorrect endpoint or credentials that have not been updated.
Check the event itself, not just the encoder. YouTube’s guidance on setting up a live stream covers stream setup and the event controls. Auto-start and auto-stop settings affect whether encoder actions can start or stop an event. Confirm those settings and whether the event is still active or has ended. The Astra restart documentation describes restarting Astra, not reopening an ended YouTube broadcast, so do not assume the event will resume automatically.
A useful comparison is to record what each side says before changing anything else:
| Check | What it can tell you | What it cannot establish on its own |
|---|---|---|
| Astra enabled state | Whether the configured stream is enabled | Whether it is reaching YouTube |
| Astra runtime check | Whether Astra reports an active stream or input, with analyser details | Whether the YouTube event is still open to the feed |
| YouTube Live Control Room | Whether the event is live, ended, or showing an incoming feed | Whether the issue is within Astra’s input path |
| Encoder URL and key | Whether the configured ingest destination and credential match the event | Whether the whole broadcast is healthy for viewers |
This separation is useful for both a one-person channel and a small team. For example, if Astra reports an active input but YouTube shows no incoming feed, focus on the output connection details and YouTube event state. If YouTube indicates an incoming feed but viewers report a problem, investigate the event and the content being sent rather than assuming that another Astra restart is the answer.
Investigate a continuing disconnect
When Astra reports a restart but YouTube remains offline, work through the path in order and make one change at a time. Confirm that the correct Astra stream is enabled and running, then inspect its input status and analyser fields. If the input is absent or unhealthy, the issue may be upstream of the YouTube output. If the input appears healthy, check the configured YouTube URL and stream key, then confirm that the destination event is the intended one and has not ended.
Check whether the disconnect followed a configuration change, a key reset, a network interruption, or an event transition. These are possibilities to investigate, not diagnoses that can be inferred from a successful API response. Compare the current setup with the values the channel administrator expects, but do not expose secrets while doing so. If the setting is managed by another person, ask them to verify it rather than replacing it speculatively.
If the event has ended, consult YouTube’s current event controls and decide whether you need to create or schedule a new event. The sources cited here do not say that restarting Astra reopens a finished event. Likewise, if the broadcast is still not reaching YouTube after confirming the event and encoder settings, gather the time of the incident, Astra’s stream ID, the response, and non-secret status details for the administrator or relevant support team.
For channels that depend on a PC-based player or encoder, separate playback failure from destination failure. The source file might have stopped, an input might have gone quiet, or the encoder might have disconnected even though the stream entry remains enabled. The checklist in why OBS can stop playing videos during a 24/7 YouTube stream is relevant when OBS supplies the material to the broadcast. If your setup uses a playlist, also check the file and output preparation; downscaling videos for a YouTube playlist stream covers a separate preparation issue, not a fix for a disconnected YouTube event.
For a channel whose main operational problem is keeping a file-based broadcast going while a local computer is off, a managed file-to-live workflow such as StreamNeo removes the need to keep that computer running for the broadcast. That is a different operating choice, not a repair for a Cesbo Astra installation or a guarantee about YouTube event recovery; decide whether the workflow fits before changing how the channel is run.
Make the recovery repeatable
Write down a short incident procedure for the people who may be on duty overnight. It should identify the Cesbo Astra installation, the stream ID associated with each YouTube destination, who can issue control requests, and where to check the event in Live Control Room. Include the distinction between an enabled stream and a disabled one, and state plainly that ok confirms a command response rather than an end-to-end broadcast.
Keep a private record of the expected output URL and the process for obtaining or resetting the stream key, but do not put the key itself in a general operating document. Note who is authorised to change those settings. If you rotate a key, make sure the configured sender is updated through the approved process, then verify both Astra and the YouTube event.
After an incident, record what was observed on each side: the Astra response, runtime status, relevant input health, and YouTube event state. Avoid recording a stream key or other secret. This record helps distinguish a repeatable input issue from an event that had already ended, and it prevents the next operator from treating every “offline” report as the same failure.
A practical handover can be concise: “Astra stream enabled; restart accepted; runtime input onair; YouTube event still ended” is more informative than “restart worked”. The first description makes clear which part recovered and which part still needs action. It also helps a technical contact investigate without making them infer what the API response meant.
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
How do I restart an Astra Streaming broadcast after a YouTube disconnect?
If you are using Cesbo Astra and the relevant stream is enabled, send POST /control/ with {"cmd":"restart-stream","id":"YOUR_STREAM_ID"}. Confirm the ID first, then check Astra’s runtime status and the YouTube event separately. The command does not enable a disabled stream.
Does restarting Astra bring my YouTube live stream back?
It restarts an enabled Astra stream from its stored configuration, but that alone does not show that YouTube resumed receiving a healthy feed. Check the encoder’s YouTube URL and stream key, and confirm the event is still active in Live Control Room. Astra’s restart documentation does not say that an ended event will reopen.
What should I check if Astra says the stream restarted but YouTube is still offline?
Check whether the Astra stream is enabled and whether its runtime status shows an active input, then verify the YouTube destination URL, current key, and event state. A successful API response is not an end-to-end health check. If the event has ended, use YouTube’s current controls to decide how to proceed rather than repeatedly restarting Astra.