Necro

Well, that answered it. Thanks!

I'm having (what I think) is an odd issue. The second and third container in a 3 container stack are getting "-1" appended to their name upon creation. There's no other containers with those names, so I can't figure out how to fix it. I've done a Compose Down, removed them manually, etc. and nothing - always created with "-1" at the end. Any thoughts/ideas how to fix would be great. It's purely cosmetic, but it's annoying. ...I actually just realized it's adding the stack name to the beggining as well. So [stackname]-[container]-1. Not certain if that's a setting or what. The first container, which is the same name as the stack, does NOT do that.

Same as above - getting the "invalid and cannot be displayed" error still.

I guess the key sticking point for me at this part is understanding how to have the local DNS redirect work with non-standard ports on the proxy server, which I didn't think was possible. And I didn't want to change Unraid's default port - just seems messy and has a potential to make things confusing later w/a non-standard config if not absolutely necessary. EDIT: Ok, I just tried something given the "Host access to custom networks" was enabled but didn't seem to be working. I toggled Docker off, toggled that setting to disabled, toggled it to enabled, and restarted docker (applying between each step)...and all is working as expected now. So, if someone updates and hits a problem like this try that as a solution. Seems the setting may say enabled but actually isn't after update.

If it's on host, wouldn't it inherently conflict with the unraid server using port 80/443? (Similar with bridge)

I recently updated UNRAID and I believe something got screwed up in my NPM setup - wondering if maybe I missed a setting change somewhere. Only using NPM to do local network proxy hosts so I can use local DNS easily (using PiHole for the local DNS) (e.g., plex.local --> directs to NPM via local DNS --> actual IP based off NPM proxy config) Getting 502 Bad Gateway errors (and testing via CURL shows I can't connect between br0(NPM) and bridge (other containers) Host access to custom networks is enabled (which I thought should address the previous) I'm having trouble wrapping my brain around what to modify/test to fix and get back to previous functionality. I don't want each container that's currently on bridge to have a separate IP is the key thing that is confusing me since, my understanding is to do what I want NPM HAS to be on it's on IP. Any thoughts/pointers would be appreciated...somewhat stumped.

Thanks for the quick reply either way! Ended up just shifting to the earlier release and it's all working fine - wasted way too much time trying to fix it when that just did it with two line changes :/.

Has something changed with using this approach? Keep getting that the entrypoint.sh file can't be found. It's definitely there (everything starts fine w/mapping just the telegraph folder, removing the extra parameter results in telegraph just starting with the telegraph.conf in that mapped directory). Somewhat baffled - wondering if it's because it's a script that it's not seeing it?

Is there anyway outside of setting the container to privileged to get monitoring for iGPU/Intel? The CAP_PERFMON approach doesn't seem to work (per here https://docs.frigate.video/configuration/hardware_acceleration/ ) or I'm doing it wrong adding "--cap-add=CAP_PERFMON" into extra parameters.

Anyone know how to get an SMB share to open in Czkawka? Trying something like smb://192.168.0.11/files and it just turns red in the other places dialog. Tried with a hostname as well, same thing.