Only one room available at a time

[reichert]

Hello guys.

I just installed MiroTalk P2P in version 1.4.99 (the latest available in cloudron) and for the first room everything works fine.
When openning a second concurrent room - the browser just does not create the room and reload the initial page. We have nothing in the console and could not found any error message.
When leaving the first room it is possible again to enter/create in any other room.
The test was done in two different computers using each one his own room to avoid session issues.

How to proceed?

[MiroTalk]

@reichert said in Only one room available at a time:

How to proceed?

https://github.com/miroslavpejic85/mirotalk/blob/ed5c1e96217f9ff8c4d1fda43122b63bbf03a0e2/.env.template#L43

[robi]

This should probably be the default behavior and needs a package adjustment @girish @nebulon

[girish]

Generally, we prefer to not change the upstream defaults at the package level. @mirotalk-57bab571 do you think the default can be changed upstream ? Why is this false by default? Thanks!

[MiroTalk]

@girish said in Only one room available at a time:

@mirotalk-57bab571 do you think the default can be changed upstream ?

Hi, I just pushed the changes.
I might be a bit slow to reply as I'm currently on holiday.

All the best,
Miroslav

[alpro]

@reichert, I experience exactly the same behaviour. With only difference that I experience it with MiroTalk SFU 1.8.60. Creating multiple rooms for my family used to work in the past. But after the update some time ago it stopped to work. With symptoms exactly as you have described. This is a bit annoying as only one person from my family can use MiroTalk SFP at the time. Any ideas how to resolve it for the time bing before any changes propagate to Cloudron?

[MiroTalk]

@alpro said in Only one room available at a time:

With only difference that I experience it with MiroTalk SFU 1.8.60.

Not sure how is handled there, but by default, OIDC_ENABLED is set to false in all MiroTalk projects.

When OIDC_ENABLED is set to true, any user authenticated via OIDC can create and share rooms. Previously, only one user had this ability, but now this behavior is enabled by default (when OIDC is active) and can be configured through the .env file.

OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true  // true or false (default true)

So when you visit your MiroTalk SFU instance outside the cloudron panel, (e.g., https://cloudron.your-domain-name.com), the Cloudron OIDC authentication popup will appear. Simply enter the username and password you use for Cloudron login. Once authenticated, you—or your family members—will be able to access the instance, create rooms, and share them with guests.

---

Additionally, you can try another approach by updating your env file (via the Cloudron file manager) in MiroTalk SFU to enable HOST_PROTECTED mode and define a list of authorized users as follows:

OIDC_ENABLED=false
HOST_PROTECTED=true
HOST_USER_AUTH=false
HOST_USERS="username:password:User:*|admin:admin:Admin:room1,room2|guest:guest:Guest:room1,room1"

When HOST_PROTECTED or HOST_USER_AUTH enabled:

HOST_USERS – Define Authorized Host Users

The HOST_USERS environment variable is used to predefine a list of users who are allowed to log in as hosts in your application. Each user entry follows this format:

username:password:displayName:allowedRooms

Multiple users are separated by the pipe symbol |.

Format Breakdown:

• username: The login name of the user.
• password: The password used for authentication.
• displayName: The name that will be shown in the UI (e.g., in meetings).
• allowedRooms: A comma-separated list of room names this user is allowed to create or join as host. Use * to allow all rooms.

🧪 Example:

HOST_USERS="username:password:user:*|admin:admin:Admin:room1,room2|guest:guest:Guest:room1"

This defines 3 host users:

1. username with password password, display name user, can access any room (*).
2. admin with password admin, display name Admin, can access only room1 and room2.
3. guest with password guest, display name Guest, can access only room1.

---

For reference here.

[alpro]

@mirotalk-57bab571 , thx a lot for the support! Adding the line below in the .env file resolved the issue.

OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true // true or false (default true)

[MiroTalk]

@alpro said in Only one room available at a time:

thx a lot for the support! Adding the line below in the .env file resolved the issue.

OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true // true or false (default true)

You're welcome.

---

For MiroTalk P2P to handle users without OIDC, use the following environment configuration:

OIDC_ENABLED=false
HOST_PROTECTED=true
HOST_USER_AUTH=false
HOST_USERS='[{"username": "admin", "password": "admin"}, {"username": "guest", "password": "guest"}]'

HOST_USERS

This environment variable differs in format from the one used in MiroTalk SFU. It defines a list of allowed users when OIDC (OpenID Connect) is disabled (OIDC_ENABLED=false) and static user authentication is needed.

It must be a JSON-formatted array of user objects, where each object contains a username and a password.

Example:

HOST_USERS='[{"username": "admin", "password": "admin"}, {"username": "guest", "password": "guest"}]'

Purpose:

The application will authenticate users using the credentials provided in this list. This enables a simple, built-in username/password authentication mechanism without requiring an external identity provider.

[reichert]

Thanks for the fix. It worked!