corradojeff

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by corradojeff

  1. Hello, I had a previous issue with a full cache drive causing problems with mover and appdata. I don't know what I messed up in my quest to fix that problem but after I sorted that mess out I had an error where my docker service randomly stopped and unraid was "signed out". I could still access some of my dockers webgui through manually typing the address in my browser. For example: Plex still worked no problem. I ended up replacing the USB drive as part of troubleshooting and all was well. Fast forward a month or so and I am getting the same errors again with the docker service. Docker Service appears stopped but I can still use plex, access webguis, and unraid appears "signed out". If I try to restart unraid the array wont stop and I get the error "RETRY UNMOUNTING USER SHARE(S)". An ungraceful shutdown and restart fixes the docker issue but I would like to fix it for good. Any help would be appreciated. utopia-diagnostics-20220214-1915.zip
  2. I am using MariaDB for nextcloud which was functioning well now all of a sudden its dead slow. Have this same UMASK in my logs.
  3. Figured I would loop back on this for posterity. I am still not sure what happened but my downloads share was on cache and that's what filled it up. It must have been a mis-click on my part. I ended up backing up appdata, domains, and system shares and reformatting. After transferring all data back I still had the issue with dockers. I ended up backing up the .confs (and any other db/config files for each docker) and wiped app data and docker.img and started fresh. I am now in the processes of setting up a second unraid server to send across country for backup.
  4. Hello, I need some help figuring out an issue I am having. I decided to add a second cache drive and create a cache pool and now my dockers open like they are fresh and need to be set up again. To add the cache drive I: - Stopped docker and VM service - Set all shares to Cache:Yes - Completed mover - Stopped the array - Added second ssd and formated both for btrfs - Setup pool with original and new SSDs - Started array - Set my appdata, system, and domain shares to perfer cache - Invoked mover - Started docker and VM services. Now when I open up any dockers like nginx proxy manager or nextcloud it's like they are a fresh install. It is possible that I started docker service BEFORE mover completed moving appdata back to the cache as I just left it for what I thought was more than enough time (few hours) and assumed it was completed. Of note is that my cache drive is reading full at 498 GB but the shares set to prefer cache should only be about 300GB. I did have shares set to cache:yes but I had not started docker service yet so not sure why they would have moved that data over. to cache. Also, my cache pool size says its full at 498GB but its displaying that it is 1TB in SIZE. While trying to fix/troubleshoot I am currently attempting to move all cache data back to the array by setting all shares to Cache:Yes but the mover has been running for sometime now and the cache drive READS have not increased. Please let me know if there are any additional screenshots or logs that I can provide to help diagnose. Thank you utopia-diagnostics-20220103-1231.zip
  5. I have the same issue. Users can upload files but they get an "unknown error". I get this same exact string in my logs. Did you happen to find a fix?
  6. Hi, I am having difficulties setting up NPM so that my ombi docker can be accessed publicly. Problem: When trying to resolve requests.mydomain.ca I get ERR_CONNECTION_TIMED_OUT My setup: Registrar - Google domain (mydomain.ca). The only DNS record is an A record (mydomain.ca > My.Public.IP) Cloudflare - (Changed Google DNS settings to Cloudflare's name servers). Created an A record in Cloudflare (requests.mydomain.ca > My.Public.IP) Ombi docker is setup on InternalIP:3579 NPM - Docker ports 1880/18443 - My ISP is seemly blocking port 80/443 so I created the SSL certificate using Cloudflare API token DNS challenge for *.mydomain.ca. Created a proxy host for requests.mydomain.ca with the destination internalIP:3579 and the SSL from *.mydomain.ca and ACCESS Public UnRAID Network Setting - I have tried NPM and Ombi both on Network Type: Bridge and together on their own custom network Router - forwarded ports 80/443 to 1880/18443 and tried forwarding 1880 to 1880/18443 to 18443 MISC: - whatsmydns.net shows that the DNS is working - I can ping My.Public.IP What's interesting is that I was able to setup public access to my Ombi docker by exactly following spaceinvaderone's video "How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX" with using ONLY subdomains provided by duckdns and all I want to do is use my own domain. Is what I am trying to do impossible with port 80/443 blocked by my ISP? I get the same error using https://requests.mydomain.ca:18442 Not sure if there is something I am missing but I have sunk countless hours on this. Any help would be appreciated. Thanks.