Jump to content

madaroda

Members
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

0 Neutral

About madaroda

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    San Francisco

Recent Profile Visitors

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

  1. Terrific work, djoss. I predict this will soon be the go-to certificate manager in unraid. Questions: How would a wildcard certificate be assembled through the proxy manager? How would we go about making the LetsEncrypt cert self-renewing? Edit: Just found that Lets Encrypt wild cards don't work yet. Hope that comes soon.
  2. I moved all plugins to a temporary folder and rebooted. The "/" folder has the following permissions. So it does not seem as if a plugin is masking "/" incorrectly. I will check containers now. Any other ideas?
  3. Here's the zip. tower-diagnostics-20180925-1626.zip
  4. I'd be happy to. I downloaded the Diagnostics from the Tools page, and it is a heavily populated zip file. Which file(s) should I include?
  5. I found the problem. It appears that somewhere along the upgrade process, the permissions for the root folder ("/") were being reset to 700 on every reboot. Adding "chmod 755 /" to the bottom of the /boot/config/file fixed the problem.
  6. I'll keep updating in hopes someone runs into this: Via SSH, I made DOCKER_ENABLED="no" in /boot/config/docker.cfg; and rebooted. Still getting the 500 error on the webgui. The errors reported in /var/log/ngnix/error.log have changed slightly: The very last part (referrer: "http://10.10.10.111/Docker") is new, and came up AFTER I disabled docker altogether. How is that possible? Also I continue to get the following email from my unraid install after reboot: Could this be related? Do I need to add a user "nobody"? Gracias.
  7. UPDATE: I got SSH and webgui up again by reverting to the last saved version of my flash drive (6.3.x). I upgraded to the current version (6.5.x) and SSH continues to run. The WEBGUI is down again, though. I enter my user name and password, and the browser (any of them) now goes to a "500 Internal Server Error --- nginx" page. The content of /var/log/ngnix /error.log is now different, reading: Permissions of /etc/nginx/htpasswd are at 666. Fix?
  8. Disabled dockers as you suggested. Trying webgui through IP address now reports a "502 Bad Gateway - ngnix" page. Still no SSH access. Entering through telnet, here is the contents of /var/log/ngnix /error.log. Also, got this via email: Thanks.
  9. A couple of days ago i added letsencrypt/nginx and organizr2 dockers. I am guessing this was the start of the problems I now have. All of my docker apps are accessible via both internal IP and external https (my own domain). However: I have no access to the unraid webgui. Log files pointed to a permissions error on .htpassword. In following some instructions on fixing that, I rebooted the box. Now I don't even have SSH access with root ("Permission denied" on entering password). I deleted all the password files in /boot/config and rebooted. Only way in is through telnet. Again, all apps work, I just have no (easy) way to configure the system. How do I get my webgui and SSH access back with only telnet at my disposal?
  10. I figured out how to stop a container in the CLI. Stopping Letsencrypt did not fix the issue. I assumed they were related because it happened right after the LE installation. So, here I am, most likely in the wrong thread, and no solution.
  11. Using internal IP will not work (gets the 500 error). Trying hostname (https://unraid.mydomain.com), which in DNS is a C record to mydomain.com (IP set via DDNS on router) just gives me the NGINX "Welcome to our server" page.
  12. I configured the Let's Encrypt (nginx) docker with nzbget, organizr, sonarr, radarr, etc. dockers using my own domain. I can access all of those apps using https (https://nzbget.mydomain.com). But . . . I have lost access to the Unraid GUI. I get a 500 error on the GUI, and a "/etc/nginx/htpasswd" failed (13: Permission denied)" error in /var/log/nginx/error.log. I am trying to enter the GUI locally using http. I can SS=H into unraid, and all the docker apps are accessible. Just not the front end. Advice?
  13. Thanks. It’s what I hoped for. Now off to buy and build.
  14. A year ago, the old motherboard on which unRAID sat stopped working. I did not do anything about it immediately as I wanted to weigh the options, and then procrastination took over. So I still have 8 WD Red 8TB disks sitting idle (two of them are parity), all formatted XFS. I also have two BTRFS-formated SSD cache drives. Now I need to get the stored data back. Is it possible to mount all the devices (HDDs, SSDs and flash drive) in a totally different rig? Do I need to do something special to make the data accessible? Or is there a better way? Thanks
  15. Upgrades have always gone smoothly. But not from 6.3.3 to 6.3.5 (I missed 6.3.4). I am not able to mount unraid shares on my Mac (AFP or SMB), getting the following error: "There are no shares available or you are not allowed to access them on the server. Please contact your system administrator to resolve the problem." Soon after booting into 6.3.5 I got a "SECURITY Information" email with the following: "Tower : May 27 17:24:06 : root : unable to stat /etc/sudoers : Permission denied ; TTY=unknown ; PWD=/ ;" In my log file, the following error appear multiple times: "May 27 17:24:16 Tower root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token" And probably related to my inability to mount, I get the following: "May 27 18:06:09 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D May 27 18:06:09 Tower avahi-daemon[2790]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). May 27 18:06:09 Tower avahi-daemon[2790]: Successfully dropped root privileges. May 27 18:06:09 Tower avahi-daemon[2790]: open(/var/run/avahi-daemon//pid): Permission denied May 27 18:06:09 Tower avahi-daemon[2790]: Failed to create PID file: Permission denied May 27 18:06:09 Tower emhttp: shcmd (760): /etc/rc.d/rc.avahidnsconfd start |& logger May 27 18:06:09 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D May 27 18:06:09 Tower avahi-dnsconfd[2799]: connect(): No such file or directory May 27 18:06:09 Tower avahi-dnsconfd[2799]: Failed to connect to the daemon. This probably means that you May 27 18:06:09 Tower avahi-dnsconfd[2799]: didn't start avahi-daemon before avahi-dnsconfd." This is a bit over my head. Fixable, or should I revert to 6.3.3? Thanks