
- #Bitnami owncloud trusted domain verification
- #Bitnami owncloud trusted domain software
- #Bitnami owncloud trusted domain code
My request was approved via domain verification using a temporary CNAME entry. Also, choose the web server type as apache2.īecause I couldn't receive emails from the domain that I used (for lack of MX records), I worked with Comodo technical support over a web chat session. You would need to fill out a request form on Namecheap's web page using the blob in the generated.
This is important because of the recent Chrome controversy about deprecating SHA-1. On the VM, run the following to generate a key with SHA-256 hash. Next, prepare for the certificate signing request (CSR). We need to create a private key first with the following command. (Note, Namecheap's certificates use Comodo as the certificate authority.) I acquired a cheap SSL certificate from Namecheap, where its PositiveSSL single-domain certificate cost only $9 a year, and it is available almost instantly, pending domain ownership verification.
Access the web UI using the host name and make sure it works. I decided to just modify the PHP file directly, and only allow accessing from that host name. Change the trusted domains settings in ownCloud to use the host name instead of that IP address. Note that the IP address is temporary, we need to set the TTL to something as short as a few minutes. Create an A record for the host DNS name such as, and assign the current ephemeral IP address to it. I used Google Domains to register a domain name that I liked, which is reasonably affordable. Now that the ownCloud was live and well, I still needed to further configure secure access. Do restart the ownCloud stack after the change. I find that the Bitnami way to be much easier to work with. #Bitnami owncloud trusted domain code
The ownCloud way is a bit kluncky as it requires code change. I have learned to make this adjustment before configuring any desktop clients. Since I only intend to run ownCloud alone on this VM, I would very much like it to run from the root path. This is intended for installing ownCloud on a shared web service. If the answer is no, you can manually start it by running the following script from the installation directory.īy default, the Bitnami installation runs ownCloud from the web URI of /owncloud.
Choose production settings ( i.e., option 2) for the installation type.Īt the end of the installation, the script asks you if you want to launch ownCloud. Do not use the internal IP, even though it is the default setting. Since you always need remote access to the VM, consenting to the internal IP would prevent you from accessing the web user interface (UI) without having to change the trusted domain further.
Choose the external IP address for the Ubuntu VM instance running in Google Compute Engine. Email is optional since I don't intend to enable SMTP for ownCloud.
Admin user info (username, password, and a descriptive name). Only a few essential items needed I to be prepared before the installation. The first option turned out to be my natural choice.Īfter having downloaded the Bitnami installer on my Ubuntu image (via wget), I simply ran the installer script (via sudo). Deploy the Bitnami installer for LAMP stack, and then add the Bitnami module for ownCloud.įor my purpose, I wanted something to go live in hours, so I wanted to fiddle as little as possible.
Deploy the standalone Bitnami installer for ownCloud. There are two ways one can use Bitnami stacks. So I chose Bitnami, who specializes in packaged solutions for easier deployment. It could get quite complex if one has to deploy the ownCloud software, as well as all the necessary dependencies on a VM. The complete stack of ownCloud requires a web server supporting PHP (such as Apache), and MySQL as the supporting database. Doing so would add the tags http-server and https-server to the instance, allowing the native firewall to open ports for the VM. I made sure to select both "Allow HTTP traffic" and "Allow HTTPS traffic". (There are commercial file sync solutions that address this issue by design, including SpiderOak and Wuala.)įirst, I created an Ubuntu image with in Google Compute Engine. With virtual machines (VM) available from IaaS providers, it is conceivable that one may be able to run ownCloud in a public cloud, so that a personal version of Dropbox can be had without dealing with concerns of security and privacy issues. #Bitnami owncloud trusted domain software
Traditionally, ownCloud is a software package that is deployed on-premise. The first thing came to mind was ownCloud, an open-source alternative for document sync solutions such as Dropbox, Box, etc. To take a test drive on this favorite operating system of mine, I decided to deploy an application on the new operating system. Google Cloud Platform recently announced the availability of Ubuntu images for Google Compute Engine.