TeddyTux

I figured it out! No issues on the unraid end. I needed to setup some firewall rules on the router. Thanks for your help! Apologies for the wild goose chase.

Hey Friends! I added a 10gbit PCIe card to my nas, and set it up as br0/eth0. Bridging is enabled. Bonding is disabled. I’m noticing the unraid plugins can’t check for updates though. Fix common problems indicates it can’t connect to github and the DNS settings need updating. In network settings, I see this error in red at the bottom left of screen: Interface - Ethernet Port 1 is down. Check cable! I normally leave the unraid in auto dhcp, and then assign static IP at the router. Diagnostic attached. Any guidance is appreciated! servetux-diagnostics-20251116-1236.zip

Origamiofficial's Pihole-Unbound Community Applications Template Welcome to the support page of the Origamiofficial's Pihole-Unbound Community Applications template. This template installs a supercharged Pi-Hole docker container with Unbound built-in. Pi-hole includes a caching and forwarding DNS server, now known as FTLDNS. After applying the blocking lists, it forwards requests made by the clients to configured upstream DNS server(s). However, this leads to some privacy concerns as it ultimately raises questions about whom you trust with the all the dns lookup data from your household. You have a few options of whom to trust: 1. Your ISP Pi-hole -> FTLDNS -> Your ISP -> Authoratative Server Pros - Easy. Works out of the box. Just plugin and turn on your ISP provided modem. Cons - Your ISP is collecting all your DNS searches, building a profile on you, and selling that data. 2. A third party DNS service (ie. Quad9, Cloudflare, Google, etc). Pi-hole -> FTLDNS -> Cloudflare -> Authoratative Server Pros - You're circumventing your ISP Cons - You're still trusting a third party company, so choose carefully. In this case Cloudflare would have the ability to collect all of your DNS lookups, because they are an intermediary between your home and the authoratative server. 3. Run your own recursive DNS server, like Unbound (.....this is what this container does!) Pi-hole -> FTLDNS -> Unbound -> Authoritative Server Pros - You're self hosting Unbound which will cache DNS results locally. If Unbound doesn't have the DNS record cached already, it'll go upstream directly to the Authoritative Server. No intermediaries! No trusting your ISP or a 3rd party service. Cons - Authoratative Servers do not currently support DOT/DOH. I am happy to help to the best of my abilities, but I am only publishing this template to community apps to make it easy for other users. See here for the official github page for the project and support documentation: https://github.com/origamiofficial/docker-pihole-unbound My personal setup howto: I switched the docker container to my custom swag network. Port 80 and 53 were already in use. Update the timezone Switch port 53 tcp & udp to something else. Example: 65053 Switch port 80 to something else. Example: 65080 Update the password In my personal situation, Unbound fails to start and logs reflect an error in unbound.conf. I jump to that line of the config (at the very end, in Local Zone section), and comment out the two offending lines: nano /mnt/user/appdata/pihole-unbound-daily/unbound.conf ########################################################################### # LOCAL ZONE ########################################################################### # Include file for local-data and local-data-ptr ##COMMENT OUT## include: /opt/unbound/etc/unbound/a-records.conf ##COMMENT OUT## include: /opt/unbound/etc/unbound/srv-records.conf ########################################################################### # FORWARD ZONE ###########################################################################

Sorry for the trouble! The template already defaults to config = /mnt/user/appdata/redbot. That should be your persistent data storage. What else did you set? Thanks

Your PC ---> Pihole ---> Unbound ---> Authoritative DNS Server There are no authoritative servers that support DOT/DOH yet, unfortunately. I don't know how you would adjust unbound settings. I'd check with the github page for the container. I'm not sure why you'd want to though. It's one of the perks of the container. It automatically coordinates the pihole/unbound stack for you. Pihole starts up automatically pointing at the unbound server and everything.... simply load your adlist of choice.

Hi! You are correct, you simply wait for the github repo to update, then restart the container. The docker container will always pull the newest version on restart. Right now, there is nothing to do except wait. You should not be attempting to make changes in unbound.conf (I'm guessing you're reading a bunch of different guides...). You should make changes by adding or updating environment variables to the docker container. Check the github page for a list of common options: https://github.com/pi-hole/docker-pi-hole/#environment-variables I simply created the template to make it easy for the community to use pihole+unbound on Unraid. I'm not affiliated with the github project, but I am happy to help when possible. Upstream Servers are irrelevant. Unbound is the upstream server, but locally hosted. Thats why it points at 127.x.x.x. Eliminating reliance on a 3rd party like google/cloudflare/etc. See here for relevant discussion on doh/dot/unbound: this was a helpful dns primer: https://threat.media/definition/what-is-an-authoritative-dns-server/

I always understood that stars are good indicator of projects on github. This one has 900+ stars and was updated inside of a month, so I figured it was widely adopted/well regarded.

