Bitwarden Nextcloud

Posted on  by admin

  1. Which is the best alternative to bitwardenrs? Based on common mentions it is: Pass-import, Keepassxc, Bitwarden/Server, Bitwarden/Desktop or Nextcloud/Docker.
  2. Apr 26, 2020 The Nextcloud VM maintainer went with Bitwarden and I think it is a nice selfhosted alternative with apps for all operating systems and extensions for all browsers. There is even a CLI tool. Antoine August 1, 2020, 3:50pm.

I am trying to host nextcloud and bitwarden from the same server on my home network and be able to access both of them from the internet via https. I've purchased a domain, set up an A record for my nextcloud server at and pointed it the IP address of my router, and forwarded port 443 to the server in my home network.

This article is part of the series Build your very own self-hosting platform with Raspberry Pi and Kubernetes

  1. Deploy NextCloud on Kuberbetes: The self-hosted Dropbox


Bitwarden Nextcloud

Now we have prepared our RaspberryPi cluster to receive Kubernetes as a self-hosting platform, it's time to start installing applications !

NextCloud is an file hosting open-source software similar to Dropbox. Unlike Dropbox, NextCloud is not available as a SaaS but only on-premise which means anyone is allowed to install and operate it on their own private server. NextCloud offers individuals and organisations to gain control over their private data with a safe and secure solutions. NextCloud also provides a long list of add-ons working alongside the file sharing solution such as: Calendar & Contacts management, Audio/Video conferencing, Task Management, Photos albums and more.

In this article we will learn how to safely install NextCloud on a Kubernetes environment and configure both Desktop and Mobile access from anywhere.


In order to run entirely the tutorial, we will need:

  • A running Kubernetes cluster (see previous articles if you haven't set this up yet)
  • A domain name in order to access our NextCloud instance from outside our network. (replace by your domain)
  • Have a external static IP (usually the case by default)
  • Access to your router admin console to port-forward an incoming request to our Kubernetes Ingress service.


We are going to isolate all the Kubernetes objects related to NextCloud in the namespace nextcloud.

To create a namespace, run the following command:


The first step consists in setting up a volume to store our NextCloud data (files and database). If you followed the previous articles to install and configure a self-hosting platform using RaspberryPi and Kubernetes, you remember we have on each worker a NFS client pointing to a SSD on /mnt/ssd.

1. Deploy the Persistent Volume (PV)

The Persistent Volume specify the name, the size, the location and the access modes of the volume:

  • The name of the PV is nextcloud-ssd
  • The size allocated is 50GB
  • The location is /mnt/ssd/nextcloud
  • The access is ReadWriteOnce

Create the following file and apply it to the k8 cluster.

You can verify the PV exists with the following command:

2. Create the Persistent Volume Claim (PVC)

The Persistent Volume Claim is used to map a Persistent Volume to a deployment or stateful set. Unlike the PV, the PVC belongs to a namespace.

Create the following file and apply it to the k8 cluster.

You can verify the PVC exists with the following command:


In the next part, we are now going to deploy NextCloud using the stable/nextcloud Helm chart.

1. Download the Chart values of the chart locally

Run the following command to download the Chart values into the local file nextcloud.values.yml.

If you open the file, you will see the default configuration values to setup NextCloud. Instead of using the flag --set property=value like before, we will use the file nextcloud.values.yml to make all the changes.

2. Update the values

We now need to update a few properties before installing the Helm chart. Open the file nextcloud.values.yml and change the following properties (replace the information surrounded by with your information).

Nextcloud Keepass

Take a look at the file if you want to make more customisation to NextCloud:

  • Configure emails
  • Configure an external database or deploy a MariaDB as part of the Chart (improve performance)
  • Configure Redis server (improve performance)

3. Install the Chart

Bitwarden nextcloud installBitwarden

In the part, we will install the Helm chart under the namespace nextcloud with nextcloud.values.yml as configuration file.

After a couple of minutes, check if the pod and service is up and running:

4. Debugging

You can check the logs with the following command:

Otherwise check the folder /mnt/ssd/nextcloud/data/nextcloud.log.

Outside access

This step is configured before the ingress in order to be able to issue a certificate automatically when we deploy the ingress

The next part consist to enable the connections to NextCloud from outside so you can access your data from anywhere.

Bitwarden Nextcloud For Mac

1. Port Forwarding

First you need to go to your router setup and add a port-forwarding rule to map any incoming requests on port 80 or port 443 to be forwarded to (the LoadBalancer IP of the Nginx).

VirginHub - Port-Forwarding

2. Map the subdomain nextcloud.<> to your home router

First you need to find out what's your router external IP, run this command or go to

Then, we need to configure our subdomain to make sure nextcloud.<> resolves to our external static IP. Go to your domain provider console / DNS management add a record:

Bitwarden Nextcloud

  • Type: A
  • Name: nextcloud (subdomain)
  • Value: x.x.x.x (external satic IP)



At this point, the application (pod nextcloud-78f5564f89-854jr) is only accessible within the cluster on port 8080. To make it accessible from outside the cluster (on our network), we need to deploy an Ingress mapping service:port to a route of the Nginx proxy.

Because, this route will also be exposed over the Internet, we will also issue a certificate to encrypt the traffic with SSL.

1. Create the ingress config file

Create the file nextcloud.ingress.yml containing:

2. Deploy the Ingress

Now deploy the ingress:

3. Check the certificate issuance

Bitwarden Nextcloud

After you deployed the ingress, a certificate should be issued, check the certificaterequest and certificate (it might take a couple of minutes to be READY):


Alright, still with me :) You can now try to access your NextCloud instance using your browser, mobile or the Android/iOS app from home or outside via '>https://nextcloud..

Connect with the user admin and the password configured in the file nextcloud.values.yml.

You can also download the Android or iOS app and access you data, sync automatically your photos and more.

  • Kauri original title: (4/8) Deploy NextCloud on Kuberbetes The self-hosted Dropbox
  • Kauri original link:
  • Kauri original author: Grégoire Jeanmart (@gregjeanmart)
  • Kauri original Publication date: 2020-03-31
  • Kauri original tags: self-hosting, nextcloud, kubernetes, dropbox, open-source, file-hosting, helm
  • Kauri original hash: QmaKwvWjA1eTYcnE4o1gwTFvpWkegaYZZ8JRzJhzXjEyiK
  • Kauri original checkpoint: unknown