Jump to content

riffles21

Members
  • Posts

    4
  • Joined

Posts posted by riffles21

  1. 1 hour ago, mrangryoven said:

    My letsencrypt docker is not working. Re-installed multiple times with no success, settings are as they were pre unRAID 6.4.0 update.

     

    
    Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
    Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
    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

    This is what im getting at the moment. Im using duckdns.org as my domain and subdomain as my duck dns name.

    Port 81 for the docker and was using 443 but i have entered 443 manually in the box as it was staying grey on the docker page.

     

    Here is my run command

    031eec3419.png

     

    I have changed the port in the unraid Settings > Identification > SSL for HTTPS to 442 and applied, this is also not helping!

     

    Any ideas? I see i am not alone with my issues.

     

    PS, this is a repost. i deleted my previous one and added this run command.

     

    I have exactly the same issue. It was running fine last week and now all of a sudden it stopped working.

     

    Maybe it has something to do with this: https://community.letsencrypt.org/t/2018-01-09-issue-with-tls-sni-01-and-shared-hosting-infrastructure/49996

     

    Edit: solved the problem, thanks @CHBMB. Set HTTPVAL to 'true' and forwarded external port 80 to internal 81.

     

    image.thumb.png.9d4cf5c49e54d089280165782a8fae5e.png

    • Upvote 1
  2. It's working for others, without that issue, so I still lean toward the controller not handling it properly.  USB 3.0 ports and controllers have clearly been more problematic, so you may want to try a USB 2.0 port, or a USB 2.0 flash drive.

     

    I tried the USB 2.0 port and, as it seems, its working for now. After wakeup the USB is still on /dev/sda and the WebGUI is working without doing anything. Thanks for the hint.

  3. Hey guys, I desperately need your help with the S3 Sleep plugin.

     

    My Setup looks like this:

    • /dev/sda -> unraid boot stick [sandisk Ultra Fit 16GB]
    • /dev/sdb - sde -> Parity + 3 Data Disks
    • /dev/sdf -> Cache [120 GB SSD]

     

    After waking up the server from sleep, USB changes from /dev/sda to /dev/sdg and the WebGUI is broken until I manually mount the stick with putty.

    This problem repeats after another sleep & wakeup, than the new mountpoint ist /dev/sdh, so again I need to manually mount this from putty to get the WebGUI working again. This goes on and on....

     

    How could I fix this problem ?

     

    My Motherboard is MSI B150M ECO , if that helps.

     

    The first question always has to be - are you sure it works with your system?  S3 sleep is never guaranteed, requires compatible motherboard, software, and all devices, and it sounds like at least one of your USB controllers does not support it correctly.  You can try fiddling with the USB config in the BIOS, and you can try plugging your flash drive into a different controller, e.g front vs back, or an internal plug, etc.  Did it ever work for you before?

     

    Here's the List from Tools / System Devices:

     

    PCI Devices

     

    00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)

    00:02.0 VGA compatible controller: Intel Corporation Device 1902 (rev 06)

    00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model

    00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)

    00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)

    00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 (rev 31)

    00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #1 (rev 31)

    00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)

    00:17.0 SATA controller: Intel Corporation Device a102 (rev 31)

    00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)

    00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)

    00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)

    00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)

     

    IOMMU Groups

     

    /sys/kernel/iommu_groups/0/devices/0000:00:00.0

    /sys/kernel/iommu_groups/1/devices/0000:00:02.0

    /sys/kernel/iommu_groups/2/devices/0000:00:08.0

    /sys/kernel/iommu_groups/3/devices/0000:00:14.0

    /sys/kernel/iommu_groups/3/devices/0000:00:14.2

    /sys/kernel/iommu_groups/4/devices/0000:00:15.0

    /sys/kernel/iommu_groups/4/devices/0000:00:15.1

    /sys/kernel/iommu_groups/5/devices/0000:00:16.0

    /sys/kernel/iommu_groups/6/devices/0000:00:17.0

    /sys/kernel/iommu_groups/7/devices/0000:00:1f.0

    /sys/kernel/iommu_groups/7/devices/0000:00:1f.2

    /sys/kernel/iommu_groups/7/devices/0000:00:1f.4

    /sys/kernel/iommu_groups/7/devices/0000:00:1f.6

     

    USB Devices

     

    Bus 002 Device 002: ID 0781:5583 SanDisk Corp.

    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

     

    SCSI Devices

     

    [0:0:0:0]    disk    SanDisk  Ultra Fit        1.00  /dev/sda <- this disappears after wakeup, and comes up new (see below)

    [1:0:0:0]    disk    ATA      ADATA SP550      0C    /dev/sdb

    [2:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sdc

    [3:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sdd

    [4:0:0:0]    disk    ATA      ST3000DM001-9YN1 CC4C  /dev/sde

    [5:0:0:0]    disk    ATA      ST3000DM001-1CH1 CC44  /dev/sdf

    [6:0:0:0]    disk    SanDisk  Ultra Fit        1.00  /dev/sdg <- this disappears again after second wakeup and comes up new (see below)

    [7:0:0:0]    disk    SanDisk  Ultra Fit        1.00  /dev/sdh

     

    That keeps going after every wakeup...

     

     

    I found this line in the syslog :

    kernel: ACPI: (supports S0 S3 S5)

     

     

    I'm new to unRAID, switched from openmediavault. There worked everything fine, but the system was installed on a ssd not a usb thumb drive.

     

    Maybe a little script, like searching for the usb drive after wakeup and mount it again, would help ?

  4. Hey guys, I desperately need your help with the S3 Sleep plugin.

     

    My Setup looks like this:

    • /dev/sda -> unraid boot stick [sandisk Ultra Fit 16GB]
    • /dev/sdb - sde -> Parity + 3 Data Disks
    • /dev/sdf -> Cache [120 GB SSD]

     

    After waking up the server from sleep, USB changes from /dev/sda to /dev/sdg and the WebGUI is broken until I manually mount the stick with putty.

    This problem repeats after another sleep & wakeup, than the new mountpoint ist /dev/sdh, so again I need to manually mount this from putty to get the WebGUI working again. This goes on and on....

     

    How could I fix this problem ?

     

    My Motherboard is MSI B150M ECO , if that helps.

×
×
  • Create New...