Jump to content

jakeortman

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

 Content Type 

Posts posted by jakeortman

    Samsung 870 EVO Drives for Cache -- Should I Worry?

    in General Support

    Posted

    I currently have a couple 500GB WD Red SA500 NAS SATA SSDs (2.5") in a pair for my cache (btrfs, RAID1). I'm running a bit short on capacity with some docker/media/things I'm doing. I have the option to get a pair of new Samsung 870 EVO 1TB or 2TB drives. I've heard and seen some stories about EVOs of the past having issues with firmware and premature failures. Has that gotten any better? I have some credit at Dell and this is their limited inventory of 2.5" drives, so I'll likely be shopping from there (their selection isn't great, but credit is credit).

     

    I'd go with M2, but I want to keep my RAID1 protection and I only have one M2 slot on the motherboard I'm using.

    Figro's Docker Repo Support Thread

    in Docker Containers

    Posted

    On 6/16/2023 at 7:17 AM, Slippin' Jimmy said:

    Just an FYI for those having issues, I changed over to CloudflaredTunnel by Cornflake under apps about 2 weeks ago which is using the official cloudflared docker repository, and have had no issues with it.

    I've been having issues with the other Cloudflared docker containers and installed the CloudflaredTunnel by Cornflake and got my tunnel up and running quickly and verified on the cloudflare end fo things. However, I can't figure out where to setup ingress rules. In my previous setup, there was a config.yaml file in appdata, but now I'm not seeing that. How do you setup ingress rules with Cornflake's container?

    [Support] aeleos - cloudflared tunnels

    in Docker Containers

    Posted

    13 hours ago, ConnerVT said:

    First, you may wish to create a new tunnel.  You posted your UUID tunnel ID above.

    Who's an idiot?

    👈 This guy right here....😒

     

    Guess what I'm doing tonight now? LOL

     

    Yeah, I'm probably going to split things up into multiple line-items. My NPM has been weird and funky for a while now, I finally had to hard-code it to a version that worked properly a few months back as an update killed it. I'm using the same NPM as you are. I'll likely just blitz both and re-setup everything from scratch.

    [Support] aeleos - cloudflared tunnels

    in Docker Containers

    Posted · Edited by jakeortman

    On 8/28/2023 at 6:05 AM, ConnerVT said:

    After changing your ports did you update your config.yml file as well?

    Yup, I did, sorry I forgot to mention that.

      

    tunnel: bd6221asdfasfsadf
credentials-file: /home/nonroot/.cloudflared/blahblahblahblah.json

ingress:
  - service: https://192.168.1.20:443
    originRequest:
      originServerName: my.subdomain.com
      noTLSVerify: true

     

    According to the dashboard at https://one.dash.cloudflare.com/, the tunnel is healthy, so I'm starting to think this is a NGINX Proxy Manager issue at this point.

    [Support] aeleos - cloudflared tunnels

    in Docker Containers

    Posted

    This is probably something really dumb, but I can't seem to get it figured out.

     

    First off, recently, I changed my NPM ports so they're using standard HTTP (80) and HTTPS (443) ports after changing the default admin ports in Unraid. I'm doing this so I can serve content locally on my network with the same domain name as I do remotely (say, photos.domain.net). That way I can access the server directly when I'm outside the network, run it through cloudflare outside the network, where it uses Google Workspace as an access method.

     

    This all worked until recently, but would randomly crash, and I wanted my wife to still have a way to easily access the photos and recipe site I had setup. So that's why I changed the port. But cloudflared is still being weird. I'm getting a lot of these type of messages in the logs and the sites aren't accessible outside the network. 

      

    2023-08-26T04:18:25Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: cannot validate certificate for 192.168.1.20 because it doesn't contain any IP SANs" connIndex=3 dest=https://recipes.mydomain.net/favicon.ico event=0 ip=198.41.192.77 type=http
2023-08-26T04:18:27Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: cannot validate certificate for 192.168.1.20 because it doesn't contain any IP SANs" cfRay=7fc94557be3915ca-SJC event=1 originService=https://192.168.1.20
2023-08-26T04:18:27Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: x509: cannot validate certificate for 192.168.1.20 because it doesn't contain any IP SANs" connIndex=3 dest=https://recipes.mydomain.net/service-worker.js event=0 ip=198.41.192.77 type=http

     

    Red X on Parity Drive

    in General Support

    Posted

    59 minutes ago, JorgeB said:

    Disk dropped offline so there's no SMART, but this is usually a power/connection problem, check/replace cables and post new diags.

     

    You should enable system notifications so you are notified as soon as there's a problem.

    Will shut it down and check wiring later tonight. I think that drive is directly connected to the SATA port on my server while the other parity is connected to the SuperMicro backplane, so that makes sense it might have come loose.

     

    And email notifications have been setup now. Thanks for the reminder as I'd been meaning to do that 🙂

    • Like 1

    Red X on Parity Drive

    in General Support

    Posted

    Happy Turkey Day everyone! I logged into my unraid UI today after not logging in for a few weeks and was looking to run a backup before potentially upgrading to 6.11.5 (I'm on 6.11.1). I saw a Red X on one of my parity drives. I run a dual-parity setup, so not too stressed out (yet) and the drives are under warranty, but I'd be curious if anybody can see anything in the attached diagnostics that would point to why the drive is marked with an X (the SMART log for the drive, also attached, didn't have much since it couldn't connect to the drive, it says). 

    storage-diagnostics-20221124-1024.zip storage-smart-20221124-1016.zip

    [Plug-In] Community Applications

    in Plugin Support

    Posted · Edited by jakeortman

    While I totally get the reasoning to force 6.9 as the minimum version, is there a way to force install back to a version that works on 6.8.3? I installed some newer version that doesn't load the apps page properly, can't install the newest version because I can't do 6.9 until they fix the custom IP stuff that was causing kernel panics on my system (in theory, 6.10 has that in place). 

    all docker containers lists version “not available” under update

    in General Support

    Posted

    On 5/14/2021 at 4:30 AM, HyperV said:

    I had exactly the same issue and could not find any solutions on the forum or the internet. So I did some digging myself and found the cause of the issue. The docker update check script gets the remote digest of the latest tag from the docker repository via a header called 'Docker-Content-Digest'. The script checks for this header with a case-sensitive regex pattern. Manually querying the docker hub registry gives me a header called 'docker-content-digest' (mind the casing). The docker hub registry must have recently changed the casing of this header, because it broke for me in the last 24 hours. I'm running on Unraid 6.8.3 still, so I'm not 100% sure if this issue also exists in 6.9.x.

    If you feel up to it, you could quite easily fix this yourself until there is a real fix. I'll describe the steps below:

    Open file: /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

    Go to line 457.

    There you should look for the text: 

    
@Docker-Content-Digest:\s*(.*)@

    and replace it with: 

    
@Docker-Content-Digest:\s*(.*)@i


    Save the file.

    This will make the header check case-insensitive and should make it work again.

    Registered a forum account here just to say Thank you! I was bouncing between all sorts of threads thinking it was a Pi-hole or DNS issue, but this fixed it immediately. 

×
×
  • Create New...