Another Port Forwarding Post
-
Accessing the site from a private 192.168.1.x network behind PF to a 192.168.1.x address. MY windows 7 PC that has virtualbox running on it with the web server. Access to the site is fine from any computer on the network, just not the host PC with VirtualBox running on it.
What it does is when i put the web address in it automatically directs me to the HTTPS address which don't exist, no certificates for it. Anyway i just went into my web server and turned SSL from default to off on each domain and that fixed the problem. Only problem is if i ever decided to do SSL on those sites ill have to figure out the real reason it didn't work.
But to answer the other half of your question. I do have NAT reflection on.
-
"Accessing the site from a private 192.168.1.x network behind PF to a 192.168.1.x address."
then pfsense has nothing to do with that traffic. You only talk to pfsense if your wanting OFF the 192.168.1.x network.
If you don't have SSL cert, then no your webserver can not serve up SSL. If you want to access SSL from outside pfsense, then you would need to forward 443.
But again if your just talking between 2 clients on your same 192.168.1.x network - then pfsense is not involved in that conversation. Unless you were bridging to interfaces on pfsense, and one machine was connected to 1 and other connected to other interfaces on the pfsense bridge. Other than sort of setup - no pfsense is not involved in local network traffic.
