ZurkeyDurkey

Sorry for the delay; didn't see a notification that there was a new reply. I THINK I have them setup correctly. I was able to get nginx-Proxy-Manager-Official on its own IP address separate from my unRAID server. I was also able to specify different ports instead of the container's default of 80 and 443. In the router, I have the port forwards set for nginx-Proxy-Manager-Official's IP address, with Port 80 and 443 forwarded to the ports I specified in its container. So long as there are no issues or exposures with the way I did that, I should be good to go!

Thanks for the tips. I went ahead and set up my Port Forwards properly. Something clicked a couple of hours ago and I figured some of the other stuff out. One of the biggest problems was unrelated to what I typed. Basically, I have been remoted into my network via Wireguard (Unifi VPN Server) and working on all this. But, my laptop wasn't using my pihole's IP for DNS, despite it being manually set in the laptop settings, and on the VPN Server DNS settings. Flushing DNS and rebooting the laptop didn't fix. But, I removed and re-added it to the VPN Server, and it started resolving through the pihole! My final follow-up question; since I use macvlan on unRAID, each docker container on br0.1 will have its own IP address. If I manually set the Nginx-Proxy-Manager-Official container to the same IP as my unRAID server, I'll get an IP conflict in Unifi. Think I'll be fine with seperate IP addresses for containers like Nginx-Proxy-Manager-Official and the ‘arrs, so long as they are all on the same br0.1 network? Thanks again for your help.

Hi, I’m trying to get my containers properly setup on Docker. I just don’t know if I’m doing it right. The problems I face are not knowing the proper Docker Network types to use per container, not knowing why some containers get an IP in a different range (192 vs 172), why some using Bridge don’t show an IP, and why some port forwarding doesn’t seem to work. I’ve looked some of this info up, but I always find folks posting differing opinions on the matter. I'll describe my networking situation and obstacles below. For any examples of IPs and ports, I’ll be using ones I don’t plan to implement for privacy reasons. Let’s say I have my Unifi devices/controller on a subnet 192.168.40.xx, and unRAID on a different subnet of 192.168.120.xx. I have a custom network in Docker called br0.1 (192.168.40.xx). I have been trying to use the custom network, which is on the same IP range as my Unifi devices. In the Network Settings, “Enable Bonding” is NO, “Enable Bridging” is YES, and "Docker Custom Network Type" is macvlan. For my router, I currently have a UDM SE, and it acting as the primary/only DHCP server for my network. For now, the following containers I want to use are: Nginx-Proxy-Manager-Official binhex-official-pihole binhex-plexpass The ‘arrs I want binhex-official-pihole to be able to point to Nginx-Proxy-Manager-Official so that I can get local SSL certificates, and eventually setup a reverse proxy using my registered domain. I’m unsure if pihole and Ngnix need to be on the same subnet or network type in unRAID. For actual pihole and Nginx steps, I've been trying to follow the "Secure Local Domains Easily with Pi-hole & Nginx Proxy" YouTube video by TechDox, and the second half of the "Use a Reverse Proxy Server for Local SSL Certificates on all Home Lab Services!" YouTube video by WunderTech. Nginx-Proxy-Manager-Official won’t start if I have the Network Type set to Bridge, but it will start if I have the Network Type set to br0.1. It says on Community Apps that the custom network is recommended, anyway. However, I’ve read that the custom networks like the one I have with br0.1 cannot see other containers on a different network type. If I am trying to have pihole local records setup with nginx for generating local SSL certs, and eventually get a reverse proxy setup with my registered domain, should both containers be on br0.1? Another obstacle I have for Nginx-Proxy-Manager-Official; I have to forward ports 80 and 443 from my UDM SE. But I read that unRAID should absolutely NOT have its own ports of 80 and 443 forwarded. When using br0.1, I can give Nginx-Proxy-Manager-Official its own IP. If it is not supposed to use br0.1, does it still get its own IP or will it share an IP with unRAID? I'm not sure if it SHOULD have the same IP as unRAID or not. Also, depending on the correct option, do I change the port numbers for 80 and 443 on the Nginx-Proxy-Manager-Official container to something like 1280 and 12443, then forward those in the UDM SE? I’ve attached screenshots of an example from my UDM to see if that would be correct way to enter it. Moving onto binhex-plexpass; I have that container set as Host, which from what I’ve read is the proper Network Type. But if I were to install and configure the ‘arrs containers, what network type would they need to be on? Also, should I be seeing information on the Docker sections in unRAID for their “CONTAINER IP”, “CONTAINER PORT”, and “LAN IP:PORT”? Sorry for this mess of requests. I spent 10 hours yesterday scouring reddit threads and YouTube videos trying to find the most current, support steps for all this (as well as trying to understand it all), and ended up crashing my server and having to rebuild it from a flash backup. Any and all help is 1,000,000,000% appreciated. I feel like I'm just missing a couple pieces of critical info, and then hopefully this all will make sense to me.

