Wnagge

Sorry for the late reply. I watched that video and confirmed that I do not have CGNAT. I do have a forward facing IP and can access the minecraft server all the time on the IP:Port, but only sometimes on subdomain.DuckDNS.org:Port. I still haven't solved this.

I wanted to start a minecraft server for me and my friends to play on. I have the server successfully running using Crafty Controller and have forwarded port 25565 on my router. I am trying to expose it to the internet using duck dns but having some issues. For example my friends should be able to connect to the minecraft server from subdomain.duckdns.org:25565. It works occasionally but very infrequently. I am using mcsrvstat.us to verify if it is working or not. almost always the duckdns address doesn't work, but if I put in my public IP address (same one showing in duck dns) as IP:25565 it says the server is online. I'm very confused as to why this isn't working with duck dns. I have had duck dns working flawlessly for over 2 years for my wireguard vpn which still works. Looking for any help on this or if there is a better way to approach the problem!

Update: So I turned off bridging, which allowed the port forward to go through in the Shaw app, then reenabled the bridging in UnRaid and everything is all good!

First of all, thank you VERY much for all the detailed information! Unfortunately most of the things mentioned in your second post seem above my skill level at the moment. However, your mention of bridge mode led me to turn that off so that it is as if I didn't have the second nic, and should be back to the same as when port forwarding did work. So I turned off bridge mode, the mac address for the interface physically connected to the ISP modem/router is showing connected. But now Shaw's broken app they force you to use for port forwards doesn't work and won't let me sign in, sigh. I guess I will wait until their app comes back online and see if that solves my problem! Once again, thank you for the replies and I'll provide an update to my situation when I can.

It is directly into my ISP modem, not sure what the forbidden routers are even lol. My internet provider is Shaw if you're in Canada and they make you port forward through their dumb app now and not through the web ui. I am not trying to port forward through the unraid machine if that's what you mean (wouldn't even know how to do that), but I was able to port forward through the Shaw app prior to adding the second NIC and can still do it though the app for other devices

Hello smart people of the Unraid forum. I'm not sure if my issue is actually with Unraid or not but hoping that someone can help! I have an Unraid server with dual NIC, one on the MOBO and one PCIE card. The MOBO interface is connected to my ISP modem and the PCIE interface is connected to a POE switch which is in turn connected to IP cameras. Prior to adding the PCIE NIC, I was able to add port forwards no problem, and the previously forwarded ports are still working. Now that I have the dual NIC I am getting an 'please try again' error anytime I try to forward a new port. I tried to forward a port for another device and it is working which leads me to believe the issue is with my Unraid machine. Onto some further information. In my ISP 'connected devices' page, it shows 2 devices with the IP of my Unraid machine. One is MAC address D8:5E... (eth0) and the other is MAC address 30:52... (eth1) Based on a MAC address lookup tool online, the D8:5E device is Gigabyte while the other is a generic Chinese brand so I would say eth0 is the MOBO connection that should be directly to the modem. On the ISP 'connected devices' it shows the eth1 MAC address device as online and the eth0 device shows offline but the server is definitely connected to the internet. The IP cameras also all show as online devices. Here is my network settings. I'm not sure what of the data is sensitive so if you need to see anything that I've redacted I can provide it. End result is trying to find out if what I'm seeing in the network settings and ISP network information has anything to do with not being able to port forward!