Setup OwnCloud on 1@1 Shared Hosting

The OwnCloud LogoThe OwnCloud Project


Just to give a general overview of this project, recently I acquired this domain and being the tinkerer that I am, I wanted to see if it would be possible to deploy a OwnCloud instance onto my 1@1 Linux shared hosting platform.  Now my initial reaction to this was that it wasn’t going to work mainly because OwnCloud is a file sharing system that requires a wide ranger of prerequisites that I didn’t think were supported by 1@1.  Now 1@1 says it doesn’t support OwnCloud hosting on its Linux shared hosting environment, but i’m here to tell you that it is possible and you can very easily setup and create a OwnCloud instance to run along side your existing WordPress, Joomla, or other CMS type sites.

OwnCloud_Offical Website | OwnCloud_Documentation

NOTE: This is going into a 1@1 Linux Shared Hosting Enviroment, please do not expect to be able to setup SSL (unless you have SSL)or edit any configuration files as 1@1 keeps almost all system files locked down. This is going to be a very basic setup/usage of OwnCloud.  I would not advise using this is you are concerned about security.

Section 1.0: Acquiring the Installer

To download the files necessary for OwnCloud please visit the OwnCloud_Installer_Page.  You will want to download the “Web Installer” as this package is designed to run on various shared hosting platforms. Once you download the package you will need to upload this file to your 1@1 shared hosting platform.  I did mine via ftp, I would have done this via terminal and wget but my 1@1 package didn’t support the command.(I really am serious when I say they have it locked down) I put mine in 1@1’s “/” directory  since this is usually what your “FTP” or “Webspace Explorer” will default to.  In this folder I created a folder named “OwnCloud” to store the file.

Install _ ownCloudInstall _ ownCloud_Shared_Hosting

1@1_Control Panel

Section 2.0: Creating a Sub-domain in 1@1

After uploading the OwnCloud “Web Installer” to a place of your choosing you will need to setup a “Sub-Domain” manually on the 1@1 control panel. This is really simple to do, so please follow along with theses steps.


You will first need to log into your 1@1 control panel, and locate the “Domain Center”icon and click on it.  This will redirect you to a “Domain Overview” that will allow you to view/setup new sub-domains.  Drop down the “Add Domain” box and select “Create Sub-Domain”.  Next you will need to assign a name to the “Sub-Domain” and create it.  Domain-Center_Control PanelSub-domain_Domain CenterCreate_Sub-Domain_Domain Center

Congratulations you have now created a “Sub-Domain” but you will need to do one last thing before you are finished with it.  After you create the “Sub-Domain” you will need to specify what folder that “Sub-Domain” should look into.  In the “Domain Center” you will be able to expand your “Primary Domain” and select the new “Sub-Domain” you created.

In the next window you will have to edit the location of the new “Sub-Domain”.  I placed mine in a folder that I created in my “Webspace Explorer” called “OwnCloud”.  So summing this up when I go to “” 1@1’s DNS servers will look into this folder for any OwnCloud files.

NOTE: The OwnCloud  folder where I put the “OwnCloud Shared Hosting Installer” we downloaded earlier.

Sub_Domain_Settings_Domain Center

Section 3.0: Create  a MySQL Database for OwnCloud

ATTENTION: Please write down/store or remember the following settings/credentials as you will need them later on when you setup OwnCloud!

Next we will need to create a MySQL Database for OwnCloud.  From the 1@1 Control Panel you will need to locate the “Manger Webspace” section and click on “MySQl Database”.  This will bring you to an overview page of all your current MySQL Databases.  From here you can click on “New Database”, a new window will appear that will allow you to set a description of the database along with it’s password. After finalizing this window you can click next and 1@1 will give you an overview of the database that you just created.

1@1_Control PanelMySQL Databe_Control Panel MySQL Databe_Overview_Control Panel MySQl_Database_Settings_Control Panel

Section 4.0: Finalize your 1@1 OwnCloud install

Now we can finally get OwnCloud up and running on our 1@1 shared hosting environment.  On a web browser of some sort point your browser to “” and you will be presented with OwnCloud’s “Setup Wizard”.  It may check for some dependencies first then ask you where you would like OwnCloud to install to.

OwnCloud_Setup_Page_Wizard OwnCloud_Setup_Page-Dependiency

By default OwnCloud  we launch the OwnCloud installer from /OwnCloud.  OwnCloud will try create a new folder named OwnCloud and try to install to /OwnCloud/OwnCloud. You can either accept the default which is fine or you can leave it blank to install it into the current directory. After this you will be presented with a window saying OwnCloud is now installed. Click next and you will be redirected to the final setup page.

ATTENTION: Never give the Administrator user and MySQL user the same credentials.  If a hacker gained access to your MySQL Database they will be able to see all users passwords and files.

Create a Username and Password for your OwnCloud administrative user then supply the information that you saved from earlier about you MySQl Database. After the correct information is entered you will be redirected to your OwnCloud dashboard.  From here you can explore, create new users, and add apps.


I will be going into more details for exploring, create new users, adding apps and other function in a later post.  If you guys or gals have anything to add or just general questions please feel free to leave a comment below and I will get back to you.


Thank you


One thought on “Setup OwnCloud on 1@1 Shared Hosting

  • I will be going into more details for exploring, create new users, adding apps and other function in a later post. If you guys or gals have anything to add or just general questions please feel free to leave comment below and I will get back to you.

Leave a Reply