Ryonez

Squid is meaning using pi-hole as the DNS server unRaid uses for itself. Though looking at the replies for it I don't get why this is pointed out. I don't use it for my server, and that's because I host it on that server. I might personally try it if it was hosted off the server, but I could see there being issues where it might block something unRaid needs by accident. It's unlikely you'll need to filter the traffic for unRaid though. Pi-hole is fine to use as the DNS server for wireguard, though there's some tweaks you need to do if you're hosting pi-hole on the same unRaid server as wireguard.

Is it only possible to have one active tunnel at a time? I've been trying to set up a second one to create a game network. I have another one, an admin network that has docker access that's working fine. But this second one I can get the client and server to handshake. Any idea what the issue might be?

Good to know, thank you for the clarification!

I'm a tad confused, why do we need to join their poll if we can vote here? Though I'd like to point out, if this is being considered a serious poll being taken on board by the unraid team, I'd much rather see it handled completely on your site, here on the polls. I've left facebook long ago. Not an issue for most, I agree, but for myself I don't wish to use a social service that has such massive disregard for it's members.

Just set your "documentMaxLength" to 2000000 in the config and remove the CMD_documentMaxLength from the template. In fact I have almost everything done in just the config file. Going to let the others know, the docker image is still broken, though I guess the arm build is okay. Just to clarify, Version 1.4.0-ls11 is the last build I can get working.

Alright, thank you. I might poke around this subject more myself later.

I don't know. I'm a little reliant on others knowledge here as I'm by no means an expert and what I do know is rather patchworked.

Yup, I linked it with a edit shortly after. Sorry, I didn't think when I posted it to add it.

The lack of `Docker Isolation through Linux namespaces / subuids`. I've been given the example over here that if someone breaks out of a container when they are root, they are root on the host as well.

Any chance there are some updates? The lack of docker isolation is actually starting to worry me as I do have a few external services I host on unRaid.

Okay, did some testing and I believe the current docker image is broken. Version 1.5.0-ls12: Image broken. Seems to be missing the correct public/build files to run. Version 1.5.0-ls11: Image broken. Throws error in console: `s6-applyuidgid: fatal: unable to exec ./node_modules/sequelize-cli/bin/sequelize: No such file or directory` Version 1.4.0-ls11: Works. Has insecure pdf support, but is functional. My instance isn't public, so I'll fall back for now until it's been looked at and fixed.

I can't really test that. Beside using oauth, I'd have to change the config to edit the domain and such. When attempted as is, firefox throws security errors and won't load part of the page.

My current codimd instance is broken. Looking in the container, no such file is there:

Running my small server would be so much more hassle if it wasn't for you guys. Thank you for creating something that just works and lets me focus on other things.

Jesus, this really makes it off-putting for people to ask for help. Is not noticing I missed something, asking if it was the issue taking responsibility? *I noticed a mistake I made, and asked it that was causing silent failures.* Also, I outlined how and why I missed it, and offered an improved that would make it harder to miss. Wasn't blaming anyone else on that in the slightest. You need to keep in mind you guys are good at this shit. I'm not dumb by any means, but I don't know everything and something like this can be overwhelming, especially in instances when you're trying to piece together several dockers. I'm happy to stop the conversation here, I just want to get that off my chest because the way things started to turn. "we do our best to lower the bar" defiantly felt like it would naturally follow on to "but if you're to dumb you're outta luck". Logically I know that's not what you mean, so don't worry, but emotionally it does feel like an attack kinda. But, we think we have the issue, I'll look into it some other time, and if there's an issue I'll pop back and provide stuff like the run commands and see if we can hammer it out. As it stands, I feel like the mistake I made is what's feked it up. Thank you very much for you're help guys. Even if I got a little upset, I do appreciate the help alot. I hope you have a good day!

As mention in the section you quoted: Gone, as in, I had like 5-6 places I was getting instructions from. Something that's normally used as a description field ended up being glossed over, especially as it didn't look like instructions among all the instructions being looked at. I had already identified that I missed it, and why and how it could've been prevented by adding it to the dockerhub instructions. Telling me it's in the template again doesn't help if I'm to be frank.

I followed the dockerhub instructions for the most part, which don't mention this limitation. And I must have glazed over the instructions in the template because it looked like a two line description, not instructions like the on in elasticsearch's template.After juggling three docker image setups, it was just gone. Mmm, please defiantly add that to the dockerhub instructions, maybe under `Application Setup`? I wish this didn't fail silently as well, bu I feel that's more an issue with how diskover is written over the image itself. I'll keep that in mind and add it to future help requests. At the time it was asked of me, I had given up and removed the images completely. Maybe after I sort out network isolation with my docker containers I'll give this all another go.

The template information that's filled when using CA. Yes, the instructions for this are in two places. I don't even know what the full command is, and I've since removed the dockers images after trying three full times to get it working from start to finish. Again, nothing is throwing an error. They all seem to function, but just not do anything. Just noticed thought, the template I was looking at most was elasticsearch's. discover had this: ``` Elasticsearch is needed for this container. Use 5.6.x. ``` I just used what was in the template, which seems to point to 6.6.2. Did this really silently fail because of this?

I'm aware of that, I followed the instructions on dockerhub. Redis and Elasticsearch were set up, but there's no errors other than redis saying it's not going to have high performance on unraid. It gets here: ``` Once running the URL will be http://host-ip/ initial application spinup will take some time so please reload if you get an empty response. ``` There's a response that I mentioned above that, but otherwise nothing happens. no info, nothing saying it's processing, nada. If it's failing because of this: ``` If you simply want the application to work you can mount these to folders with 0777 permissions, otherwise you will need to create these users host level and set the folder ownership properly. ``` Then the documentation needs the instructions for unraid added. It's not in the template info. Also again, it should error on perm issues, which it isn't.

Fair enough. It just doesn't seem to work on my end, and as mentioned there's no apparent reason why. There's no errors, and it doesn't seem to actually do anything. Without it being in the docs I'm also not sure what to expect, so I can't do anything with this. For now I'm going to use WizTree64. It's a tad easier, maybe I'll hit this up again sometime to see if I can get it to do something.

And still getting the same issue. Yup noticed this very quickly, and it's something not mention in the documentation. I'm done with this. It shouldn't be hard, everything is there. Yet it just spits out `No diskover indices found in Elasticsearch. Please run a crawl and come back.` There's no indications of anything actually doing anything, no guides as to what to expect at the start. It just doesn't work, for no obvious reason. In my opinion right now, this needs to either be updated with better docs on dealing with issues and how to find out what's actually going wrong, or looked at for removal. And I'm not saying that lightly. I'm a firm support of linuxserver's work for the community, but this thing is just a mess.

Came back to it after leaving it for a night, still no clue what's happening.

How do you know if things are working? Atm I'm seeing this: My assumption is it needs to do an initial scan, but there's no proper indicators as to what's happening. Should I be worried that almost nothing shows on the dashboard?

Are those of us on the stable release of unRaid missing any important updates with Dynamix System Statistics? You have it restrict to a release candidates atm.

Thankfully that was a horribly false alert. It seems I made the mistake of copying another folder that had those files missing instead. I was from an instance that broke that I could never narrow down exactly what cause it. Checking the backups, I can confirm the correct folder was backed up safely, sorry for the trouble. Now I can relax with it back up >.<