# Getting Discourse installed on OVH VPS **URL:** https://meta.discourse.org/t/getting-discourse-installed-on-ovh-vps/23308 **Category:** Self-hosting **Created:** [21 בדצמבר,‏ 2014,‏ 5:34am UTC](https://meta.discourse.org/t/getting-discourse-installed-on-ovh-vps/23308 "2014-12-21T05:34:09Z") **Posts on this page:** 1 **Showing post:** 27
### Author: ![pl3bs](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pl3bs/32/37266_2.png) [@pl3bs](https://meta.discourse.org/u/pl3bs) #### Post date: [13 בינואר,‏ 2015,‏ 11:57pm UTC](https://meta.discourse.org/t/getting-discourse-installed-on-ovh-vps/23308/27 "2015-01-13T23:57:46Z")
I’ve created a guide which includes my solution here: > [@Guide: Getting Discourse Installed on OVH Cloud (Part 2)](https://meta.discourse.org/t/guide-getting-discourse-installed-on-ovh-cloud-part-2/23963): > > As promised, I am going to post up a guide for others to follow after spending numerous hours trying to get this figured out properly. This is a continuation from here: Where I was totally lost. This guide assumes: OVH Cloud or Dedicated Server Clean install Ubuntu 14.04LTS 64bit A Record Pointing (sub)Domain for Discourse to IP apt-get update reboot It’s my first step at new installs. Now we’re going to switch to generic kernel for AUFS support. apt-get install linux-image-server mv … My main err was assuming bind9 was of absoute importance. It wasn’t. Bind9 is necessary if you would like to host your own nameservers and run a control panel. Once I tried everything raw, the process went smoothly. I allowed godaddy to host the nameservers, created A records for each doman/sub pointing to cloud IP, then setup nginx reverse proxy on the front-end with discourse and apache vhosts on the back end. All is well with OVH when you do away with control panels, nameservers, and a need for bind9. Give me a little slack, I didn’t even know what ssh was 90 days ago, LOL! --- _[View the full topic](https://meta.discourse.org/t/getting-discourse-installed-on-ovh-vps/23308)._