The scope here concerns use of VPN (Virtual Private Network) to gain secure access from the public network to a local private network. It relates to private secure access and use from the public network. It does not consider public VPNs setup for public use.

There have been considered 3 different levels of access as described by the applications used:

• Nextcloud - a full privately hosted publicly accessible file shareing application, with many additional features
• Privatebin - An encrypted file publicly accessible file sharing server
• Syncthing - A files synchronising system
• Wireguard - A VPN server

These applications and their scope are described further below.

Nextcloud is an open source content collaboration platform. At its core is file-sharing, but it has many other core functions as well as extensibility with additional installed applications. While Nextcloud can securely share files it is not focused as a simple, public, and secure file-sharing platform.

I have been using Nextcloud and before that Owncloud from which Nextcloud was forked since circa 2013. My server setup is described here:

• kptree nextcloud is Docker based setup, that I currently use, since 2022.
• kptree nextcloud is a VM setup previously I used.

• Syncthing
  • getting started
• Syncthing Getting Started

• The Linux Code How to Use Unison for Seamless File Synchronization Between Servers
• Arch Linux Unison manual
• UNIX / Linux: HowTo Use unison File Synchronizer
• GIT Unison
• Unison Website superseded

• Linux incrond inotify Monitor Directories For Changes And Take Action

I previously successfully setup wireguard on my router. This was installed on “bare metal” as was the nftable based router firewall. I later installed Bind9 DNS and Kea DHCP programs in Docker containers. I always run Docker in a VM to prevent Docker's packet filtering from affecting the bare metal firewall rules. I did not move Wireguard to a Docker container as I did not have the need at the time.