![]() Ssl_certificate_key /etc/letsencrypt/live//privkey.pem Ssl_certificate /etc/letsencrypt/live//fullchain.pem Generate a random password for the admin:Īnd copy/paste this password to the umurmur config file.Ĭreate the systemd service unit (just copy/paste this block):Ĭat > /etc/systemd/system/rvice /etc/systemd/system/rvice /etc/nginx/sites-available/nf << EOF We will define the certificates later on. You can now edit the configuration file at /usr/local/etc/nf. Install the umurmur binary on the system: However, we switched to the official murmur server, as the latest umurmur release is becoming old and outdated.Īpt install git build-essential cmake libconfig-dev libprotobuf-c-dev libmbedtls-dev ssl-certĬreate the directory for the server sources:Ĭheckout to the latest version (see the releases list): Note This install procedure is for the umurmur server, which is a lightweight Mumble server. You can see how we configured our instance here: Server ![]() ![]() Since December 2020, we are using our Ansible role to install both the web client and the Mumble server: Therefore, the below install procedure won't be updated anymore. Indeed, the Mumble server listens on port 64738, while the client listens on ports 80 and 443, so they won't conflict ) Just reuse the same certificate for both applications and you should be fine. However, you can as well use a single domain name for both applications, or a domain name for the web client and another for the Mumble server. No password is needed, although we could decide to setup a password if we see that there are too much spam. To connect you can give the username you wish. It is also possible to connect through another Mumble client either at or with port 64738. Since March 2020, the PPBe is hosting a Mumble server together with a web client on or Mumble is a server for holding audio conferences.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |