This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Problems with IPv6?


Recommended Posts

Hey today my internet went down which changed my IP. After that I've not been able to get my mumble server running.

My log says:


<W>2015-03-25 18:13:15.280 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2015-03-25 18:13:15.292 OpenSSL: OpenSSL 1.0.1e 11 Feb 2013
<C>2015-03-25 18:13:15.295 Successfully switched to uid 108
<W>2015-03-25 18:13:16.273 ServerDB: Opened SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2015-03-25 18:13:16.305 Resource limits were 95 95
<W>2015-03-25 18:13:16.306 Successfully dropped capabilities
<C>2015-03-25 18:13:16.616 MurmurIce: Initialization failed: Ice::SocketException
<W>2015-03-25 18:13:16.626 OSInfo: Failed to execute lsb_release
<W>2015-03-25 18:13:16.627 Murmur 1.2.4 (1.2.3-349-g315b5f5-2.2+deb7u2) running on X11: Linux 3.12.35+: Booting servers
<W>2015-03-25 18:13:16.730 1 => Server listening on
<W>2015-03-25 18:13:16.765 1 => Failed to set IPV6_RECVPKTINFO for
<W>2015-03-25 18:13:16.932 1 => Announcing server via bonjour
<W>2015-03-25 18:13:17.008 1 => Registration needs nonempty 'registername', 'registerpassword' and 'registerurl', must have an empty 'password' and allowed pings.
<W>2015-03-25 18:13:17.009 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)


I read somewhere that it is trying to force IPv6 or something but could not find a fix.

The server is running on a RaspberryPi with Raspbian

Any help is appreciated.

Link to comment
Share on other sites


  • Create New...