Darren Cook

Is this ever going to be updated for ZFS pools? as seems to not find ZFS pools these days?

Same. on latest stable build.

Did you change dns to cloudflare or opendns? Seems to have sorted my dns issue.

Has something changed in the last update? Was getting random 'unable to resolve server.newshostserver.domain' and downloads would randomly stop. just changed DNS to cloudflare to see if this resolves it, but now i just keep getting in a loop of trying to connect to VPN then times out then tries again and again.....? Even tried replacing PIA server with another, same issue with multiple? Debug log attached.... also checked firewall for the PIA ip, no matches blocked. FIxed: Downloaded new openvpn config files reference a IP (91.90.121.230) rather than the older config that references uk-manchester.privacy.network (domain). Restored old PIA config files from 4 months back. works fine with DNS changed to cloudflare, new config files do not. very weird? not sure as to why? as i downloaded them from PIA site. ping uk-manchester.privacy.network Pinging uk-manchester.privacy.network [45.133.172.215] with 32 bytes of data: Reply from 45.133.172.215: bytes=32 time=40ms TTL=51 Reply from 45.133.172.215: bytes=32 time=30ms TTL=51 Reply from 45.133.172.215: bytes=32 time=31ms TTL=51 Reply from 45.133.172.215: bytes=32 time=35ms TTL=51 Ping statistics for 45.133.172.215: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 40ms, Average = 34ms ping 91.90.121.230 Pinging 91.90.121.230 with 32 bytes of data: Reply from 81.92.206.162: Destination host unreachable. Reply from 81.92.206.162: Destination host unreachable. Reply from 81.92.206.162: Destination host unreachable. Reply from 81.92.206.162: Destination host unreachable. Ping statistics for 91.90.121.230: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Is scrutiny dead? running ghcr.io/analogj/scrutiny:master-omnibus However the docker won't start... "Execution error - Server error" nothing seemingly being put into logs..?? Forced update, same issue.

I have setup values for the docker (--runtime=nvidia and GPU ID) as per instructions to add nvidia encoding. however the software still uses CPU to encode. I added my pc as a node and added directory's as per instructions, also the pc is using CPU to encode rather than nvidia GPU.. Anyone care to explain if something different needs to be done in the flows for this to work??

Nope, as last time i reported a bug i was ignored, until it became apparent there was a major issue with Active Directory integration with 6.9.3 Feel free to submit one and reference this thread or my own thread.

So its not that then. thanks for clarifying. i remember the last RC (6.9.0?) had issues with AD that where not picked up until final release when i had flagged it. i have a feeling something again was missed?

I actually noticed on boot that unraid is setting all my shares to 0777 despite them listed in unraid as private shares 0755? Active Directory reports users have correct permissions, but nada when it comes to accessing (denied error). For clarity reasons: My two AD servers are on Unraid. been meaning to move one onto proxmox but haven't had time yet. im wondering if this is the same for yourselves? if so it might be the fact unraid will not be able to join the domain during startup? i know this was easily resolved in 6.9.3 by running "net join -U Administrator" in ssh...but this doesn't seem to resolve it in 6.10.2

Since updating to 6.10.1 i noticed that my SAMBA shares from Unraid, Active Directory permissions are getting denied (No Permission to view), despite effective access showing correct permissions for this AD group (Unraid is joined to the domain) So, i created a few new shares and tested permissions, I'm not sure if my config files are messed up in Unraid or something has gone pear shaped during the upgrade? Example: I created a new share in Unraid, set it to a private share and exportable, check the permissions, I'm seeing "everyone" getting full read/write access to brand new shares that should be private? Wanting to see if anyone else is seeing this? or just myself?

Am i going mad. or has this broken? setup and connecting. but every request results in the same error. 2022-04-29T14:47:57Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [ip for NGIX:443 goes here but removed]: connect: no route to host" cfRay=[blanked]-LHR originService=[ip for NGIX:443 goes here but removed] 2022-04-29T14:47:57Z ERR Failed to handle QUIC stream error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [ip for NGIX:443 goes here but removed] : connect: no route to host" connIndex=1 Followed two guides to compare settings. tried setting disabletlsverify to true, just get 502 errors. even tried setting up each host name in the yaml. same deal. *hits head off wall*

Is it just me or does the 'skip speed gap' tick box not actually work? Tried several times and it always stops for speed gaps..? also clicking the actual text on this option seems to toggle the 'skip ssds' box above?

Can someone advise how you change the hostname of this docker? i cannot for the love of me figure out how to? might be useful to put it as a configuration option in unraid when installing? Also, removing the allowed domains check - Failed CORS: null vs 192.168.1.x, 192.168.1.x, 192.168.1.x, pi.hole, localhost, 192.168.1.x might be useful as some of us block refferers in chrome.

Pi-Hole DoT DoH. How the heck do you change the hostname of pi-hole? i have set it in dhcp server. but i cannot for the love of me find a setting in pi-hole to change it. nor config files? Can someone let me know?