I need to get more serious with backups. I read a lot about 4-3-1 and 2-2-1 but not sure i get it all. I need to find something that works with my truenas scale setup.
I need to get more serious with backups. I read a lot about 4-3-1 and 2-2-1 but not sure i get it all. I need to find something that works with my truenas scale setup.
I second drive mirroring with ZFS. Truenas Scale has been a quantum leap for me. I have two very old Dell T110 with 32GB ram each. One, the main one, has 4x 4GB Western Digital Gold drives, which cost me a fortune at the time. I think they are in raid5 but cant remember. The other t110 has cheaper WD reds. I turn on the slave machine on saturdays to complete replication tasks. I dont have a robust backup model yet besides replicating to an external HD on a 3rd machine but will need to work on that.


I hadn’t considered the port conflict issue … probably shows how ignorant I am on all this stuff, not just on proxies … :-)


I’m picking up on this because I’m getting a bit confused. I’ve run this through docker compose using the below yaml. I’ve done it as normal user, “Fred” (added to docker group) rather than root (using sudo although it make no difference as I get the same outcome). I normally have a “docker” folder in my /home/fred/ folder so is /home/fred/docker/vaultwarden in this instance (i.e. my data folder is in here).
I get the same issue highlighted here which is all about the SSL_ERROR_RX_RECORD_TOO_LONG when trying to connect via https, whereas when I try to connect via http, I get a white page with Vaultwarden logo in top left corner and the spinning wheel in the center. I’ve got no proxy enabled and I’m still not clear why I need one if I’m only accessing this via LAN. Is this something on the lines of “you must yse this through a proxy or it won’t work” thing? Although that not why I understood the from the guidance. I’m clearly missing something although not sure what exactly it is …
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: always
environment:
# DOMAIN: "https://vw.home.home/"
SIGNUPS_ALLOWED: "true"
volumes:
- ./vw-data/:/data/
ports:
- 11001:80


Thanks for sharing the other communities. I have used this forum a lot and there are some great helpers here. I really hope things don’t get a bad turn. We really need these forums to help newbies. We’ve all been there. You could argue that the typical newbie question “where do i start?” Is “low effort” but simply reading all the answers about how others approched self hosting has given me so much benefit.


I don’t have any proxy.
Nice one. I missed this
And, i can’t find clients on f-droid. Any variants recomended that dont come from the playstore.
Another key feature will be Keepass data import.
That is another problem i face when i have the app open on desktop and phone at the same time. Its a nightmare.


Readeck looks similar to Wallabag?


This is a good comment! I just discovered after your comment that floccus has a setting to link up with Linkwarden so that together, they achieve most of my desired outcomes. It just becomes more i volved in the managemente as you no end up with two components to manage rather than one ;-)


Exactly! The point really is tgat it shiuld be detecting duplicates regardless once ticked.


Mate, it was a sarcastic statement 😉


Well no. Initially i had the storage set on the VM where its running. I wasn’t expecting it to download all that data.


OK, so maybe I didn’t explain myself. What I meant was that I would like resilience so that if one server goes down, I’ve got the other to quickly fireup. Only problem is that slave sever has a smaller pool, so I can’t replicate the whole pool of master server.


Well, its ticked but not working then because I found duplicate links. Maybe it only works if you try to store the same link twice but it doesn’t work on the imported bookmarks


I was using floccus, but what is the point of saving bookmarks twice, once in linkwarden and once in browser


Looks very interesting. But as others noted, still too young, only two releases in 3 months and 1 person. Certainly to keep an eye out. The MIT licence worries me too. I always add the licence in the criteria ;-)


absolutely, none of that is going past my router.
I too have syncthing replicating across 3 machines but its only usefull if you loose one machine. Recovery of old versions of docs is tricky. Syncthing does save versions but hunting fo old versions of files in hidden folders isn’t great. It would be great if you could browse file history via browser or the file manager, similar to what happens on Sharepoint.