sv3nx Posted August 10, 2010 Share Posted August 10, 2010 How do I get the server to Public Internet list? Do I only need to fill the servername filed in ini file? Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 10, 2010 Administrators Share Posted August 10, 2010 See ini file# To enable public server registration, the serverpassword must be blank, and# this must all be filled out.# The password here is used to create a registry for the server name; subsequent# updates will need the same password. Don't lose your password.# The URL is your own website, and only set the registerHostname for static IP# addresses.##registerName=Mumble Server#registerPassword=secret#registerUrl=http://mumble.sourceforge.net/#registerHostname= Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 11, 2010 Author Share Posted August 11, 2010 See ini fileSO I need it like this? # To enable public server registration, the serverpassword must be blank, and# this must all be filled out.# The password here is used to create a registry for the server name; subsequent# updates will need the same password. Don't lose your password.# The URL is your own website, and only set the registerHostname for static IP# addresses.#registerName=MyHostNameregisterPassword=registerUrl=http://homepage.com/registerHostname=MyHostName Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 11, 2010 Administrators Share Posted August 11, 2010 Yes (those values are placeholders, right? :P) Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 12, 2010 Author Share Posted August 12, 2010 Yes (those values are placeholders, right? :P)I've set it up exactly as it is in my previous post, but server doesn't show up in public list. Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 12, 2010 Administrators Share Posted August 12, 2010 Well, you’ll have to enter YOUR servers details.registerName=example.comregisterPassword=registerUrl=http://example.com/registerHostname=example.comIf your domain for that server is example.com. Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 12, 2010 Author Share Posted August 12, 2010 Well, you’ll have to enter YOUR servers details.registerName=example.comregisterPassword=registerUrl=http://example.com/registerHostname=example.comIf your domain for that server is example.com. So I did, above was just an a example. Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 12, 2010 Administrators Share Posted August 12, 2010 Does your server log state anything?On successful registration it should log it, and probably on failure as well. Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 13, 2010 Author Share Posted August 13, 2010 Does your server log state anything?On successful registration it should log it, and probably on failure as well. 2010-08-12 11:18:44.223 1 => Server listening on [::]:647382010-08-12 11:18:44.271 1 => Announcing server via bonjour2010-08-12 11:18:44.279 1 => Registration needs nonempty 'registername', 'registerpassword' and 'registerurl', must have an empty 'password' and allowed pings. Here's how it is configured: registerName=jope.eeregisterPassword=registerUrl=http://jope.ee/registerHostname=jope.ee Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 13, 2010 Administrators Share Posted August 13, 2010 As stated in the log, you have to specify a secret registerpassword for registration as well. Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 13, 2010 Author Share Posted August 13, 2010 As stated in the log, you have to specify a secret registerpassword for registration as well.dough Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 15, 2010 Author Share Posted August 15, 2010 As stated in the log, you have to specify a secret registerpassword for registration as well.Sooh addedd the required password, but still not in pub list. Log shows: 2010-08-15 19:42:12.804 Initializing settings from /home/kasutaja/murmur/murmur.ini (basepath /home/kasutaja/murmur)2010-08-15 19:42:12.875 Binding to address 195.250.189.1112010-08-15 19:42:12.917 SSL: Added CA certificates from '/etc/ssl/certs/ca-certificates.crt'2010-08-15 19:42:12.939 ServerDB: Openend SQLite database /home/kasutaja/murmur/murmur.sqlite2010-08-15 19:42:12.966 Failed to connect to D-Bus session2010-08-15 19:42:14.226 Murmur 1.2.2 (Compiled Feb 9 2010 17:44:13) running on X11: Debian GNU/Linux 5.0.5 (lenny): Booting servers2010-08-15 19:42:14.250 1 => Server listening on 195.250.189.111:647382010-08-15 19:42:14.302 1 => Announcing server via bonjourWhat else am I missing here?Edit: Nevermind it is working now! Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted August 15, 2010 Administrators Share Posted August 15, 2010 Yeah, public registration may take some several minutes before the server shows up in the public server list. Quote Link to comment Share on other sites More sharing options...
sv3nx Posted August 16, 2010 Author Share Posted August 16, 2010 Yeah, public registration may take some several minutes before the server shows up in the public server list.Thank you for helping out! Quote Link to comment Share on other sites More sharing options...
viktor9 Posted September 8, 2011 Share Posted September 8, 2011 HelpI like problemma# Path to database. If blank, will search for # murmur.sqlite in default locations or create it if not found. #database=/var/lib/mumble-server/mumble-server.sqlite database=mumble # If you wish to use something other than SQLite, you'll need to set the name # of the database above, and also uncomment the below. # Sticking with SQLite is strongly recommended, as it's the most well tested # and by far the fastest solution. # dbDriver=QMYSQL dbUsername=mumble dbPassword=123456 dbHost=localhost #dbPort= dbPrefix=murmur_ #dbOpts= # Murmur defaults to not using D-Bus. If you wish to use dbus, which is one of the # RPC methods available in murmur, please specify so here. # dbus=system # Alternate service name. Only use if you are running distinct # murmurd processes connected to the same D-Bus daemon. dbusservice=net.sourceforge.mumble.murmur emailfrom = bot@ukr.net # If you want to use ZeroC Ice to communicate with Murmur, you need # to specify the endpoint to use. Since there is no authentication # with ICE, you should only use it if you trust all the users who have # shell access to your machine. # Please see the ICE documentation on how to specify endpoints. ice="tcp -h 127.0.0.1 -p 6502" # Ice primarily uses local sockets. This means anyone who has a # user account on your machine can connect to the Ice services. # You can set a plaintext "secret" on the Ice conntection, and # any script attempting to access must then have this secret. #icesecret= # How many login attempts do we tolerate from one IP # inside a given timeframe before we ban the connection? # Note that this is global (shared between all virtual servers), and that # it counts both successfull and unsuccessfull connection attempts. # Set either Attempts or Timeframe to 0 to disable. #autobanAttempts = 10 #autobanTimeframe = 120 #autobanTime = 300 # Murmur default to logging to murmur.log. If you leave this blank, # murmur will log to the console (linux) or through message boxes (win32). logfile=/var/log/mumble-server/mumble-server.log # If set, murmur will write its process ID to this file. pidfile=/var/run/mumble-server/mumble-server.pid # The below will be used as defaults for new configured servers. # If you're just running one server (the default), it's easier to # configure it here than through D-Bus or Ice. # # Welcome message sent to clients when they connect welcometext="<br />Welcome to this server running <b>Murmur</b>.<br />Enjoy your stay!<br />" # Port to bind TCP and UDP sockets to port=64738 # Specific IP or hostname to bind to. # If this is left blank (default), murmur will bind to all available addresses. host=77.121.4.50 # Password to join server serverpassword= # Maximum bandwidth (in bits per second) clients are allowed # to send speech at. bandwidth=72000 # Maximum number of concurrent clients allowed. users=100 # Regular expression used to validate channel names # (note that you have to escape backslashes with \ ) #channelname=[ \\-=\\w\\#\\[\\]\\{\\}\\(\\)\\@\\|]+ # Regular expression used to validate user names # (note that you have to escape backslashes with \ ) #username=[-=\\w\\[\\]\\{\\}\\(\\)\\@\\|\\.]+ # Maximum length of text messages in characters. 0 for no limit. #textmessagelength=5000 # Maximum length of text messages in characters, with image data. 0 for no limit. #imagemessagelength=131072 # Allow clients to use HTML in messages, user comments and channel descriptions? #allowhtml=true # Murmur retains the per-server log entries in an internal database which # allows it to be accessed over D-Bus/ICE. # How many days should such entries be kept? #logdays=31 # To enable public server registration, the serverpassword must be blank, and # this must all be filled out. # The password here is used to create a registry for the server name; subsequent # updates will need the same password. Don't lose your password. # The URL is your own website, and only set the registerHostname for static IP # addresses. # registerName=plusnet.ks.ua registerPassword=plus registerUrl=http://plusnet.ks.ua/ registerHostname=77.121.4.50 # To enable bonjour service discovery uncomment the following line. # To change the name announced by bonjour adjust the registerName variable. # See http://developer.apple.com/networking/bonjour/index.html for more information # about bonjour. #bonjour=True # If you have a proper SSL certificate, you can provide the filenames here. #sslCert= #sslKey= # If murmur is started as root, which user should it switch to? # This option is ignored if murmur isn't started with root privileges. uname=mumble-server # If this options is enabled, only clients which have a certificate are allowed # to connect. #certrequired=False # You can configure any of the configuration options for Ice here. We recommend # leave the defaults as they are. # Please note that this section has to be last in the configuration file. # defaultchannel=3 [ice] Ice.Warn.UnknownProperties=1 Ice.MessageSizeMax=65536 log<W>2011-09-08 15:58:33.821 Murmur 1.2.2 (1.2.2-6) running on X11: Debian GNU/Linux 6.0.2 (squeeze): Booting servers <W>2011-09-08 15:58:33.897 1 => Server listening on 77.121.4.50:64738 <W>2011-09-08 15:58:34.088 1 => Announcing server via bonjour <W>2011-09-08 16:00:07.812 1 => Registration: SSL Handshake error: The certificate is self-signed, and untrusted <W>2011-09-08 16:00:07.854 1 => Registration failed: SSL handshake failed <W>2011-09-08 17:00:14.652 1 => Registration: SSL Handshake error: The certificate is self-signed, and untrusted <W>2011-09-08 17:00:14.694 1 => Registration failed: SSL handshake failed Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.