This is where Flussonic differentiates itself. The login you use for the web UI is completely separate from the credentials required to publish a stream (RTMP push) or view a protected stream.
Stream authentication is handled by the auth section within a stream definition:
stream camera_01
input fake://;
auth
user publisher
password = "pub123";
perm = publish;
user viewer
password = "view456";
perm = play;
This separation means an operator can log into the web UI to monitor servers, but cannot accidentally disrupt a live stream without separate publish credentials. flussonic login
Because Flussonic uses local storage, if you lose the root password and are locked out of the UI, there is no "email reset" feature. Recovery requires:
| Field | Default Value |
|------------|----------------------------|
| Username | admin |
| Password | admin (or none – depends on version) | This is where Flussonic differentiates itself
⚠️ Note:
Never send your password over plain HTTP. In the Flussonic settings, configure an SSL certificate. Once HTTPS is active, you can disable HTTP access entirely by setting port 8080 to 0 in the configuration file. This separation means an operator can log into
Flussonic is famous for its powerful REST API. After logging in, you can access /api on your server (e.g., http://server-ip:8080/api) to see a live documentation of all API calls. The API uses the same credentials as the web login.
For video engineers and system administrators managing large-scale streaming infrastructures, Flussonic Media Server is a powerful yet complex tool. While much of the conversation around Flussonic focuses on its low-latency streaming, CDN origins, or DVR capabilities, the first line of defense—and often the first point of configuration friction—is its login and authentication system.
This article dissects the Flussonic login process, exploring how it balances out-of-the-box simplicity with enterprise-grade security.