talmania

Members
  • Posts

    194
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

talmania's Achievements

Explorer

Explorer (4/14)

2

Reputation

  1. Just curious if anyone has moved to NextCloud 22? I noticed current rev is 22.2 (running 21.0.5 here) and wondering if moving to 22 is a technology challenge (requiring a manual install) or simply a channel release thing? Thanks!
  2. To get some GPU integration I upgraded to 6.9rc2 and everything went perfectly fine. Everything that I've tested has worked as expected save for 10Gbe transfer speeds which have become slower and unpredictable. I've run iperf3 and found it maxing out at the speeds of my SSD's as it did pre upgrade at 500MBps. Since the 6.9rc2 upgrade I've found my transfers to be erratic with occasional speeds hitting 350MBps but mostly in the 150-225MBps range. I've confirmed that directI/O is still enabled and nothing else has changed. I'm going to turn on jumbo frames for testing but never had them enabled before and was hitting a constant 500MBps without fail (occasional drop when loaded or mover running of course). Thanks! Edit: My 10gbe adapter is an X540-T2
  3. Hi all---I replaced my cache drives the other day and found when i turned back on dockers that nothing was listed at all. So I added back in my templates and that seemed to work just fine save my swag docker. Long story short, I ended up renaming the entire /config folder (which was a LONG time in use from very early letsencrypt days) and and seeing if a complete reinstall worked. Got caught with the rate limit of letsencrypt. Is there a way I can move over the certs that were generated in the old /config structure? Thanks! RESOLVED: In case anyone comes across this I came across a thread about CA Backup/Restore and completely forgot the app was running on my system. Did a restore of everything and it's working perfectly now.
  4. Thank you! That worked just fine--appreciate the help!
  5. Thanks--so just delete, download and use same settings/paths as previous and should be good?
  6. Is this a drop-in replacement for the old Bitwarden? Give it the same name and settings and good to go?? Thanks
  7. I've been running the following for a LONG time (easily 8+ years) and am looking at doing more (virtualization & conversion, maybe gaming) from my system. Here's what I currently have: Supermicro X8SIL x3470 Xeon 16GB ECC 4220 Norco 20x 3.5" HS 2x MV8's 10TB Parity 10x 3-4TB legacy drives that are getting phased out 5x 10TB drives 2x 512GB Samsung EVO SSD Cache My only real requirement is virtualization support, ability to handle more than 1-2 converting streams at a time and my MOST important is Lights out management (iLO, DRAC name your flavor). My thought was keep the 4220 (upgraded fans & PSU) since I've got the open bays and will be further consolidating legacy drives but everything else is up for replacement. Thanks for any and all suggestions!!
  8. Another question for cheesemarathon or others: how are you backing up Bitwarden? I've read multiple GitHub recommendations but a lot of them refer to pulling in a docker that contains the sqlite3 bits etc. Wondering how you would recommend backups cheese? Thanks!
  9. Thanks Cheese!! Great to hear--appreciate your work!
  10. Question regarding Bitwarden---I can see there's a bitwarden_rs here that's forked from the one by dani_garcia. The one by dani_garcia has a Duo version that's what I can only assume is working towards adding the Duo functionality (I'm not a GitHub/programmer so it's mostly Greek to me) but curious if there are plans to ever have Duo working in the Unraid published version? I've subscribed to Bitwarden but would rather host it myself and using Duo would be really nice.
  11. I've found that when accessing Nextcloud via my iOS phone client externally that it takes approximately 30-60 seconds to "wake up" and connect with the server--until then it appears like a non-responsive hung app and clicking various areas of the Nextcloud iOS app do nothing. Internally it connects immediately via the app and website; externally it connects immediately via a browser--this change probably happened close to the 15.0 upgrade. Anyone seen this before and have any insights or places to start looking? Thanks!
  12. It would not surprise me in the least---China is know for their rampant theft of IP. If I was a major decision maker in a corporation with sensitive data I wouldn't be using Supermicro boards.
  13. kizer is spot on--the community here is incredible--I've had my butt saved by incredible members here. I've been using the same license (and same USB key now that I think about it hmmm) since buying a 1TB drive was considered HUGE and cost prohibitive. If you look at the cost of my license over the last decade plus, it's amounted to absolute peanuts.
  14. EDIT: Sometimes typing something out can REALLY help. It occurred to me no more than 10 minutes after publishing this post that these lines jumped out at me: #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; I commented out those extra authentication steps and IT WORKS! I guess I was close and not as stupid as I thought--would love to hear best practices moving forward and if this approach in sites-conf/default is preferable to /proxy-conf/app.subdomain.conf and what the distinction is. Leaving this here in case it helps someone down the road. I've been running letsencrypt perfectly with Nextcloud for years now thanks to this awesome community---I've recently decided to try more dockers than just Plex & Nextcloud (specifically Bitwarden but my questions are primarily around letsencrypt) and I'm trying to learn how to publish more than one docker. I've jumped back to square one and learning about the configs etc (from watching spaceinvader videos and reading articles at linuxserverio) and feel like I'm SUPER close but missing something subtle somewhere (or maybe just think I'm closer than I actually am). I've got DNS working for a custom domain (was already working for nextcloud) for bitwarden, created the new docker network and moved the containers over to that network for communications (as I understand it is necessary) and then passing the bitwarden subdomain to letsencrypt successfully after working with the nginx/proxy-confs and creating a bitwarden.subdomain.conf file and then realizing there's default in nginx/site-confs that looks like the following and when I would hit bw.mydomain.com externally I'd land on the nextcloud landing page. server { listen 80; listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name nextcloud.mydomain.com; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://172.23.1.31:444/; } } So I tried several things from that point: 1) added a line to reference the proxy-confs (with the *.subdomain.conf file I created) with an include statement in the site-confs/default (which ended up in errors in letsencrypt log on startup). 2) ignored the proxy-confs all together and added the following to my sites-confs/default after the above code: server { listen 80; listen 443 ssl; server_name bw.mydomain.com; include /config/nginx/ssl.conf; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_Bitwarden Bitwarden; proxy_pass http://172.23.1.31:8343; } } I no longer land on the nextcloud landing page but get a generic prompt for a username and password for authentication and get no further (I can access the docker internally no problem). I've tweaked more than a few I'm curious what best practice is? Is it to use the proxy-confs or to use site-confs to address the various services? In my research I've seen it done both ways...thanks in advance for any and all advice/help!