Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

jhartley

Members
  • Joined

  • Last visited

Everything posted by jhartley

  1. I am using NPM. For some reason when I point my config file at NPM https end point and then add my host to NPM, it wont find my host. When I point my config to the NPM http end point it will find my host. Solved: For anyone else experiencing the same issue, to fix this do the following: 1. set your NPM host to http 2. Get the origin server key and cert being used by your tunnel and create separate files for each (name.key, name.pem) 3. Go the the SSL tab in NPM and create a new custom certificate using the .key and .pem files created 4. do to SSL tab for the host and add that certificate
  2. So you add an individual entry for each service. Can you not just do a wild card that catches all subdomains?
  3. @aeleos any advice here would be appreciated.
  4. What endpoint do you point to in your cloudflared/config.yml? I ask because I made these changes in NPM and used http instead of https for each host. However, if I point to NPM endpoint using the following: ingress: - service: https://192.168.1.20:18443 originRequest: originServerName: MYDOMAIN.com I get the following error in the Cloudflared Tunnel log: 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: remote error: tls: unrecognized name" connIndex=3 dest=https://app.domain.com/favicon.ico event=0 ip=198.41.192.77 type=http But if I point to an http enpoint in my cloudflared/config.yml like so: ingress: - service: http://192.168.1.20:1880 originRequest: originServerName: MYDOMAIN.com Everything works. But this doesn't seem to be secure to me. Additional Note: Pretty sure this is a TLS issue. When I add noTLSVerify: true to my config file it will work when connected to my https port. I am not understanding why this is the case. I created a client certificate in CloudFlare and added it as a customer cert in NPM. What am I doing wrong? This has to be something stupid simple. @aeleos
  5. So the value is only applied when you click the balance button? I was thinking it had something to do with the total capacity you allow your cache group to fill up to.
  6. What is this setting for "Block group usage (%):"? I have check the Unraid documentation and can't find any reference to it.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.