poeterdebier

Thanks for the info. I will have a look into this. Actually I wouldn't know. When I bought my parts I did not really considered the Intel vs AMD. Parity errors where not really on my mind around that time as I was not experienced with Unraid (still not I guess). gr Piet

Hi guys, was wondering if somebody could have a look at my diagnostics. I keep getting 28 or so errors after multiple parity check with "write corrections to parity" enabled. Attached is my extended disk checks from my spinning disks. I could not do one for the cache which is an Nvme. Also attached my diagnostics. Diagnostics taken after latest parity check. The extended disk checks all passed a couple of days ago. Thanks in advance guys. Regards Piet tower-diagnostics-20210907-1003.zip WDC_WD40EFAX-68JH4N0_WD-WX12D10JSXKD-20210904-0457.txt WDC_WD40EFAX-68JH4N0_WD-WX12D10JSZ6U-20210904-0457.txt WDC_WD40EFAX-68JH4N0_WD-WX42D10LL6FF-20210904-0458.txt

He, Guys, was wondering if somebody could help me getting Fail2Ban working. Got the following: added to jail.local [bitwarden] enabled = true port = http,https filter = bitwardenrs action = iptables-allports[name=bitwarden] logpath = /log/bitwarden.log maxretry = 3 bantime = 14400 findtime = 14400 bitwardenrs.conf (inside filter.d folder): # Named this way beacause the one bundled with fail2ban is outdated # https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup # - Set up logging to file > https://github.com/dani-garcia/bitwarden_rs/wiki/Logging # - Set logging level to warn or error # Logged in bwdata/logs/identity/Identity/log.txt [Definition] failregex = Username or password is incorrect\. Try again\. IP: <HOST>\. Username: .*\.$ ignoreregex = added -e LOG_FILE=/log/bitwarden.log -e LOG_LEVEL=warn -e EXTENDED_LOGGING=true as extra parameter to bitwardenrs and mapped a folder for the log file. See also attachment. To Let's Encrypt (or Swag) added the same mapped folder. I can see the failed log in attemps in the log of bitwarden but F2B is not doing anything with it. gr Piet

He Guys, I was wondering if somebody could give me a hand to get this HTTPS working. I would like to try Bitwarden locally only because I don't like the idea of my password manager accessible from the internet with a reverse proxy like in the video of Spaceinvader one. I tried a lot of things but I just cannot get it to work. I tried installing Caddy, Nginx Proxy Manger etc but no go. I would appreciate any help. I have Nextcloud up and running as per Spaceinvader one's video. So Let's Encrypt is working. I recently changed the repo to "swag" though. As the other repo was depreciated due to copyright issues if I understand it correctly. Side question: nobody here has any trouble with your password manager accessible from the internet? I mean (correct me if I am wrong) everybody who has the address can (try) to access you vault right? Sure there is the log in but somehow it feels less secure than an instance like openVPN or Wireguard. What are you're thoughts? gr Piet