Agora Setup Guide

Applies to: Current VideoHub360 theme package

What Agora Powers

Agora provides the real-time connection used by VideoHub360 Studio, Mobile Live, compatible Live Rooms, and interactive viewer participation. Agora credentials belong to VideoHub360 Core; Studio uses those credentials through the platform integration.

Add Agora Credentials

1. Create or open an Agora project in your Agora account.
2. Copy the project App ID.
3. Obtain the App Certificate when token security is enabled.
4. In WordPress, go to VideoHub360 → Settings → Agora.io Settings.
5. Save the App ID and App Certificate in the matching fields.

Use HTTPS. Camera and microphone access can fail on an insecure site even when the credentials are correct.

Use Agora with Studio

The normal production workflow is:

1. Open the frontend Dashboard.
2. Open Studio.
3. Choose Production Studio or Mobile Live through the Studio entry screen.
4. Complete the livestream setup.
5. Test the camera and microphone.
6. Start the broadcast.

Studio creates and uses the required live session data. Do not create a normal VOD through Add Video merely to obtain a Studio channel.

Studio uses a dedicated saved host UID for the Program output. A host who opens the public viewer page joins with a different signed audience UID, preventing a duplicate copy of the host video. Public participant names and avatars are resolved by the server-side participant identity registry.

Broadcast and Interactive Behavior

Broadcast mode is intended for a produced host-to-audience stream. Interactive mode can allow approved viewer participation according to the video’s join rules. Participant publishing permissions, passcode requirements, and “allow everyone to be host” behavior should be tested with a separate viewer account.

Do not enable conflicting open-host and passcode workflows on the same session.

Live Rooms

Live Rooms use their own frontend room-management workflow. They can use Agora, but they are not the Production Studio and do not automatically provide the same Program composition, recording, overlays, or replay-publishing workflow.

Manual or Legacy Livestream Metadata

Administrators may still encounter Core livestream fields on a VideoHub360 post. Treat those fields as advanced or compatibility controls. Standard creators should use Studio for new platform livestreams.

Test the Connection

Test with two devices or separate browser profiles:

• host in Studio
• viewer on the public video page
• camera and microphone permissions granted
• host visible once, not duplicated
• participant names correct
• viewer join behavior matches the configured mode
• ended state appears after the host ends the stream

Troubleshooting

Agora App ID is not configured

Save the App ID under VideoHub360 → Settings → Agora.io Settings and confirm VideoHub360 Core is active.

Token or authorization errors occur

Verify the App Certificate, server time, channel data, and HTTPS. Do not send browser-provided participant identities as authoritative user data.

The host appears twice on the viewer page

Confirm the current Core and Studio versions are installed together. The public page must use a separate audience UID and must not publish another host feed.

Signed-in participants appear as guests

Confirm token authorization is reaching the server-side participant identity registry and that the current user is authenticated on the public site.