Continuing last post, we will finish the installation of Nextcloud, create a self-signed HTTPS certs, and port-forwarding 443 to our server so that we can access it from the public internet. Install Nextcloud dietpi-software Then go to Software Optimised, under Cloud/Backups, hit spacebar to select Nextcloud, then back to the main menu, select Install. If it installs correctly, you can now access Nextcloud from: http://your-server-ip/nextcloud It should show you the login page....

This is something that has happened on my home and work network. Perhaps you set up a personal website on a raspberry pie that is inside your home network. You get everything up and running, you have destination NAT or port forwarding configured on your home router. You buy a domain and set up A-record with your home’s internet IP. Everything is great and you can access your website from the internet....

Asymmetric routing means that the request packets are sent to one gateway, but the response packets are received from another gateway, that is, the returning packets are taking a different path. Normally this wouldn’t be problematic as the end devices don’t really care about which gateway they receive the packets from. However, asymmetric routes become a problem when NAT is used or having a firewall in between the network. When a firewall receives a response packet that it’s unaware of the original flow, it may consider the response packet invalid and drops it....

Recently I’ve been tinkering with RockPro64 and decided to install NextCloud on it as a medium to sync data between my computers and phones, as well as using it as a backup storage. The setup is as follows: RockPro 64, 4GB RAM, with 32GB Micro-SD card, PCI-E to SATA-2 adapter Operating System: Dietpi based on Debian “buster” Two 1TB Hard drives that will be used for RAID 1 Array Encrypted Storage with LUKS and LVM2 Nextcloud installation Self signed HTTPS Dynamic DNS and port forwarding port 443(HTTPS) to the NextCloud using a Mikrotik router In the following series of post, I will walk through the above setup one by one, provide the necessary configuration and information to complete the above setup....

On my previous post I wrote about how an unmanaged layer 2 switch is possibly the culprit of AP failures. My solution is to connect the APs directly into the Fortigate firewall. Since our topology is simple it only requires a simple solution. This post I will walk through that solution step by step. There is already an offical document from Fortinet on how to do so. However, it only explains how to connect 1 AP to the Fortigate....