coop-cloud/mumble
1
0
Fork 0
Code Issues 2 Pull Requests 1 Projects Releases Wiki Activity

ALLOW_PING not respected #7

New Issue
Open
opened 2026-04-29 09:19:12 +00:00 by amras · 1 comment
amras commented 2026-04-29 09:19:12 +00:00
Owner
Copy Link
Copy Source

In the mumble-server.ini docs, the allowPing option is described as follows:

Respond to UDP ping packets.
Setting to true exposes the current user count, the maximum user count, and the server's maximum bandwidth per client to unauthenticated users. In the Mumble client, this information is shown in the Connect dialog.

Reproduction

  1. abra app config <DOMAIN>
ALLOW_PING=true
USERS=100
  1. abra app deploy <DOMAIN> --force
  2. Connect to DOMAIN using a mumble client
  3. (Re)open the Mumble Server Connect window (Server -> Connect)

Expected Behavior

DOMAIN should have some value in the Ping column, and "1/100" in the Users column.

Actual Behavior

DOMAIN shows no values for Ping or Users, regardless of whether ALLOW_PING is true or false.

In the [mumble-server.ini](https://github.com/mumble-voip/mumble/blob/master/auxiliary_files/mumble-server.ini) docs, the allowPing option is described as follows: >Respond to UDP ping packets. >Setting to true exposes the current user count, the maximum user count, and the server's maximum bandwidth per client to unauthenticated users. In the Mumble client, this information is shown in the Connect dialog. ## Reproduction 1. `abra app config <DOMAIN>` ``` ALLOW_PING=true USERS=100 ``` 2. `abra app deploy <DOMAIN> --force` 3. Connect to DOMAIN using a mumble client 4. (Re)open the `Mumble Server Connect` window (Server -> Connect) ## Expected Behavior DOMAIN should have some value in the Ping column, and "1/100" in the Users column. ## Actual Behavior DOMAIN shows no values for Ping or Users, regardless of whether ALLOW_PING is true or false.
amras commented 2026-05-01 11:29:59 +00:00
Author
Owner
Copy Link
Copy Source

The reproduction seems inconsistent.
It's possible it might've been a symptom of a persistent traefik or docker-network issue, which resolved after restarting docker.

In any case, unless I can get another reproduction I'll have to close this issue.

The reproduction seems inconsistent. It's possible it might've been a symptom of a persistent traefik or docker-network issue, which resolved after restarting docker. In any case, unless I can get another reproduction I'll have to close this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke cas (Cassowary) coopcloud decentral1se (decentral1se) fauno (fauno) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) stevensting trav yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/mumble#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?