I'm such an idiot, I forgot I turned off Threat Management to do throughput tests and never turned it back on. But, thanks for confirming that those appear to be malicious attempts. I got the issue resolved. Rather than make a separate post, there is one minor issue I have just been dealing with. After deleting my world (just folder "world"), and uninstalling/reinstalling the Docker for MineOS, I restored my server as "world2". But, an old cron job still seems to be running. It is doing hourly archive backups of "world" still. I think it is actual backups of "world2", but I can't confirm. I keep having to delete these backups before the SSD fills up. There is no visible Cron job running for this. Any thoughts?

Fixed my previous posted issue by nuking MineOS and completely re-installing it. Got a new issue now. Doesn't seem to have any impact on performance, but keeps logging an attempted connection every few seconds. com.mojang.authlib.GameProfile@14c59377[id=<null>,name=pfclown,properties={},legacy=false] (/193.35.18.210:51472) lost connection: Disconnected I get messages like this with the same IP, but different port. This occurs when MineOS docker is running, but the world doesn't need to be started for these logs to keep appearing. Attaching screenshot.

I'm running into an issue where my restore points stopped being created on after 5:00pm on December 3rd. The manual and automatic restore point creation via the MineOS GUI doesn't work. In the Restore Points box, it says "Uh oh!! Restore point attempt failed a few seconds ago." In the top-right corner, the pop-up window says "[world] backup failed 1". There are no updates for the MineOS docker, the world is still accessible, and creating an Archive backup works fine. It is just the Restore Points. I've tried running the server from 19.1 to 19.3, but that didn't resolve the issue, either. Stopped/Started the docker, rebooted the unRAID server, and updated the unRAID server, too. Any ideas on where I could start investigating?

I am getting similar crashes, as well. I thought I had fixed it (see above post), but it is randomly crashing. The error I mostly see in console is that the server failed to keep up. My unRAID server is connected via ethernet to 1000/1000 fiber service. I'll buy you another beer for help, binhex. crash-2022-04-20_21.38.21-server.txt

Well, I messed things up. Everything had been working perfectly with my binhex-minecraft docker and world. I decided to add a graphics card to my unRAID setup to experiment with cloud gaming via VM (I was following this guide: https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248/7 (pasting the link here doesn't seem to work). Before I got to Step 7 in creating the VM, I decided to make sure nothing was messed up with Minecraft. Alas, things were messed up. There appears to be a ton of server latency now, and it disconnects between 30sec - 80sec with the error: "Connection Lost - Internal Exception: java.net.SocketException: Connection reset." I have to shut down the server, and restart it in order to join again. But, the same issue occurs. I've removed the graphics card, and uninstalled the plugins I used in the guide, but the issue still exists. Any help is appreciated. UPDATE: I copied the binhex-minecraft appdata, and went ahead and nuked the docker installation. I reinstalled it, had it generate a new world, then overwrote that world folder with my old one. It works! No more issues. Though, I still would appreciate insight on what could have caused the issue. I'll attempt the graphics card installation another time, but skip all the pre-work from that guide since it more than likely caused the issue (or running one of the plugins).

Don't know if I missed this, but how would one reset the world entirely? Like, if we wanted to start fresh with a newly respawned world.