Vultr Broadcaster is a cutting-edge application that brings the power of OBS Studio to your browser. It is designed to provide a seamless and efficient live streaming experience by offering a headless OBS Studio solution with a convenient web interface. Whether you are a professional streamer, content creator, or an organization looking to broadcast events, Vultr Broadcaster empowers you to take your live streaming to new heights.
Vultr Broadcaster leverages the capabilities of OBS Studio, a renowned open-source software for video recording and live streaming. With Vultr Broadcaster, you can harness the full potential of OBS Studio without the need for a local installation. It operates as a headless application, meaning that you can access and control OBS Studio functionalities remotely through your web browser.
The intuitive web interface of Vultr Broadcaster simplifies the streaming setup and management process. Instead of relying on a desktop application, you can now leverage the power of OBS Studio directly in your browser. The web interface offers a user-friendly environment that allows you to configure scenes, add sources, adjust audio settings, and fine-tune your stream without the need for complex software installations.
Vultr Broadcaster goes beyond traditional browser-based streaming solutions by seamlessly integrating Virtual Network Computing (VNC) technology. This integration enables you to have remote access and control of the streaming machine, providing you with a comprehensive broadcasting experience. With VNC, you can monitor your stream, make real-time adjustments, and ensure your content is delivered flawlessly.
Join the next generation of live streaming by harnessing the power of Vultr Broadcaster. Experience the convenience of a headless OBS Studio application with a feature-rich web interface. Elevate your live streaming capabilities and engage your audience like never before.
Vultr Broadcaster has been setup for you to access in a variety of ways
User: OBS User
Password: OBS Password
Password: OBS Password
Cockpit control panel is accessible via https://use.your.ip:9080/:
* Credentials are the same as provided on the Server Information page
If you use the Vultr Firewall, make sure to allow access to port 9080.
Cockpit can be disabled by connecting as the root user and running:
# systemctl disable --now cockpit.socket
To access the service with a domain name, instead of use.your.ip, it is possible to register a domain name from a domain registrar, and either follow the registrar's documentation on updating DNS records, or utilize Vultr's DNS.
Once DNS has finished propagating, and the registered domain name resolves to use.your.ip, connect to the server via console or SSH as the
Certbot is installed by default on this app. If you need to update or reinstall, please see the recommended installation steps at eff.org.
The below example shows installing multi-domain certificate for the bare or root domain of
example.com as well as the fully-qualified domain name (FQDN) of
www.example.com. The email provided is used for registering an account with Let's Encrypt and is not sent to Vultr:
# certbot --nginx --redirect -d www.example.com -d example.com -m email@example.com --agree-tos --no-eff-email
Upon successfully requesting certificates, a message should be shown that includes text similar to the following:
Successfully deployed certificate for www.example.com to /etc/nginx/sites-enabled/XXX_https.conf
Congratulations! You have successfully enabled HTTPS on https://www.example.com
(Optional) To update the Cockpit Control Panel to use the same certificate, a script is available to be invoked via:
In case a certificate issued by Let's Encrypt via
certbot is to be revoked, or otherwise needs to be uninstalled, these steps should be followed:
1. Back up current web server configuration files:
# cp -r /etc/nginx /root/nginx
2. Revoke the certificate:
# certbot delete
3. Restore default web server configuration:
If a commercial certificate is desired instead of the free Let's Encrypt certificate, install the public certificate as
/etc/nginx/ssl/server.crt and the private key as
/etc/nginx/ssl/server.key. Refer to the certificate vendor's documentation for any further details. Once these files are in place, reboot the server to ensure all services are using the correct certificate:
While strongly discouraged, it is possible to disable HTTPS access by running the following:
# rm /etc/nginx/sites-enabled/obs_https.conf /root/; reboot
Report an application with malicious intent or harmful content.