OpenSimulator · EN

WebRTC voice and conference troubleshooting

Specific symptoms and first checks without exposing credentials.

This documents one specific WebRTC stack. Respect compatible versions and consult linked sources before modifying a production deployment.

Official repositories and downloads

Three distinct components: voice server, simulator modules, and optional ad hoc conferences. Use versions compatible with your installation.

BloodMoon Voice — voice serverRelease v1.0.0 and installer
OpenSimulator WebRTC modulesRelease v0.9.3.1-webrtc.3, DLL/PDB ZIP
OpenSimulator AdHoc ConferencesPHP/MySQL source and installation guide

Nothing happens when enabling voice

First check estate and parcel voice permissions. This is a frequent cause: the viewer may never request provisioning when disabled.

Logs to examine : Region OpenSim.log and viewer diagnostic console if available.

Messages to search (clues, not guaranteed errors) : Search voice, WebRtc, parcel and provisioning; no request may indicate disabled parcel permissions.

Checks before changing anything : Check parcel and estate voice permissions before networking.

Possible fix after confirmation : Enable appropriate permissions and retest.

Server running but nobody connects

Check DNS, TLS certificate, TCP 9443, WebRtcVoiceServerURI and simulator authorization. Inspect region logs and wolfvoice.service. A running systemd service does not prove audio connectivity.

Example for your own installation: adapt all domains, paths and names.

sudo systemctl status wolfvoice.service --no-pager -l
sudo journalctl -u wolfvoice.service -n 60 --no-pager

Logs to examine : OpenSim.log and journalctl -u wolfvoice.service on the voice server.

Messages to search (clues, not guaranteed errors) : Search WebRtc, HTTPS, TLS, handshake, refused, unauthorized and timeout.

Checks before changing anything : Check DNS, certificate, TCP 9443, keys and allowlisted egress IPs.

Possible fix after confirmation : Fix networking or authentication without disabling certificate checks.

Session created but no audio

UDP 40000–40999 must be reachable by viewers. Check WOLFVOICE_PUBLIC_IP, NAT forwarding and ICE candidates in logs. A loopback test may succeed while external clients fail.

Logs to examine : wolfvoice.service and OpenSim.log; viewer ICE diagnostics if available.

Messages to search (clues, not guaranteed errors) : Search ICE, candidate, UDP, timeout, failed; wording depends on backend version.

Checks before changing anything : Check UDP 40000–40999, advertised public IP and NAT.

Possible fix after confirmation : Fix UDP reachability without exposing private management ports.

Connected but no spatial audio

Check that avatars have transmitted positions and joined the same voice room. Parcel isolation may be intentional. Also inspect viewer microphone, volume and audio devices.

Logs to examine : OpenSim.log, wolfvoice.service and viewer audio diagnostics.

Messages to search (clues, not guaranteed errors) : Search room, join, position, spatial, disconnect and related failures.

Checks before changing anything : Check voice room, distances, parcel settings, microphone and volume.

Possible fix after confirmation : Fix the identified room or device issue rather than restarting the grid.

Private call fails between simulators

Verify matching module versions and keys on both simulators. A server upgraded to two-key RPC authentication may reject an older region using only the legacy mode.

Logs to examine : OpenSim.log from both simulators and wolfvoice.service.

Messages to search (clues, not guaranteed errors) : Search call, credentials, RPC, forbidden, unauthorized, timeout.

Checks before changing anything : Compare module versions, authentication modes and key file access.

Possible fix after confirmation : Align modules and keys in a coordinated way without ad hoc rotation.

AdHoc conference HTTP 403

Check the PHP/MySQL registry, request signature, shared key and permitted simulator egress IP. Do not disable access control to hide the error.

Logs to examine : PHP/web and MySQL logs for the AdHoc API, plus OpenSim.log.

Messages to search (clues, not guaranteed errors) : Search HTTP 403, authentication, signature, allowlist and database errors.

Checks before changing anything : Compare simulator egress IP, key/signature and service rules.

Possible fix after confirmation : Correct the permitted IP or signature without disabling access control.

TLS or certificate error

The DNS hostname in WebRtcVoiceServerURI must match the HTTPS certificate. Modules verify the chain and hostname independently of some global OpenSimulator settings. Do not bypass invalid certificates.

Logs to examine : OpenSim.log and wolfvoice.service; reverse-proxy TLS logs if used.

Messages to search (clues, not guaranteed errors) : Search certificate, SSL, TLS, hostname mismatch, handshake.

Checks before changing anything : Check DNS name, certificate chain, renewal and system clock.

Possible fix after confirmation : Fix certificate or URI, not TLS verification.

Audio breaks up under load

Check voice server CPU, UDP network, packet loss, session count, VM limits and logs. Audio is sensitive to latency and jitter; resource contention can cause dropouts.

Logs to examine : wolfvoice.service, OpenSim.log and CPU/network metrics.

Messages to search (clues, not guaranteed errors) : Search disconnect, overload, timeout, ICE and repeated errors during dropouts.

Checks before changing anything : Correlate CPU usage, sessions, latency, UDP loss and system events.

Possible fix after confirmation : Address the measured bottleneck and compare before/after.

Firestorm occasionally shows a Vivox alert

The upstream troubleshooting guide describes a Vivox alert triggered by an audio settings panel even when WebRTC works. Distinguish it from a real WebRTC provisioning failure using logs.

Logs to examine : OpenSim.log and viewer diagnostics when available.

Messages to search (clues, not guaranteed errors) : Look for an actual WebRTC failure rather than assuming every Vivox alert is one.

Checks before changing anything : Check whether voice really fails when the alert appears.

Possible fix after confirmation : Do not reinstall the backend based solely on the alert.

Further reading and sources