Jump to content

StandardToast

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by StandardToast

  1. Hey all,

     

    So I followed both of SpaceInvaderOnes videos and I have it set up as the following

     

    ddclient configured with CloudFlare as my DynamicDNS - Working I can ping the subdomain and it resolves to my IP

    CloudFlare as Reverse Proxy DNS - Possible error here?

    Owned domain from namecheap -> setup with cloudflare DNS

    My domain does show up in cloudflare as transitioned and active. I have an A type dns record for 'cloud' that has my correct WAN  IP

     

    I have edited the nextcloud config files - Question is "'trusted_proxies' => ['letsencrypt']", " required in the nextcloud configuration file?

    I have edited the lets encrypt subdomain config files and its no longer a sample file

    My NextCloud docker container is on the custom proxynet ethernet bridge thing

    My let encrypt is using port forwarded 180 (changed from port 80 on the forward rule) and 443 as the video show (had issues when using 1443 )

    I have edited the nextcloud config to use cloud.* instead of nextcloud.* to match my subdomain name

    My unraid server does have a  static IP on the internal network

     

    Logs

    Nextcloud shows no log errors

    ddclient has - "WARNING: found neither iupv4 nor ipv6 address"

    LetsEncrypt - Server ready status

     

     

    I am getting a 502 bad gateway error when I VPN out and go to https://cloud.mydomain.com

     

    I had an issue where I couldnt see with canyouseeme.org the 443 or 1443 port forward rules. Checked with my ISP and confirmed they do not block them

     

    Videos I followed -

    https://www.youtube.com/watch?v=I0lhZc25Sro

    https://www.youtube.com/watch?v=fUPmVZ9CgtM

    https://www.youtube.com/watch?v=I0lhZc25Sro

     

     

    What would cause this 502 bad gateway? What steps can I check? Is it useful to post the config files? Is it safe to post the config files? Thanks everyone

  2. Hey everyone. I recently set up unraid about a week ago and everything was going fine. I upgraded my drives recently starting with my parity of 2tb to 8tb. I followed the guide on the Wiki and no problem there system was up and functional.

     

    After that I needed to upgrade my data drive. In this case I removed a 2tb drive again and upgraded to a 8tb drive. At some point during that the build failed and it ran a read check on that brand new 8tb drive (Shucked WD Easystore White label). Read check passed however the drive still shows disabled and I cannot enable it. I get a CRC Error and I have replaced the sata cable and it also happens on my SSD cache. This SSD is only 1 year old and shouldn't have this error either and if it matters I added the cahce and the 2nd 8tb drive (the data one) at the same time.

     

    Do I have a bad sata controller on my MB? Can I re enable this drive? Is there a Sata HBA someone could recommend? Thanks

     

    System Info

    M/B: Supermicro X8DAH Version 1234567890 - s/n: VM21S56452

    BIOS: American Megatrends Inc. Version 2.1. Dated: 12/30/2011

    CPU: Intel® Xeon® CPU X5687 @ 3.60GHz

    HVM: Enabled

    IOMMU: Enabled

    Cache: 256 KiB, 1024 KiB, 12288 KiB, 256 KiB, 1024 KiB, 12288 KiB

    Memory: 32 GiB Other Multi-bit ECC (max. installable capacity 192 GiB)

     

    WD Drive Error

    199UDMA CRC error count0x000a200200000Old ageAlwaysNever6

    SSD Cache Error

    199SATA CRC error count0x0032100100000Old ageAlwaysNever1

    tower-diagnostics-20200426-1539.zip

×
×
  • Create New...