SSL and domain names

[crombiecrunch]

Hello all

Is there a guide on how to setup a domain name for the server?

Right now I can only access it buy going to IP:port. I have tried adding just a A record on the domain name but that just takes me direct to the server IP.

Is there a guide on how to setup a SSL cert for the server?

Also can you use a sub/domain name instead of the IP address? So I want to offer somename.myhostname.com:randomport and they can use that address to connect to the server. If that can be done will I need a wildcard SSL cert?

[kissaki]

A domain is a 1:1 mapping to an IP. So an A record is sufficient to redirect you to an IP, as you said it works as well.

And if it already directs you to the IP, you should be able to connect to domain:port

yes, subdomains as well. They're just the same.

About the cert, I think the murmur.ini tells you a bit, probably as well what kind of cert you need.

So you'll just need one of those and set them for the server.

If setting in ini is not sufficient set them through Ice for the virtual server.

[crombiecrunch]

Ok, so I have installed my SSL cert and have uploaded the files to the server. In the .ini file I have added

[*]sslCert=/etc/apache2/ssl/guildmumble.com.crt

sslKey=/etc/apache2/ssl/guildmumble.com.key[*]

I restarted the server, but when connecting to a new server I still get a verification warning. Pressing view certificate, it still shows Murmur Autogenerated certificate v2.

Any ideas what I did wrong?

[kissaki]

I'm not quite sure if you have to set them via Ice for a specific virtual server.

Did you create an entirely new server? virtual server or process?

[crombiecrunch]

I had the guys over at [*]http://mumb1e.de/[*]set everything up for my server. They installed everything from murmur to their control panel. I am still learning mumble. Ive created a few v servers that I was testing. I didnt see any .ini files for each server though, only the main mumble.ini.

[crombiecrunch]

Ok, so I figured out the SSL issue. My host name was set to something different, setting it to the same as what I setup the SSL cert for has fixed the issues.

[kissaki]

Your murmur.ini is used as a default for your virtual servers.

The virtual servers themselves don't have an ini file, so you'll have to change settings for specific virtual servers via Ice.

[crombiecrunch]

ok so here is a interesting one. So I did a update on the server today and it upgraded a few things like apache2 and openssl.

Now when I connect to the mumble servers it gives me the SSL warning the host name did not match any of the valid hosts for this cert, blah blah blah

I checked the cert file and its using the default murmur autogenerated file EVEN though in the murmur.ini file its being told to use my SSL file.

I have restarted the server several times even reissued the stupid SSL files and I can not get it to go back to my SSL file. I cant even find the murmur autogenerated one to delete them

Any help on this

[kissaki]

So you only set it via ini?

Try setting it via Ice.

I think the cert will stay after vserver creation no matter what you do with the ini.

[crombiecrunch]

How do I do that? I am just using the installed control panel.

[kissaki]

Which control panel.

There's none natively with Murmur.

[crombiecrunch]

The only one Ive tried so far, the one from mumb1e.de

[kissaki]

Well, there's probably a setting for that, configuring virtual servers.

I can't guide you through that though, I never used that control panel.

[crombiecrunch]

actually i just loaded up your control panel, now I see I can change each servers SSL with yours correct?

[kissaki]

Yes.

In each vservers details there's a config section where you can change it.