Pihole-Unbound Community Applications Template Welcome to the support page of the Pihole-Unbound Community Applications template. This runs both Pi-Hole and Unbound in a single container. The base image for the container is the official Pi-Hole container, with an extra build step added to install the Unbound resolver directly into to the container based on instructions provided directly by the Pi-Hole team. Pi-hole includes a caching and forwarding DNS server, now known as FTLDNS. After applying the blocking lists, it forwards requests made by the clients to configured upstream DNS server(s). However, this leads to some privacy concerns as it ultimately raises questions about whom you trust with the all the dns lookup data from your household. You have a few options of whom to trust: 1. Your ISP. Unfortunately, they often monetize and sell this marketing data. Example: Pi-hole -> FTLDNS -> Your ISP -> Authoratative Server 2. A third party DNS service (ie. Quad9, Cloudflare, Google, etc). Unblocked DNS requests from Pi-hole will hit FTLDNS then pass to third party DNS. You're still trusting a third party company, so choose carefully. Example: Pi-hole -> FTLDNS -> Cloudflare -> Authoratative Server 3. Run your own recursive DNS server, like Unbound! This is what this template does. Unblocked DNS requests from Pi-hole will hit Unbound then be made directly to the authoritative servers instead of routing through a third party dns services. This way you & only you, maintain full control of your DNS data. Example: Pi-hole -> Unbound -> Authoritative Server This template installs the one-container (new) version of the docker container described at the github for the project: https://github.com/chriscrowe/docker-pihole-unbound/tree/main

##----Temporary Location! I will relocate this post to Docker Container forum when new template is approved, and added to Community Apps----## Red-DiscordBot V3 Community Applications Template Welcome to the support page of the Red-DiscordBot V3 Community Applications template. This template installs the newest Red-DiscordBot in a convenient multi-arch container. Red is self hosted, fully modular, Discord bot – meaning all features and commands can be enabled/disabled to your liking, making it completely customizable. The default set of modules includes and is not limited to: Moderation features (kick/ban/softban/hackban, mod-log, filter, chat cleanup) Trivia (lists are included and can be easily added) Music features (YouTube, SoundCloud, local files, playlists, queues) Stream alerts (Twitch, Youtube, Picarto) Bank (slot machine, user credits) Custom commands Imgur/gif search Admin automation (self-role assignment, cross-server announcements, mod-mail reports) Customisable command permissions Additionally, other cogs (plugins) can be easily found and added from our growing community of cog repositories. GitHub Repositories Cog-Creators Red DiscordBot: https://github.com/Cog-Creators/Red-DiscordBot PhasecoreX's Docker Container: https://github.com/PhasecoreX/docker-red-discordbot Docker Hub: https://hub.docker.com/r/jonasbonno/discordbot Cog Repository: https://index.discord.red/ Example to launch a new Red Bot in your Discord, and load the Audio Cog so you can play music from youtube etc: Create a new bot in the Discord Developer Portal: https://discord.com/developers/applications Enable Administrator Permissions Enable Privileged Gateway Intents Create and Copy the Token for use in the Unraid Template Install the Template using the new Bot Token Invite the Bot to the server using the link generated and displayed in logs Example: I am assuming your chosen prefix = . Load the Audio cog by sending a message to the bot on discord with: .load audio Check here for a list of audio commands, and more details: https://docs.discord.red/en/latest/cog_guides/audio.html#basic-audio-use

Hello! I have the Gigabyte X570 AORUS ELITE WIFI with Bios F38d and AMD Ryzen 5 5600 processor. While doing a parity check for 15 hrs etc, there is no issue and the system is very responsive. If the system is idling though it inevitably hangs. It becomes non responsive via gui/ssh/etc. I'm thinking it's an AMD bios thing...super frustrating. Things I've tried: SVM Mode -> Enable IOMMU -> Enable Global C States Disabled Typical Idle Current CSM Enabled & Legacy Boot I have recorded a syslog, and attached it. Any guidance would be incredible. I've been struggling with this for wayyyyyy too long tbh. Edit: Made a few tweaks, and fired it back up..... Will report back. - I found an udpated bios. Updated to F38e - ACS Enable -> Enable - Enable AER Cap -> Enable syslog

Fantastic guide! Thank you for your effort on this! One thing that caused me a lot of tripped me up 4. Under `listeners:` and `- port: 8008` change `bind_address: ['0.0.0.0']` I didn't realize what you meant. Ended up spinning my wheels for a few hours. Just in case someone else runs into issues, your line should look like this: bind_addresses: ['0.0.0.0'] I didn't know the first part had to be removed, because you didn't explicitly say it. I kept leaving it in there and only changing the second ip to 0.0.0.0. Dumb. I know But just in case another idiot comes along