FIXED: Internal Network can't access webserver but external can

[GentlemanJimStacey]

EDIT: Much to my embarrassment as a DevOps Engineer who should have known better... I restarted the machine, and it started working just fine. Thought to be fair, it shouldn't have exhibited that behavior all of a sudden! Hahaha


I've seen posts similar to this on these forums, but it seems like the solutions they've recommended haven't worked for me.

Essentially, I have a webserver at 192.168.0.50 in LAN. My OPNSense firewall is the internet gateway and it's at 192.168.0.1. I've set up power forwarding so that WAN access to port 80 and port 443 are forwarded to 192.168.0.50, and I've changed the ports associated with my firewall GUI to others, so as to not cause any potential conflict there.

Anyone from the outside can visit "mydomain.com" just fine, receive certs, TLS, etc.
But when I try to access "mydomain.com" from my internal network (i.e. my PC at 192.168.0.110 trying to connect to mydomain.com), it fails saying "Connection Timed Out".

I do have NAT Reflection and automatic NAT outbound rule creation enabled. I also have IDS and IPS active, though haven't downloaded any rule sets, or anything like that. I also tried the DNS Override through Unbound DNS, but either I didn't do it right, or it didn't work either.

Any ideas?