perfect

I have SWAG running on my Unraid (v6.12.3) for the last few years without an issue. Recently, I received an e-mail from Let's Encrypt that my Let's Encrypt certificates expire in 7 days. I wasn't sure why I was suddenly seeing this message. I restarted the docker (and ultimately the server) and am still getting this message when running "certbot renew" in the SWAG console: root@fb4ff453e394:/# certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/Anasrp.duckdns.org.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Renewing an existing certificate for Anasrp.duckdns.org and 3 more domains Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: Abitwarden.duckdns.org Type: unauthorized Detail: 98.156.3.173: Invalid response from http://Abitwarden.duckdns.org/.well-known/acme-challenge/eUOCQd_YPD0oElb3CUNDwdaAaELTmY08jIHlMKi7IK4: 404 Domain: Anasrp.duckdns.org Type: unauthorized Detail: 98.156.3.173: Invalid response from http://Anasrp.duckdns.org/.well-known/acme-challenge/StQ2pSQqV1BM2ecxkSlA-inT3y4nYuKC8gKZpWRtP4k: 404 Domain: Anextcloud.duckdns.org Type: unauthorized Detail: 98.156.3.173: Invalid response from http://Anextcloud.duckdns.org/.well-known/acme-challenge/UIY3Tai7Bxp77hc_s9vGoajYm0CwxgoLT2g58gLOBUw: 404 Domain: Aoverseerr.duckdns.org Type: unauthorized Detail: 98.156.3.173: Invalid response from http://Aoverseerr.duckdns.org/.well-known/acme-challenge/7prnLRprrrzttvcKjCqu5A24DffX5kc9t9R1HzS6J4E: 404 Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet. Failed to renew certificate Anasrp.duckdns.org with error: Some challenges have failed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/Anasrp.duckdns.org/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 renew failure(s), 0 parse failure(s) Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. I'm having a hard time understanding these messages. Are all of my certs failing or just the "Anasrp" cert? How do I fix this issue and ensure that my reverse proxies are still working? Note - I faced a similar issue a few years ago when the Let's Encrypt certificate was updated and my Unifi router needed to be updated in order to resolve the issue.

I feel like this should be a well documented process, but I couldn't find anything in the help manual specifically for how to upgrade / replace a small cache with a larger cache drive. I watched a few videos and have read several threads, but they don't show the same dialogues or options as my current version (v6.12.3). I'm simply trying to replace my 256GB SSD cache to a 1TB SSD cache. Most of my shares are using Cache -> Array, but my Appdata, Domains (VMs), and System shares remain on the Cache and are taking up about ~100GB and I'm frequently running out of room on the cache when transferring large amounts of data. Is there a guide or document that explains the correct procedure for replacing a cache drive with a larger version? I do not have enough free SATA ports for a cache pool. I found several older threads that used the following general process: 1. disable VM(s) 2. disable docker 3. change all shares to cache=yes 4. invoke mover, wait for it to finish 5. change drives 6. move everything back to the cache 7. re-enable VMs and Dockers My shares do not have an option for "cache = yes". Instead, I have primary and secondary storage choices and a "Mover Action" (Cache -> Array ... or ... Array -> Cache). I'm doing my homework before attempting this upgrade since I'm concerned about ruining my VMs or Dockers ☠️

Thanks much for the support - I did that and continued updating all the way to the "latest" version. Now it works again! Is there a way to "pin" this version so that it doesn't update [with the docker "update all" command]?

