Bambuser RTMP Ingest: Finding the Streaming Endpoint

Where to find the Bambuser RTMP ingest endpoint

There is no single public ingest address you can safely copy from a forum post. Bambuser gives you the RTMP server address and the stream key or stream name through your own account or broadcast setup. In older desktop workflows this came as a profile file for Flash Media Encoder (FME), which already contained the server and stream values. Get the endpoint from your account, not from a third-party list, because hosts and keys can differ by account, by broadcast and over time.

• Sign in to the Bambuser account that owns the broadcast.
• Open the broadcast or channel setup and look for the option for external encoders, RTMP or encoder settings. The exact wording depends on your product version and plan.
• Copy the server URL and the stream key, or download the encoder profile if one is offered.
• Paste both values into your encoder exactly as given, then run a short test broadcast before going live.
• If you cannot find any RTMP or encoder option, ask your account administrator or Bambuser support whether RTMP ingest is enabled for your account.

How RTMP ingest and FME profiles work

With RTMP ingest, your encoder pushes a live audio and video stream to a server. The encoder needs two values: the server URL, which says where to connect, and the stream key or stream name, which tells the platform which account or broadcast the stream belongs to. A correct server with a wrong key will usually connect and then be rejected, or fail to appear in the right broadcast.

FME refers to Adobe Flash Media Live Encoder, a legacy desktop encoder. Its profiles are XML files that store encoding settings plus output details such as the server URL and stream name. Importing a platform-supplied profile fills these fields automatically, which is why services used to offer an FME download instead of asking users to type the values.

Check these details in Bambuser's current documentation or dashboard, since they can change: whether your plan includes RTMP ingest, the exact ingest host, whether keys are permanent or created per broadcast, and whether an FME profile is still offered.

Using the endpoint in a modern encoder

If you have an FME profile but use a different encoder, open the XML file in a plain text editor and look for the entries holding the output URL and the stream name. Copy the URL into the encoder's server field and the stream name into its stream key field. Some encoders want one combined address instead of two fields. In that case follow that encoder's own instructions for joining them, rather than guessing the format.

• Remove spaces and line breaks that sometimes get copied along with the key.
• Check that the address scheme matches what the platform provided, for example rtmp or rtmps.
• Do not reuse a key from an earlier broadcast if your setup issues a new key for each event.
• Use a private test broadcast to confirm that video and audio arrive before you announce the stream.

Treat the stream key as a password. Anyone who has it may be able to broadcast to your channel, and a downloaded profile file contains it in readable text. Store the file securely, keep it out of shared folders and screenshots, and reset the key if it has been exposed and your account allows that.

Limits and related questions

Plain RTMP commonly uses port 1935, and some office or school networks block it. If the encoder cannot connect even with correct values, try another network or ask your network administrator. If the platform supplies an rtmps address, the connection is encrypted and normally uses a different port. Use the address exactly as provided.

RTMP workflows typically use H.264 video and AAC audio, but resolution, bitrate, keyframe interval and codec limits are set by the receiving platform. Check Bambuser's current requirements for your account and do not rely on values from old FME profiles or unofficial guides.

Common causes of a failed or missing stream are a mistyped or truncated key, an expired or ended broadcast, a server address copied from an outdated source, or encoder settings the platform does not accept. If the dashboard does not offer an ingest endpoint at all, the feature may be unavailable on your plan. Only Bambuser or your account administrator can confirm that.