MadOne627

Been a while but after learning a few things about networking in the past year or so, I now know exactly what the issue was. I believe skols said my router did not support loopbacking. At the time i just followed your workaround and it worked great for a while. Recently I have been trying to get a collabora server up and running. In order to use the unraid docker container, you are required to use of the nextcloud.myaddress.com to work properly. After a bunch of research and breaking my router a few times, (my wife is a saint) i figured it out. You can not use loopbacking behind a second router, the open wrt guys do a great job explaining it here. The section titled "OpenWrt as cascaded router behind another router (double NAT)" applies to my issue. Thought i would come back an share in case someone else is trying to do this. I was forced by my isp at the time to use there router and cascade all my firewall changes down to my personal router. Lead to a bunch of issues. If your isp was like mine this may lead to you have the same issue i was having. Thanks again for your help a year ago guys. I have gotten a ton of mileage out of this tool.

Thats it. I can now get to it internally with the LAN IP:Port and can get to it via web address via WAN. Thanks for your guidance skols!

Thanks for your help skols. I fixed the images above. Seems like i embedded them wrong. I tried what you said and now it works on my lan but not via wan. Is this just how this configuration works where unless your router supports hairpinning the right way you either get internal or external use? It seems like i should be able to create an exception where if i approach swag using an internal ip address i get directed to the 192.168.XXX.XXX:444 address and via the external route (or router IP?) get the nextcloud.example.com. Though maybe i am just defining hairpinning in a different way. Again thanks for helping some random guy on the internet out.

Hey Guys, I have been doing my best to read up on peoples answers to a question that has been asked several time about lan connections failing but wan connections working. I am currently able to access my nextcloud server externally after using the spaceinvader one videos as a guide, but as soon as i configured the swag docker for reverse proxy i can no longer connect locally. Some had previously mentioned hairpinning on your router could cause this problem and I have looked into this as well. I am using an OpenWRT on a Linksys and have for my port forwarding Enabled NAT loopback. Which seems to be the same thing i think. The weirdest part of this to me is when i use my vpn in browser and i open open webui for nextcloud it works, seemingly because its routed externally (nextcloud.example.com)? Not very sure why this worked, so i tried using the local address and port in my web browser (https://192.168.XXX.XXX:444), this sure enough returns via the domain and external routing(returns via nextcloud.example.com). Do i have something configured wrong in my swag that is forcing my calls out or is this due to Loopback not being the same as hairpinning. Please see my config files below. Here is the Open WRT port forwarding i was talking about if it helps Any guidance you could give me would be great. I really appreciate it!