![]() Save and exit once you have pasted the public key inside this new file. ssh/ folder and paste your public key inside. ![]() Now create a file called authorized_keys in that. On the server, let’s create the SSH folder and restrict it’s permissions. Ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXM圓MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf copy all of this to your clipboard so we can paste it to the server in a minute. On your own machine view your public key by using: $ cat ~/.ssh/id_rsa.pub Since we created a key pair earlier we will use the same one for the mumble user. We will then add this user to the sudo group with the following command: $ usermod -aG sudo mumbleĬhange to the user by running: $ su - mumble As such we will make a new user aptly called mumble. Generally it is not considered good security practice to run services as root when not required. $ apt list -upgradableįinally this will upgrade those packages. This will show which packages have updates available. This will update the package lists on the machine. On a Ubuntu machine updates can be achieved by carrying out the following commands: This would have been sent to you via email if no public SSH key was entered. If you did not setup SSH in the droplet creation stage you would be asked for a password when attempting to connect. $ ssh we pasted in our public key, we were able to SSH into the droplet easily. Now that you have created the droplet, let’s attempt to connect using SSH. Copy and paste SSH public key you created/already had(alternatively you can add one later, it’s covered in step 6).Choose datacenter region closest to you.Choose droplet specs - the first basic option will do for a Mumble server (1GB mem/1vCPU).Choose operating system - here we have chosen Ubuntu 16.04.The following is what will need to be changed/selected. ![]() You will then be taken to a basic configuration page for a new droplet. To create the droplet, simply go to the Create dropdown menu on the top right of your Digital Ocean account and select droplet. Next you will be asked for a passphrase, whether you choose to use this is up to you, however I would suggest doing so. Hit enter to use the standard name and location for your keys. NOTE: If you already have SSH keys setup you can skip this step. You will also need to use the following software: a browser, a terminal, SSH, a text editor, Mumble-Server and the Mumble client. In order to follow this, you will need a Digital Ocean account and a domain you have purchased from your registrar of choice. Usually I run a Mumble server on a Raspberry Pi 2 in my homelab, however I recently set it up on Digital Ocean and thought I would document the process as I did not find any posts detailing the entire procedure. Although the majority of people have moved to proprietary options such as Discord, I prefer to use Mumble as it is the better option for privacy and freedom. The following was created on a Ubuntu 16.04 droplet but should be very similar if not the same on other distributions. So, logged out of the old laptop and tried logging in on the new one with the same password, same error message.This post will cover the complete process of setting up a Mumble server utilising Digital Ocean as a VPS provider and using a custom domain bought through a domain registrar. i checked the password on the old laptop and it matched what i thought it should have been. Viola! the old laptop logged in as SuperUser the first time with the saved password it had hidden somewhere. after resetting the password a couple times to the same thing i thought it was i played a hunch and reinstalled mumble on the old laptop hoping it might be hiding a certificate somewhere i couldn't find it. now from what i have read the certificate part of that is superfluous, but i didn't see that until after wasting an hour or two trying to find the certificate on the old laptop where i had uninstalled mumble already. but, when i went to login to SuperUser the first time i went and looked up the password, put it in, and got the wrong password or certificate error message. i installed mumble 1.3.3 on a new laptop, copied the certificate over for my personal account which worked fine. until i replaced the laptop i was using to administer the server with. Can i confuse this topic even more? i have had murmur running on my win 2012r2 server for a while and had set the superuser password and it was working fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |