Skip to content

Ubuntu

How to Install OnlyOffice Document Server For Nextcloud, Fast & Easy

I’ve wasted a ridiculous amount of time trying to get the Collabora / LibreOffice / CODE platform integrated with my Nextcloud 11 server.  I wanted to have Google Docs-style editing, but it was turning out to be a massive headache.  One day, on accident, I stumbled on an OnlyOffice plugin for OwnCloud.  After a little digging, I found out it worked with NextCloud as well.  Less than 15 minutes later, I had the OnlyOffice Document Server packages installed on a second Ubuntu 16.04 server and it was fully integrated with my NextCloud server.

 

What You Need

 

For this guide, you will ultimately need the following:

  • A 2nd Ubuntu 16.04 or 16.10 Server
  • A Valid SSL Certificate (A FREE LetsEncrypt Certificate Will Do)
  • A Valid DNS Entry for Both Servers (for this guide, you are required to use onlyoffice.yourdomain.tld, custom OnlyOffice domains are out of the scope of this guide)

 

Installing Dependencies

 

OnlyOffice requires a few dependencies.  Mainly, nodejs, postgresql, and nginx.  In addition, we’ll need to enable a repo for up-to-date ttf-mscorefonts-installer packages.

 

First, let’s go ahead and add the needed repo’s.

 

echo "deb http://archive.ubuntu.com/ubuntu precise main universe multiverse" | sudo tee -a /etc/apt/sources.list
curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -

 

Next, install postgresql.

Click Here to Keep Reading!

How to Install Openstack Ocata on a Single Server, Using Devstack

Deploying an Openstack test or development platform can be a very daunting task.  A traditional installation of an Openstack infrastructure requires many servers and is quite complex.  However, there are a few methods that can make this task much easier, and possible with access to a single physical server or virtual machine that has enough resources.  Today, we’ll deploy an Openstack Ocata infrastructure using a single virtual machine (in my case, a VMware ESXi based virtual machine) using Devstack.  I’ve found this to be the most stable, repeatable, and reliable method to get an Openstack infrastructure up as quickly as possible.  Keep in mind, this same guide can be used to install almost any release of Openstack, simply by adjusting one word.  More on that later.

Requirements

 

For this guide, you will need a server at least as good as these specs.

  • Virtual Machine on a real hypervisor (ESXi, KVM, Xen, etc) or a bare metal server with virtualization support.
  • 14GB of RAM is the recommended minimum.  18GB or more will provide the best results.
  • 100GB of hard disk space, at least.
  • Ubuntu 16.04 LTS server, having already ran sudo apt update && sudo apt upgrade
  • About an hour and a cup of coffee.

 

Installing OpenStack

Click Here To Keep Reading!

How to Fix ‘setkeycodes 00’ and ‘Unknown key pressed’ Console Errors on OpenStack!

Earlier today, I wrote an updated tutorial on using devstack to install OpenStack on a single Ubuntu 16.04 server.  That deployment went so smooth it was no surprise when I ran into a roadblock when trying to console into my first instance.

 

The Problem

 

When accessing the console through the web browser, I wasn’t able to use the keyboard.  Every time I hit any key, these two lines would display in the console:

 

[ 74.003678] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.

[ 74.004462] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).

 

use_setkeycodes_unknown_key_pressed_error_VNC_console_openstack

Click Here To Keep Reading!

Install OpenStack on One Virtual Machine, the Easy Way, On Ubuntu 16.04 LTS!

Many of you have emailed me or posted to voice your gripes about the painful process of installing an OpenStack environment to play around with. I feel your pain! My recent article on deploying OpenStack using conjure-up worked great until a developer committed some defective code.  Some of you even reverted to my old guide on deploying OpenStack on Ubuntu 14.04 from last year.  So, I set out to give you a fool proof, 100% guaranteed deployment method that’s EASY, STABLE, and works on Ubuntu 16.04 Xenial.  Here you go!

Requirements

 

For this guide, you will need a server at least as good as these specs.

  • Virtual Machine on a real hypervisor (ESXi, KVM, Xen, etc) or a bare metal server with virtualization support.
  • 14GB of RAM is the recommended minimum.
  • 100GB of hard disk space, at least.
  • Ubuntu 16.04 LTS server, having already ran sudo apt update && sudo apt upgrade
  • About an hour and a cup of coffee.

 

Installing OpenStack

Click Here To Keep Reading!

Install OpenStack on a Single Ubuntu 16.04.1 Xenial Xerus Server Using Conjure-up

Introduction

 

It’s been some time since I wrote Installing Ubuntu OpenStack on a Single Machine, Instead of 7.  Since then, there have been many updates to both OpenStack, and Ubuntu.

