Jump to content

glassbase

Members
 View Profile  See their activity

  • Posts

    9

  • Joined

  • Last visited

 Content Type 

Posts posted by glassbase

    6.9.1 to 6.11.5: I had blank root password

    in General Support

    Posted

    I took the plunge and updated from 6.9.1 to 6.11.5. It took awhile for WebUI to finally load, but it is up. All else appears normal: dockers are up, SMBs are up, SSH is working, etc. 

     

    I had a blank root password (I know, I know, I live my life dangerously). 

     

    The new login screen does not let me login with root//*blank*. Says password cannot be blank. 

     

    Can I just add a password to root user via command-line? OR What do I need to do?

    Not getting Temp's on disks even though they are in smart data.

    in General Support

    Posted · Edited by glassbase

    I am also not getting temp displays in GUI.

     

    Shows up under stats under attr 194, but never displays in Main tab temp column. 

     

    I have hpsahba installed, added 194 to notifications, set my controller type to SAT. 

     

    I know they used to show (maybe back in 6.8.x) without requiring hpsahba to be installed. 

     

    HP DL380p G8 12xLFF with P420i Raid (in HBA mode)

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    13 hours ago, dlandon said:

    Are you mounting those disks manually somewhere in a script?  If so, don't.

     

    There is an issue with those mounts.  I would do the following:

    • Be sure auto mount is turned off for both disks.
    • Don't auto start the Dockers.
    • Remove the 'dev2' Historical device.
    • Reboot the server.
    • Rename the mount points like you want.
    • Mount the disks.
    • Start the Dockers.

    Back up and running with these steps.

     

    Although I did realize you cannot click the pencil to edit name, you actually click the name. (I swear in older version of UD, you clicked the pencil, but been long time since I had to edit mount names.)

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    11 hours ago, dlandon said:

    Are you mounting those disks manually somewhere in a script?  If so, don't.

     

    There is an issue with those mounts.  I would do the following:

    • Be sure auto mount is turned off for both disks.
    • Don't auto start the Dockers.
    • Remove the 'dev2' Historical device.
    • Reboot the server.
    • Rename the mount points like you want.
    • Mount the disks.
    • Start the Dockers.

    100% non manually mounting, only every mounted using UD. I will try those steps and report back. Thx

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by glassbase

    Hi,

     

    (Not sure if what I am experiencing is related to this issue.)

     

    For me, nothing has changed other than auto-updating Unraid plugins. Unraid is 6.9.1. UD plugin 2022.05.19. UD+ plugin 2022.05.17. Uptime is 19+ days (I had a much longer runtime, but sorted my equipment a couple weeks ago :) ). No drives removed or inserted recently.

     

    My unassigned devices appear to be mounted and readable/writeable in dockers/SMB/etc ... but the GUI tells a different story. 

     

    SPCCxxxxxx drive appears in Historical Devices and appears to be the exact same name? I noticed in comments about spaces/underscores, but mine are the same?

    WDCxxxxx drive does NOT appear in Historical Devices. 

    trailer is a device I use in-frequently, little HDD for my media server in camping trailer. Not worried about that one today. Is not plugged in currently. Has not been plugged in for year-ish

     

    Just want to understand how to fix this. 

     

    1. Stop dockers using these devices

    2. Remove from Historical

    3. I cannot click the pencil icon to edit the name? Will I be able to after it is removed from Historical?

    4. Reconfigure 

    5. What about the WDCxxxxx drive that is not under Historical?

     

    Capture.thumb.PNG.2fa6767b00b6a1271c6d5d36d2c22453.PNG

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by glassbase

    HI all,

     

    Hopefully my strange fix helps people here with this "Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA."  error.... because HTTPVAL was not working for me (and my ISP does not block port 80) and I figured out why...

     

    I use a docker-compose file with the line = "image: linuxserver/letsencrypt:latest" and it was not updating my image upon running "docker-compose up -d" for whatever reason. I came to this conclusion after closing port 80 in my router and was not receiving the timeout error during validation. 

     

    Then I run "docker pull linuxserver/letsencrypt:latest" and watched it actually pull the latest image, start letsencrypt and bam, I was able to complete validation. 

     

    IDK how to force an update to an image on unRAID or others or if my fix will work for anyone else, because I use Docker for Mac (do not have an unRIAD box YET :P ) 

     

    edit - spelling

×
×
  • Create New...