Thanks for the tip on how to delete .step file (I had to use Krusader to delete it since I didn't have permissions via Windows sharing). I was able to update the docker container all the way to v25.0.9... but I am still not able to access the GUI from either the internal IP or external (SWAG) link... (do I need now set the nextcloud container to the latest version - instead of 21.0.3-ls143)? Both my internal IP (x.x.x.x:443) and my external address (via SWAG) keep giving me this 404 error:

Count me in the group that learned the hard way that you can't update the Nextcloud docker directly from the Unraid GUI. I was on a pretty old version (21.0.0.18) and have spent hours trying to figure out how to correctly upgrade (or rollback to the previous working version). I tried following this guide: https://info.linuxserver.io/issues/2023-06-25-nextcloud/ I currently have installed repo: linuxserver/nextcloud:24.0.12 I tried running the "docker exec -it nextcloud updater.phar" command but it seems to be stuck at Step #3 (creating a backup) and nothing I do seems to release it or restart it. I can't see my GUI nor access Nextcloud from internal or external (SWAG) links. I end up getting a 404 error (maybe I need to edit my SWAG confs???). I have a config.php file (located here: \\UNRAID\appdata\nextcloud\www\nextcloud\config ) but not a version.php - so I can't really tell if I'm even updating the php correctly. The only error I seem to have in my log file is "s6-applyuidgid: fatal: unable to exec php7: No such file or directory" Any assistance would be greatly appreciated.

Hi! I posted a very similar issue yesterday and I thought I solved my problem.... maybe not. I purchased a few 10TB HGST UltraStar HDs (https://www.amazon.com/dp/B07DPKWLJR) that were used from a datacenter refresh. I already replaced my main parity drive (a 3TB WD) with one of the 10TB HGST datacenter drives. At first I couldn't get the 10TB HGST to appear in the system until I used the supplied "power disable" SATA adapter cable. This worked for my parity 1 drive and I was able to upgrade the parity drive. Today, I tried doing the exact same replacement procedure for my parity 2 drive (currently a 3TB WD) with an identical 10TB HGST datacenter drive. Of course, I first tried using the "power disable" SATA adapter cable - but unRAID didn't see the drive. I have since tried all sorts of combinations of SATA cables, HBA card ports, power cables, mobo SATA ports, different 10TB datacenter drives, etc. No matter what I do it doesn't seem to want to find the 2nd 10TB drive and I'm stumped as to why. If I plug in the 3TB WD it immediately recognizes it (as an unassigned device). Note - I can physically feel the drive spinning up (while using the "power disable" SATA adapter cable. What should I try next? I'm following this procedure here: https://flemmingss.com/replacing-a-parity-drive-in-unraid/ I've attached my diagnostics if that helps! renfrewnas-diagnostics-20230713-1958.zip

###SOLVED### The renewed hard drives that I bought have a "power save" feature and required me to use a special SATA power cable that I guess bypasses this feature. This was included with the HDD, but I didn't consider that it was needed until I read reviews on Amazon. I was able to find the disk and am re-building my parity with the upgraded 10TB HDD! I am replacing a 3TB WD HDD with a 10TB HGST HDD (renewed from a data center pull, mostly likely). I stopped the array, removed the original parity drive and replaced with the larger 10TB drive. When I restarted the system, the new 10TB is not showing up as assignable and my system doesn't seem to recognize it. I tried a 2nd 10TB HGST HDD (bought from the same source) and that doesn't show up either. Here are the drives that I bought in case that matters: https://www.amazon.com/dp/B07DPKWLJR I bought 5 of these HGST 10TB drives to upgrade my system - not off to a great start!

I might have actually solved my problem... My home router is a Unifi USG PRO-4. I did some reading and discovered that SWAG (Let's Encrypt) has been experiencing a certificate expiration issue since 9/30/2021 (right around the time that this started). This page really helped me better understand the issue. I did a firmware update to my USG PRO-4 and restarted my SWAG docker... and everything works now!!!

Awesome - thank you! That was a relief!!

I was able to safely roll back to 6.8.3, but all of my dockers and VM are missing. I have backups (from my flash drive) that I took before I did this. How can I restore them?

This was what I was afraid of... Can I roll back to 6.8.3? Edit - I'm restoring back to 6.8.3 now...

There are no errors on the Main page for any of my disks. No SMART warnings in the dashboard either. I have not run a memtest. I just setup the syslog server (to flash) and will monitor if a crash occurs again.

Yesterday, I upgraded from 6.8.3 to 6.9.2. At some point last night, my server went offline (crashed?). I restarted it manually and upon restart the parity check began. The parity check started off smoothly (~130MB/s), but soon slowed to a crawl (5.7MB/s - and dropping). I have stopped all of my dockers and VMs. I've attached the diagnostics. Note - I have a 30TB array (10 x 3TB + 2 x 3TB for parity). It usually takes me about 8 hours to complete a parity check. renfrewnas-diagnostics-20211014-1026.zip

I'm having a recent issue with SWAG that I need help to solve. Specs: Unraid version 6.9.2 (rebooted earlier today) SWAG (linuxserver) - up-to-date Problem: My duckdns subdomains will no longer work and I can't access any of my reverse proxies (on or off network). This all worked fine a few months ago. My ports are forwarded for 80 and 443 (I can see both ports as open using https://canyouseeme.org/) SWAG LOG: (redacted some private info) ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=duckdns.org SUBDOMAINS=cdrA,cdrB,cdrC EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http CERTPROVIDER= DNSPLUGIN= EMAIL=REMOVED STAGING=false grep: /config/nginx/resolver.conf: No such file or directory Setting resolver to 127.0.0.11 grep: /config/nginx/worker_processes.conf: No such file or directory Setting worker_processes to 4 Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d cdrA.duckdns.org -d cdrB.duckdns.org -d cdrC.duckdns.org E-mail address entered: REMOVED http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Requesting a certificate for cdrnasrp.duckdns.org and 2 more domains Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: cdrA.duckdns.org Type: unauthorized Detail: Invalid response from http://cdrA.duckdns.org/.well-known/acme-challenge/nJv_R9lJk8sxZtsoGX1gkZySREMOVED [98.156.3.999]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>" Domain: cdrB.duckdns.org Type: unauthorized Detail: Invalid response from http://cdrB.duckdns.org/.well-known/acme-challenge/VMwvJ3ck1dFUxwL12FG1CzRtmrs8REMOVED [98.156.3.999]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>" Domain: cdrC.duckdns.org Type: unauthorized Detail: Invalid response from http://cdrC.duckdns.org/.well-known/acme-challenge/7jQsQISoHcKOZpF_ajOE-AcDxz_REMOVED [98.156.3.999]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>" Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet. Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Thanks for the prompt response! I actually still have a lot of available storage left on my array and am avoiding buying a new HD (at current prices). I'm only at 50% storage usage on my 30TB array - and this particular drive is only using 1.5TB total. Is there a way that I can safely transfer the 1.5TB data from this disabled drive onto another drive and simply unmount disk3? I will then remove it from the array permanently and let the data live on the rest of the array. Is there a procedure for this?

I've attached the diagnostics file - thanks! renfrewnas-diagnostics-20210810-0915.zip

Hello! I am running Unraid v6.8.3. I recently experienced a disabled disk in my array. The contents of the disk appear to be intact (I can still navigate into the disk and access the files). I have several other available disks that I can transfer the data onto. I plan to remove this disk since it's apparently having [reallocated] sector errors. I read several threads on the topic and most link to a deleted page: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive I'm happy to post any logs - but wanted to check here first so that I don't lose any data or screw up my array.

I'm running Unraid OS Pro v 6.8.3 and have been using the Home Assistant (HASSIO) VM almost flawlessly this entire time. I am using SWAG as a reverse proxy (with duckdns). Occasionally, I have had instances where I couldn't connect to my Home Assistant VM (maybe once a month), but a quick reboot of the VM always solved the problem. Today, however, I have not been able to connect to my Home Assistant VM at all. I can see that the VM is grabbing an IP address (it shows up in my Unifi Controller), but I can't access the HA GUI via my external duckdns link or even my internal IP address. I can run the console (left click on the VM > VNC Remote) for HA... so I'm pretty certain that Home Assistant is actually running. When I run an external port checker test on the 8123 port, it says it's closed (I'm certain it used to say open) but... my internal IP address doesn't work either. I can confirm that I do have the port forwarding still setup in my Unifi Controller. I'm stumped... I haven't changed anything my Unraid config, HA configs, or even my Unifi Controller in a long time. Any ideas on where to begin troubleshooting next? Thanks!

Has anybody experienced an issue where SWAG (formerly "LetsEncrypt") will inexplicably stop resolving the secure connection when using duckdns? I've been setting up Bitwarden using SWAG as my reverse proxy. I've properly forwarded my ports and I'm confident that I've correctly configured SWAG, BitWarden, and the necessary .conf files. I will check the SWAG log and it will say "Server Ready" for all of my duckdn subdomains. Life is good. I can access BW from my internal computers, my phone, and my work computer. Then, things will just stop working... I can no longer access BW using the duckdns link. The log file will start saying "Certificate Not Found, etc". Nothing has changed in my config... I'll restart my router, the NAS, and restart the SWAG docker a few times. Then - just as I'm pulling my hair out - I'll go for a run or walk the dog and come back to find that everything is working again. Is duckdns not reliable? Is anybody else experience this issue?

I'm following SpacedInvaders Reverse Proxy setup video and am running into issues with the validation test (like many others). I have setup a duckdns.org subdomain. I have attempted to forward the 1443 and 180 ports in my Ubiquiti USG Pro-4 router. However, I'm getting the same validation errors that many others get ('cert does not exist, check port forwarding or dns'). I notice that when I use a port checking utility online, that my 1443 port is never actually "open" - even though I'm certain I have the port forwarding rule setup correctly (pointing port 1443 to port 443 on the unRAID IP). Any advice where to start troubleshooting? I'm doing this to setup the BitWardenRS docker. I'm using the latest SWAG docker, but I updated the config file to point to ports 180 and 1443 (just like in the video).

Thank you both for the help and guidance! I realized that I still had an active port forward to my previous IP (when I was running HA as a VM on my Win7 machine). I deleted the old/unused Port Forward rule and then made the HA VM (via Unraid server) the primary port forward IP and it completely worked. It looks like my Unifi controller can't have more than one IP assigned a port forward rule (which makes complete sense...) SOLVED

I am trying to correctly setup port-forwarding for my Home Assistant VM via Unraid. I have manually set a static IP for the HA VM ip (via Unifi router... using the MAC assigned from the VM), but I cannot access HA from the external IP. Testing the port forwarding continues to tell me that the port is closed. My Unraid network settings are as follows: Enable Bridging = Yes br0 Routing Table = 192.168.1.0/24 (Metric 210) My HA VM is set as follows: Network Bridge: br0 Note - I can access the internal (local) IP of Home Assistant without an issue. So the issue is definitely that port-forwarding is not working correctly. I suspect that either my Unraid network settings aren't correct - or the VM isn't configured to use the network settings correctly. Thanks for the help!

Frank, Thanks very much for the support. At this time, I ended up just using a different computer (mobo+CPU) since I was tired of fighting the Gigabyte/Athlon combo. I now successfully Unraid installed (albeit, not on the computer I originally intended). It is still strange why the boot sequence never initiated, but would for any other USB boot drive I tried to install. The new computer booted up with all of the USB drives correctly, so I'm still not convinced it was an issue on my end (but I'm a newbie, so who knows?!). I do believe that I followed the manual method correctly, but I don't remember specifically (I tried and tested quite a few different combinations). I had a variety of different USB drives - Kingston, Samsung, Sandisk, and some other generic varieties. Thanks again for the help! I'm happily running Unraid and diving into all of the quirks and features!!

Frank - I tried both ways (it was originally EFI- so I renamed it to just EFI and it still didn't boot. Note - I'm also trying all of my USBs (5 of them) with a different machine and it still doesn't work. THIS IS NOT A BOOTABLE DISK. PLEASE INSERT A BOOTABLE FLOPPY AND PRESS ANY KEY... I can't win 😞

I've tried with a 16GB stick and it still didn't work... not sure I have much smaller