ThickPeep

So instead of bridge, are you saying to set it to "Custom network:Br0"? What does that do exactly? I am shifting my setup from another server that was not running unraid, and I ran that same container in bridge before. I am not familiar with that custom network option

Hello everyone, I have run into an issue that I cannot seem to find a solution for. No matter how I attempt to google the issue, I am not really finding the specific instance (or close to it) that I am experiencing. Problem: I want to run the container "Pihole + unbound" from chriscrowe. This requires port 443, and that is the default port for https traffic to unraid. If I change that default port in unraid, I completely lose access to the Unraid webGUI (I cannot even access it locally on the machine, it pulls up firefox and says the server cannot be reached). I then changed the port back in the igent file (iirc, it may have been the network file) on the flash drive and attempted a reboot. This did not fix the problem, and the only way I was able to regain access to the server was to wipe most of the config folder out (keeping my shares/array info). I attempted again to change the port, and then provision a new cert as stated on the unraid docs, and ran into the exact same problem. Any ideas on what I am doing wrong here? Is this just a port you cannot really change? When I google the topic (I have been for 2 days now) I find other people who have lost access to the Unraid webGUI, but all for different reasons than mine, and their fixes did not remedy my issue. I want to add, I am not even using port 443 to connect to my server, I am using the default port 80 for http traffic. If relevant, my unraid version is 6.12.6