Tutorial
How To Install Webmin on an Ubuntu Cloud Server
About Webmin
Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing, and much more. Webmin removes the need to manually edit Unix configuration files, like /etc/passwd, and lets you manage a system from the console or remotely.
Step One—Root Login
Once you know your IP address and root password, login as the main user, root.
ssh root@123.45.67.890
Step Two—Add Webmin to APT repository
Edit the /etc/apt/sources.list file on your system and add the following lines.
Open the file with nano:
nano /etc/apt/sources.list
Press [Page Down] button on the keyboard to reach to the end of file. (or press Left ALt+/)
Then paste these two lines below:
deb http://download.webmin.com/download/repository sarge contrib deb http://webmin.mirror.somersettechsolutions.co.uk/repository sarge contrib
Save changes with CTRL+O and exit with CTRL+X.
Step Three—Install Webmin’s GPG key
You should also fetch and install Webmin’s GPG key in which the repository is signed and with the commands:
cd /root wget http://www.webmin.com/jcameron-key.asc apt-key add jcameron-key.asc
Step Four—Install Webmin
You will now be able to install with the commands:
apt-get update apt-get install webmin
Step Five—Login to Webmin
Open your browser and go to http://your_droplet_ip:10000/
You can now login as root with your root password, or as any user who can use sudo to run commands as root.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
author
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Might be worth mentioning that if you created a root user using a SSH key and thus don’t have a password then SSH ing and run the following command
sudo passwd root
Follow the prompts and then you should be able to login to webmin.
@Neil Sweeney: That is correct, thanks! :]
Hello,
I am really a newbie on linux so here is my question: I am using ubuntu 13.04 since I need php 5.4.x
And webadmin would make alot of things easier since im bad at linux.
So, do I need to install LAMP then install webadmin, or should I just install webadmin right away on my new vps?
also, does that tutorial work on ubuntu 13?
I believe webmin installs Apache for you. I don’t know if it can be installed on an Ubuntu 13.04, but you can try it and if it doesn’t work, you can rebuild your droplet from a 12.04 image.
Thank you.
It works on 13.04 tested yesterday :) But I have changed to 12.04 since its LTS, so just made a lamp install and upgraded to php 5.4 using ppa:ondrej/php5-oldstable.
Anyways do you think I should clear my install, and install webmin right away then try to upgrade the php version using ondrej? It worked fine yesterday on 13.04 when I first installed lamp then webmin, still maybe thats not the right way to do it.
Thanks
@kevin_thulin: If it’s working fine, I don’t think you need to redo it again from scratch. Keep it this way for a while and see how it goes.
If im using digitalocean’s lamp stack, what’s my default user/pass for sql?
@garnet: root:password, you should change it immediately once you log in (read the MOTD when you log in via SSH or run <code>cat /etc/motd.tail</code>
Small note: I had to login using https instead of http. Seems to be working fine, except for that little turnaround I had to do in the tutorial.