Having an odd ssl issue, maybe someone can shed some light on a possible cause.
I'm getting a few issues in the logs.
<W>2014-05-16 12:28:36.735 Initializing settings from /home/mumble/murmur.ini (basepath /home/mumble)
<W>2014-05-16 12:28:38.233 Binding to address 103.###.###.###
<W>2014-05-16 12:28:38.234 OpenSSL: OpenSSL 1.0.0k 5 Feb 2013
<C>2014-05-16 12:28:38.234 Successfully switched to uid 1000
<W>2014-05-16 12:28:38.241 ServerDB: Opened SQLite database /home/mumble/######.sqlite
<W>2014-05-16 12:28:38.245 Resource limits were 0 0
<W>2014-05-16 12:28:38.245 Successfully dropped capabilities
<W>2014-05-16 12:28:38.248 OSInfo: Failed to execute lsb_release
<W>2014-05-16 12:28:38.248 Murmur 1.2.4 (1.2.4) running on X11: Linux 3.2.0-4-amd64: Booting servers
<W>2014-05-16 12:28:38.264 1 => Server listening on 103.###.###.###:64738
<W>2014-05-16 12:28:38.266 1 => Failed to set IPV6_RECVPKTINFO for 103.###.###.###:64738
<W>2014-05-16 12:28:38.271 1 => Announcing server via bonjour
<W>2014-05-16 12:28:38.273 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)
<W>2014-05-16 12:31:28.828 1 => Registration failed: SSL handshake failed
Murmur is saying my openssl version is "openSSL 1.0.0k", but i check which version the system is running and the system says "openssl 1.0.1e-2+deb7u7". Which i believe may be causing the "SSL handshake failed" message, cause i can think of any other reason its failing.
Hopefully someone has encountered this before and its a quick and easy fix, thanks in advance. :)
Have you tried Mumble-Server 1.2.6 version?
Don't know if the problem might be on IPV6, have you tried to disable it and use IPV4 instead?
yeah i tried 1.2.6 first and it failed with the same error.
Just installed a fresh copy of a different version of Debian (6.0.6 instead of 7.0.0) and it fails also
Here You go,
Disabled IPv6 and still the same result
Note my actual installed version of openssl is "0.9.8o-4squeeze14" , but murmur now sees it as "OpenSSL 1.0.0l"
<W>2014-05-16 15:36:14.923 Initializing settings from /home/mumble/murmur.ini (basepath /home/mumble)
<W>2014-05-16 15:36:14.923 Binding to address 103.###.###.###
<W>2014-05-16 15:36:14.924 OpenSSL: OpenSSL 1.0.0l 6 Jan 2014
<C>2014-05-16 15:36:14.924 Successfully switched to uid 1000
<W>2014-05-16 15:36:14.926 ServerDB: Opened SQLite database /home/mumble/######.sqlite
<W>2014-05-16 15:36:14.928 Resource limits were 0 0
<W>2014-05-16 15:36:14.928 Successfully dropped capabilities
<W>2014-05-16 15:36:14.928 Failed to connect to D-Bus session
<W>2014-05-16 15:36:14.930 OSInfo: Failed to execute lsb_release
<W>2014-05-16 15:36:14.930 Murmur 1.2.6 (1.2.6) running on X11: Linux 2.6.32-5-amd64: Booting servers
<W>2014-05-16 15:36:14.937 1 => Server listening on 103.###.###.###:64738
<W>2014-05-16 15:36:14.940 1 => Failed to set IPV6_RECVPKTINFO for 103.###.###.###:64738
<W>2014-05-16 15:36:14.944 1 => Announcing server via bonjour
<W>2014-05-16 15:36:14.945 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)
<W>2014-05-16 15:38:53.484 1 => Registration failed: SSL handshake failed
Do you use basic config settings or have you edited it?
I had no problems after clean system install to get server running,
started it with root privilege and basic settings
using ice password for web based configure with phpMumbleAdmin
Here is my log from Linux Mint 16 64bit
2014-05-15 23:23:26.476 Initializing settings from /etc/mumble-server.ini (basepath /etc)
2014-05-15 23:23:26.476 OpenSSL: OpenSSL 1.0.1e 11 Feb 2013
2014-05-15 23:23:26.514 ServerDB: Opened SQLite database /var/lib/mumble-server/mumble-server.sqlite
2014-05-15 23:23:26.520 DBus registration succeeded
2014-05-15 23:23:26.523 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
2014-05-15 23:23:26.575 Murmur 1.2.6 (1.2.6-1~ppa1~saucy1) running on X11: Linux Mint 16 Petra: Booting servers
2014-05-15 23:23:26.865 1 => Server listening on [::]:64738
2014-05-15 23:23:26.910 1 => Announcing server via bonjour
2014-05-15 23:23:27.185 1 => Registration needs nonempty 'registername', 'registerpassword' and 'registerurl', must have an em$
2014-05-15 23:23:27.185 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)
Found something what might be worth to check
@ Lari , I have set up many servers myself & never had an issue. I tried changing just the registration settings and left everything else as it was and still failed. I even copied my live working server across to it and it failed too. So it wasn't a settings issue.
It think it may be the VPS host's iso's are bad. I tried 4 different versions of Debian & 2 different murmur versions (a total of 8 different environments) and all failed with the same error. Yet all my other mumble servers run on Debian no worries. Anyway, i tried Ubuntu 14.04 & it work out of the box, exactly like it always has for me.
Hi, Odd that different Debians fails, Im stuck on Mint flavour, it just seems to work best for me, had once problems with ICE after upgrade to 13 or 14 long time ago. But good if Ubuntu 14.04 works, but not good if not used to use it. Where did you get those isos? i could try out them in WM myself and see does it the same bugs.
They are the stock iso's that come with the vps, i cant download them unfortunately, or upload my own to replace them. It just fails on every version of Debian they have. Ubuntu and Debian aren't that different so shouldn't be much of an adjustment.
That's too bad, don't know if the iso's have been changed somehow in the VPS, might be differences compared to iso's in known Debian sites.
I don't have experience on VPS hosts my self, just use regular PC on my living-room.
yeah, i have run mumble on vps's for years, all over the place and never had an issue until now. I would love to run it from home but our bandwidth is quite rubbish where i live. So i am kinda forced to host in a datacentre, also the 1.5TB per month is mostly free with the datacentre i'm with. I just decided to set one up in a different country and ran into that little ssl issue that i sank about 10 hours into trying to fix, grrrrr. oh well, its running now :), Thanks for your suggestions :)
Im tempted to email the vps host and see if the can send me their Debian isos, i would love to know why its failing.
If they give you the isos, or a link where to get them, i can try out, just curious about them. Glad i could help in someway=)