The main idea of this project was to have something as reliable and as effective of what other popular solution out there would give normally (Ex: Dropbox, OneDrive, Google Drive, etc…). If you too, want to take control of your own data and stop mindlessly throwing it at some big corporation that will analyze that data for their own good, then you can with some efforts, install and run your own cloud server inside your house. I wanted to have a proper way to easily store my data in a ‘cloud-like’ environment with an acceptable service level agreement for myself so that my files are accessible anywhere and possibly retrieved in a backup in case of a problem. Simply put, your privacy and the security of your data is at stake the moment you decide to let another party handle that for you. With the increased amount of security breach happening every now and then, it’s become hard to properly trust a service provider with your personal data.Īnd then, if the breaches are not enough, most if not all providers now monitor all the files you upload for their own needs (Most of the time, to teach their AI’s to read pictures, understand word documents, etc.). Please let me know if more info is required, and I will be happy to provide.Keep your files securely in your own Cloud at Home using a simple Raspberry Pi Could something non-obvious be tying up port 443? Thanks in advance. I tried adding another port to the Duplicacy container, but I could never get this change to apply and save. I tried adding port forwarding for Unraid, but this had no effect. The error message references port 443 on my router itself (Eero), not the Unraid IP. Deleting NextCloud and restarting the Unraid server made no difference.
An incomplete NextCloud docker DID have a reference to port 443, but it was not running. I do not know where this port 443 is coming from, as no Duplicacy json file references it, nor is it listed under the container settings. When I enter Key ID, Application Key, and Bucket to recreate the storage, I see the following error in the logs:ħ 17:23:45 ERROR STORAGE_ERROR Head “ ”: dial tcp 192.168.7.1:443: connect: connection refused I ended up deleting the storage and backup info in Duplicacy and attempted to start from scratch. When trying to run the backup job I get the following error:ħ 17:23:45 Failed to check the storage at b2://SHARENAME: Head “ ”: dial tcp 192.168.7.1:443: connect: connection refused It has suddenly stopped working, and for the life of me I have made zero changes to my Unraid config since this happened. The past 13 months, I’ve had BackBlaze and Duplicacy playing nice with my Unraid, backing up files from one of my shares.
0 kommentar(er)