This tutorial will guide you through installing OpenStack on a single Ubuntu 16.04 Server.  I will be installing Ubuntu and OpenStack within a virtual machine hosted on a VMware ESXi Hypervisor, but any fresh installation of Ubuntu 16.04 should work fine, as long as it meets the minimum requirements below.  I will be using conjure-up to install the environment due to the fact that Ubuntu’s Openstack-install package doesn’t working on Ubuntu 16.04.1 at this time.

 

Note:  I have written an updated guide on Installing OpenStack on Ubuntu 16.04 LTS using devstack.  I suggest following that guide unless you have a specific reason for using the conjure-up method.  From my experience, the devstack method requires less resources, runs faster, and performs much better once deployed.

 

Minimum Requirements

 

To install the entire environment on a single physical server or virtual machine, you will need at least:

 

  • 8 CPU’s (vCPUs will work just fine)
  • 12GB of RAM (minimum needed to successfully start everything, more is better)
  • 100GB Disk Space (SSD Prefered, but rotating disk will work)
  • Ubuntu 16.04.1 Xenial Xerus x64 Server(only OpenSSH Server installed)

Click Here To Continue Reading!

Secure Apache In No Time, For Free, With an SSL Certificate From Let’s Encrypt!

Recently, I found out about a non-profit organization called Let’s Encrypt, which came into existence earlier this year.  Let’s Encrypt is a publicly trusted certificate authority that issues FREE SSL certificates.  The SSL Certificates are fully functional and extremely easy to request and install.  In fact, using Let’s Encrypt, it only takes about a minute to request and install an SSL certificate on Apache via the Linux command line, using a few simple commands.  If you have a Linux server(s) running any sort of public facing web server, there is no reason not to do this right now.  Here’s how to do it on Ubuntu 16.04 (although it should be the same process on any version of Ubuntu)!

 

Prerequisites

To install an SSL certificate from Let’s encrypt using this guide, you will need a couple things.

  • A server running Ubuntu 16.04 (although this should work on any version of Ubuntu)
  • Apache installed with a domain name(s) that is resolvable to the IP of the server.
    • If you are hosting multiple domains, you will need to be sure you have Virtual Hosts configured that properly specify the ServerName variable.

 

Install the Let’s Encrypt Client

 

To make things easy, there is a client available, based on python, that will do all of the hard work for you.  The package is called python-letsencrypt-apache.  Let’s use Aptitude to install it.

 

#  sudo apt-get update

# sudo apt-get install python-letsencrypt-apache

 

The client is now installed and we can move on to setting up the SSL certificate.

Click Here to Keep Reading!!

Configuring ownCloud 9 & Active Directory / LDAP Plugin Successfully

With this step-by-step guide, you will have your ownCloud 9 (and earlier) cloud server authenticating against Active Directory or LDAP correctly in no time!

Introduction

 

Recently, I went through the process of setting up a brand new ownCloud 9.1 server, after my previous ownCloud server had seen upgrades from 6.x all the way up to 8x.  If you’ve used ownCloud that long, you know the abundant changes and improvements that have been made along the way did not come without their growth pains; especially if you delved into encryption.  So, I decided to start fresh.  I use Active Directory to provide a centralized authentication source for everything in my personal “cloud,” so after setting up my new Dropbox clone, the first thing I needed to do was configure the LDAP user and group backend plugin.  I had a lot of problems getting the Active Directory usernames to match the ownCloud usernames, instead of showing a long string off numbers.  It was a lot of confusing UID, UUID, SAMAccountName and DN related confusion.  There aren’t any great guides to keep you from getting a headache, so I decided to make one.

 

Problems with the LDAP user and group backend plugin

 

It’s pretty straight forward to get an ownCloud server authenticating against and Active Directory server, but the biggest problem I’ve seen is the mapped usernames end up being long strings of numbers in ownCloud.  Although the display names are correct in owncloud, the actual username for all AD mapped logins, by default, are a long unique string makes things difficult.  For one, if you need to get to a users ownCloud data folder, there’s no intuitive way of knowing who’s is who’s folder from the command line.

With this step-by-step guide, you will have your ownCloud server authenticating against Active Directory / LDAP, with the following benefits:

 

  • The ownCloud username will match the Active Directory / LDAP username (no long incomprehensible string of numbers)
  • Any user added to a specified group created in Active Directory will automatically have ownCloud login privileges.
  • ownCloud users will be able to login using their username or email address (if specified in AD) interchangeably.

These three pluses make everything very seemless and saves a lot of headaches. So, lets get started.

Click Here to Continue Reading!