Apps that work with Nextcloud and can make use of the server encryption Nextcloud features but never allow to select only specific subfolders.Encryption can only the used with newly created folders and / or on premise hosting was not possible. Apps that feature encryption of files and folders, but do not work with Nextcloud and are proprietary solutions.In my research I found 2 types of Android apps: The issue here lay with the combination of two features I required: encryption at rest and the backup of specific, already existing folders. an Android app to only backup specific, already existing foldersĪs Nextcloud is a widespread solution for sharing files and backups, I figured my use case should be very easy to implement.Although it was far from perfect, the usage of Nextcloud fulfilled all features I required: On the Raspberry I’ve used a bare metal installation of Nextcloud, the Odroid ran a Docker image of Nextcloud. Requirementsįor months I’ve been using a selfhosted Nextcloud on a Raspberry Pi 3 and an Odroid N2. Nextcloud is far slower and the FolderSync app, which I used to transfer only specific folders, is unreliable. Tl dr: Resilio Sync hosted on a Raspberry Pi / Odroid / NUC does the job perfectly with their app. The backup has to be done locally inside the LAN and encryption at rest is a must-have. Only works when I restart the socket ( sudo systemctl restart docker.Issue: I want to backup specific, existing folders of multiple Android devices. Nothing changes when I restart the docker service ( sudo systemctl restart rvice). The unit run-docker-runtime\ has successfully entered the 'dead' state. Jan 21 22:20:10 hassvm systemd: run-docker-runtime\: Succeeded. The unit UNIT has successfully entered the 'dead' state. Jan 21 22:20:04 hassvm systemd: run-docker-runtime\: Succeeded. I'm not seeing anything interesting in journal -xab, except these: Jan 21 22:20:04 hassvm systemd: run-docker-runtime\: Succeeded. Will not be shown, you would have to be root to see it all.)ĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES (Not all processes could be identified, non-owned process info Netstat does show them as used, but they seem to be unattached to any process $ netstat -tulpn | grep LISTEN WARNING: Host is already in use by another containerĮRROR: for portainer Cannot start service portainer: driver failed programming external connectivity on endpoint portainer (c19930b176b21051089da6b6eb14c225d74a6bed867ab42bd23b61a81be794d8): Error starting userland proxy: listen tcp 0.0.0.0:9000: bind: address already in useĮRROR: for mariadb Cannot start service mariadb: driver failed programming external connectivity on endpoint mariadb (184e22f74c14126e8c5d4129e4a609b11f102ffcee9612c941e519f12e92d708): Error starting userland proxy: listen tcp 0.0.0.0:3306: bind: address already in useĮRROR: for traefik Cannot start service traefik: driver failed programming external connectivity on endpoint traefik (ddb84136d437d378547c39bceef5b06e169f2f72936cf092bd025b84eb7fc357): Error starting us Starting userland proxy: listen tcp 0.0.0.0:8053: bind: address already in useĮRROR: for influxdb Cannot start service influxdb: driver failed programming external connectivity on endpoint influxdb (c96dbf129ad4c7c1e4ffe01a281f680a0174b277c9364ae8de41d864444319f4): Error startingCreating mariadb. The strange thing, that when I attempt to manually re-deploy the stack ( docker-compose up -d), I get a bunch of bind errors: Creating influxdb. When I reboot the host, no container starts automatically even though they have a restart: unless-stopped and restart: always set.
0 Comments
Leave a Reply. |