Snubbers

Thanks! As above, I've tried this and done some more testing and can't get it to boot. I lack knowledge of what the bootx64.efi and associated files are doing with UEFI, but the latest live slackware distro works fine, and I see they have a menu system on boot (similar menu files), and with all the other OS' that seem to work with UEFI, I wonder if Unraid might be so nice as to look in to it for us? I've already seen people on other forums discuss the Terramaster NAS' and the ability to use Unraid and it's definitely bringing in people who want pre-built hardware yet access to the awesome slickness and support of Unraid...

[edit] - For now I'm hiding my comments, their FAQs suggest they will invalidate your warranty if you install another OS, however initial support requests have been positive, so in the interest of giving them a fair time, I'll see what happens! ... I've moved over all my HW to the 424 Max, my server was failing (although might actually have been just the USB Stick!) and needs upgrading, I have the usual 30 day Amazon return window but it would be a shame if this wasn't addressed! Is it not worth also contacting Unraid support? I think this might just be a more simple compatibility issue they may be able to resolve as well.. I've tried 10 UEFI Bootable USB OS' and all work fine, including Slackwares latest live setup.. So I then tried to change Volume labels and other things to try to get other bootable USB OS' to look more like Unraid (Just to test the assertion they might be blocking Unraid, which I don't believe why they'd single them out) to no avail, I can't make a bootable USB stop booting unless I replace the bootx64.efi or similar.

Also just got this NAS (F6-424 Max).. Same issue, if I go in to BIOS and manually override the boot option from there it boots to UnRAID fine, or hit F12 on the AMI Bios screen and select it, it will boot.. I tried following this guide And no joy, the first boot, It sticks at the AMI Bios screen, if I CTRL+ALT+DEL it will reboot and get passed the AMI BIOS screen, but sticks on a black screen! I re-did the Debian Live bootable USB and it does boot to that, which is encouraging (still selecting the "Add fixes for old BIOSes).. I can also boot from USB Virtual CD Drives.. And of course it will boot from a Windows 11 install on an NVME drive.. I guess this must be some compatibility with the specific UNRAID boot and this hardware, I have seen people on other forums with the 1235U CPU have boot from USB issues, someone did a BIOS load from defaults which fixed it! but I'm not brave enough to have a go myself yet..

I've had this happen twice now, but effectively only the Unraid web UI becomes unresponsive, I might get the login screen, but loading the dashboard just hangs.. (all other dockers seem to be running fine and all docker web UIs are full speed). I've just had to get someone to use the power button to shut the server down, then power it back on.. this works but I assume the issue will come back.. I've checked logs etc and found they obviously reset at boot, so I've probably lost all pertinent information due to the power cycle. So I'm just waiting for it to happen again, but when it does, what would be the correct way to gather diagnostics if the web UI is unavailable? (I'm just trying to set myself up to start diagnosing the issue if it returns by getting good information to help).

I've just installed a trial version of unRAID (alongside my main unRAID server). I've got a USB stick (Sandisk 32Gb) for the main array and an NVME for cache and an SSD as a second pool. Diskspeed detects all teh controllers and disks, showing the USB drives (the main array and the boot flash) all connected to the USB controller and there are drive images (close enough for the SAN DISK usb sticks).. Clicking on NVME or SSD brings up the info and benchmark buttons on the right.. Clicking on a USB drive brings the image of the drive up on the right, but no info or buttons. Is it possible to Benchmark USB Sticks? My intent is to use this very low power USFF PC as an app server, so don't need an array, so followed advice on the forums to drop in a USB stick to get around the array issue and that works well, but I would love to benchmark the USB sticks as I may use them for backups and other purposes, but wanted to check their performance. Apologies if I'm missing something, I've searched hte thread but can't see anything to confirm/deny if USB drives can be benchmarked.

Thanks for the help! I've fired up a Win 10 VM (Fresh) and instantly getting 250-320Mbps , as the Win 10 VM is updating whilst running it, that's about right! speedtest tracker is still 55-60Mbps. Additional checks 1. I've switched speedtest tracker to use br0 (Same as the Windows 10 machine) and no change 2. I've checked the 'Interface' stats on the unRaid dashboard and that shows the VM @ 300+Mbps and the Speedtest Tracker @ ~60Mbps It does look isolated to the speedtest dockers for some reason?

I've always been having this issue (with the speedtest app and speedtest-tracker app). Effectively my ISP provides 350Mbit down / 35Mbit Upstream.. I can max out the connection in SABNZBD and other download dockers, but the two speedtest ones seem to cap at 60Mbit/s down. I've tried Bridge/Host network modes to match the other dockers that can max the connection out but nothing changes, it's still capping. I've checked the speedtest endpoint which is the one closest to me, and running speedtest from any browser on any other device in the house maxes out the connection to the same server absolutely fine.. It's almost like OOKLA's CLI is limiting things? I get good network speeds in the house (I can saturate the gigabit connection if transferring files etc.) Any ideas?

Another happy user: I just picked up the RM850i second hand and negotiated based on the fact I presumed the 'i' part would be useless on UNRAID so got a bit knocked off.. Imagine my surprise when I suddenly came across this in the app store and plugged in the USB cable internally and it just worked! The only stat I was slightly intrigued about was the overall power draw, as I have 5 HDDs, 2 NVME Drives and 3 SSDs with a GTX1660 Super this is about what I'd expect when not doing too much.

Thanks for the reply! In this day/age of security I'd say it's becoming essential if you do expose services by - Adding a layer of anonymity, anyone snooping around won't know the service you are proxying to, all they will know if they fail the access list authentication is you are running nginx. - By directly exposing the service, I am relying on the robustness of their individual authentication methods, and this ties in with the previous point of hiding the service as much as possible. My setup (in case it helps in any way!) It's setup using br0 (so own IP address) using default 8080/4443 ports My DNS record is a subdomain CNAME pointing to a Dynamic DNS address that points to my WAN IP. My proxy host in NPM is set as follows (private info removed Domain Name: subdomain.mydomain.com scheme: http Forward Hostname/IP: NginxProxyManager (I'm using the container name, but tried the IP as well with the same issue) Forward Port: 8181 Cache Assets: Off Block Common Exploits: On Websockets Support: Off Access List: "Home" (A list called home with a single user, 'admin' ) Custom Locations: None SSL: Custom (1and1 Wildcard cert for my domain) Force SSL: On HSTS Enabled: Off HTTP/2 Support: Off HSTS Subdomains: N/A Advanced: Empty It may well be an issue with the NPM itself?

This may well be the stupidest idea ever and feel free to laugh.. I have added a Proxy Host to effectively reverse proxy to the NPM's (NginxProxyManagers) own WEB UI, I wondered if it would blow up, but that part works well, I can access the proxy manager externally (using a sub-domain) and SSL. What doesn't work is when I add an 'Access List' to the Proxy Host config, I do this for my other Proxy Hosts to my other dockers, this gives a first layer of authentication independently of the target docker which makes me sleep better! When I say doesn't work, I mean, when you first access the URI externally you get the authentication dialog from the access list, but entering the correct credentials has it just pop up the same authentication dialog again, I can't get to the NPM login page. Not sure if I'm being stupid here, it feels wrong proxying to itself, but the WEBUI is on port 8081, the proxying is over 8080/4443 (the defaults).

My extended test has been stuck for 8 hours. I initially excluded all but one share, but it started checking app data as others have reported, then after 3 hours moved to the next folder now it’s stuck on the share I have all my backups on. is it’s safe to just terminate the process? I’m in the middle of an iteratively scheduled parity check which will take a couple more days before complete.

I have been over there and see it affects a few people so added to a thread or two! Thanks! The other issue which I've also just had is the DNS rebind issue that only affects EAC3, so that's two silent ways it won't work 1. EasyAudioEncoder X flag setting incorrectly 2. EAE uses URI's (*.plex.direct) that my router for one sees as a DNS rebind attempt and blocks it.. I was sat there scratching my head when the same EAC3 audio tracks wouldn't play and finally stumbled across this whilst on the plex forums.. just adding *.plex.direct as an exception on the router and all is well again! This seems something so easy for plex to fix but they just seem to sit on it.. sometimes you feel like just doing it for them!

I've just realised I have/had the EAC3 'issue'. i.e. any video file with EAC3 audio requiring audio transcode down to 2 channgels (most of my client apps) won't play the file, I get the following log entry: "ERROR - [Transcoder] [eac3_eae @ 0x7e9840] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-198c89ec-c5fa-4ceb-99dc-409b57434d00/EasyAudioEncoder/Convert to WAV (to 8ch or less)/C02939D8-5F8B-432B-9FD9-6E7F76C40456_522-0-21.wav'" I found a solution in this thread, just deleting the appdata\plex\..\Codecs folder and restart so it recreates it and everything seems fine now! Instead of deleting, I just renamed the folder to "Codecs_OLD" so I could see what the difference was, there are only two differences 1. The licence file has different contents 2. (probably the most crucial!) the "EasyAudioEncoder" file (2.5Mb, no extension) does not have the executable flag set on the old non-working version! I think this happened after the update a day or so ago, or that's when I noticed it! Obviously it's fixed for now, but just wondering if anyone has any idea on how it might have happened in case it comes back at a later date?

Terrible timing, I only just set it up yesterday after trying many many options (all vpn's suck for torrents it seems) And also getting the curl response code mismatch error Thanks Binhex, I thought it might be PIA's end!

Many thanks for replying and that really helps! I see how many dockers you have now, so I think deservedly putting the niceties on the back burner is very understandable!

I hope someone can help a general question that has arisen initially with this docker app but might help me with others! I was just about to install this one but the docker template seems not to match the github/dockerhub usage instructions Specifically the template only has a single volume map (container: \data which defaults to host: \mnt\user\appdata\data) with the "show more settings' also having the standard container: /config to host: /mnt/user/binhex-sabnzbd mapping Looking on github/dockerhub, the usage instructions indicate 3 mappings: 1. -v <path for media files>:/media \ 2. -v <path for config files>:/config \ 3. -v /etc/localtime:/etc/localtime:ro \ I understand 2 and 3, one is fixed, the other hidden in 'show more settings'.. However, 1 is a bit odd, /media sounds sensible, but why is the template asking for a /data and defaulting to /appdata/data? [edit] so a bit more digging and I've found the "docker-templates" repo on github for these so I can see the template from source does not match the usage instructions (not sure if it should/shouldn't, it may be my ignorance).. One thing that springs to mind, when I've edited a few installs, I've found the 'my-[docker]' tempalte files in /flash and there is a nice <config> tag that allows you to have a <description> field per item, something I've done to a couple of dockers to help me if ever editing/reinstalling. I know it's very cheeky to ask, but I'd absolutely love it if authors detailed things using that method in their docker templates to help us OCD people who don't want to mess things up

First Post! (Hopefully) I am new to using UnRAID as an application server, so forgive my ignorance (and searching is not yielding anything) so far so good, the binhex-plexpass docker has been excellent. I unforunately tried the official docker first, but it hammered the cache drives constantly (2.2MB/s+), so switched to the binhex-plexpass (I have a plex pass ofc) and using Space Invader Ones tutorial moved the "Plex Media Server" from the old docker to the binhex one. As I have shares for each media type (Music, Movies, TV, Photos), I also edited/added paths in the docker template to map each of the shares to its own container path (for good house keeping I didn't want plex to have R/W access to everything in \mnt\user). This has left me with a little niggling doubt above the effects of these, so have three questions (if I may?) 1. Migrating the Plex Media Server appdata folder and its effect on the 'plex pass' version of the docker: So following Space Invader Ones guide, I deleted the "Plex Media Server" subfolder of appdata\binhex-plexpass and replaced this with the one from the official docker, so I am now wondering if this undoes anything 'plex pass' specific? 2: Adding extra paths to the docker template? Is this a good or bad idea? I stated why above (to limit plex's access to \mnt\user to only those folders it needs) but this does mean I've deviated from the standard docker template and as I've only got 2 dockers installed so far (binhex-krusader and binhex-plexpass) I would like to follow best practices and not make things up if it could bite me later! 3. No port assignment in the docker manager I noted for the offficial plex docker, and also for krusader there are port mappings showing in the docker manager and when adding a new docker you can use the 'show docker allocations' to make sure you don't end up with two dockers figting over one port. However with binhex-plexpass there are no port mappings (just an empty space in this column in the docker manager, and when using the 'show docker allocations' it just shows '???'. I know Plex requires port 32400 for external access (I have always had this port forwarded to the server for plex for as long as I've been using plex (mainly on windows)) but should it not show in the docker manager to help ensure it isn't attempted to be used by any other container, or is that the different between bridge and host mode? Thanks for any advice! To the best of my knowledge binhex-plexpass seems to be working perfectly and loving the ease of setup so far!