Issue with hosting
-
Ok question I have spectrum internet with a static IP address but with spectrum to use my IP address I have to go from modem to router to pfsense. It's in RIP mode (static pass through) works fine but port 80/443 won't work I set up port forwarding on the router for HTTP/HTTPS but spectrum told me for that to work it has to go through 192.168.1.65. So none of my websites work. I've had chatGPT and Google AI go over everything. I have port forwarding setup on the firewall, I can see my web set from inside the network. Please help
-
So the Spectrum router is set to pass through all traffic to the pfSense WAN? Like a DMZ mode?
I would test that by pinging from some external IP address you know and see if that appears in a packet capture on the pfSense WAN.
-
@Redman420 said in Issue with hosting:
but port 80/443 won't work I set up port forwarding on the router for HTTP/HTTPS
Here are my WAN rules :
The first two are just simple firewall rules, as the final destination is pfSense itself.
The third one is a NAT rule, as it redirects traffic to my Synology NAS, which is sitauted in my pfSense LAN, using 192.168.1.33.Now, look again.
You see :
These counters go up when the rule is applied/used/matched.
When 'TCP IPv4 port 22' traffic comes into my pfSense WAN, it will match the third rule, and gets send to LAN IPv4 192.168.1.33.
That's it.
If your counters stay at '0' then this means the rules didn't match.
It could mean : traffic never even arrived at the WAN interface => the issue is upstream.Netgate (pfSense) wrote a small help guide : Troubleshooting NAT. Use it and issue done.
-
@Gertjan yes, I looked it up, they're all zero. I'm still learning pfsense i'm getting better at it. But i'm still having issues!
-
@Redman420 What model modem is the Spectrum supplied unit? Is there an actual separate router between your modem and your pfSense router?
-
@Redman420 said in Issue with hosting:
they're all zero
Two possibilities :
- The rule(s) don't match because they are wrong.
=> show them both - the actual NAT rule and the auto-created WAN firewall rule, and if there is something to correct, we'll tell you
- Traffic never reaches the pfSense WAN interfaces, the issue is upstream.
Btw : NAT rules isn't a pfSense thing. Every router on planet earth can do NAT, and people create NAT rules since they were invented by Cisco (their PIX firewall series was the first to implement it, Cisco didn't event invent NAT, they bought it from some one else, this was somewhere in the early 80 or even 70 ties, nothing changed since).
You (and we) will be the last to deal with 'NAT'. The next one will use IPv6 and NAT becomes mostly a thing of the past.
pfSense and my ISP router both use a GUI to make NAT rules. pfSense is different because it has more settings/parameters. But basically, it's always the same. You had to create NAT rules for your previous router/firewall also. - The rule(s) don't match because they are wrong.
-
@Redman420 said in Issue with hosting:
yes, I looked it up, they're all zero
Here is what I would always suggest when you trying to do a port forward, because it is pointless to look into pfsense settings and rules if you can not see traffic at the wan.
So setup a packet capture on your wan interface where this traffic would be coming in, set it for say some oddball port so you don't get flooded with just internet noise..
Then go to say a website that lets you send tcp traffic - can you see me . org is a easy to use site.
example - sending traffic to 6666
This should always be your first check when running into anything to port forward.. Because until pfsense actually sees the traffic on its wan, there is zero possibility it can forward anything.
Doesn't matter what rules you have or don't have - a packet capture (under diagnostic menu) will see the traffic be it you allow or not.
If you are not seeing the traffic - then either your isp is blocking, ie maybe your behind a cgnat. You have some other nat device in front of pfsense where you would have to forward to pfsense wan IP. Your maybe using a proxy or a vpn where what IP you are seen as on the public internet isn't your actual pfsense wan IP.
But if you do this test and do not see the inbound traffic - you know to look elsewhere other than anything to do with pfsense wan rules or port forwards.
-
@Gertjan so chatGPT say everything on the pfsense side is prefect but the ISP router when I set up the NAT is set up for 80/443 but spectrum and the router say NAT goes through 192.168.1.65. I'm not sure what to do. 
-
@johnpoz I did that it is the router/ISP I set up NAT but it says I have to go through 192.168.1.65
-
@Redman420 said in Issue with hosting:
I set up NAT but it says I have to go through 192.168.1.65
No idea that this is suppose to mean, is that your isp device network that pfsense connects to - is that pfsense wan IP.
Looks like you tried to post a picture?
-
I'm guessing the Spectrum router 'pass through mode' is a DMZ style mode where it forwards all traffic to a nominated internal IP. 192.168.1.65 in this case.
In that case that would need to be the pfSense WAN address.
-
@Redman420 said in Issue with hosting:
192.168.1.65
If that's your pfSense WAN interface then make sure that your pfSense LAN is not 192.168.1.1/24 but, for example, 192.168.2.1/24.
-
Yeah. I was assuming that isn't the case though because that would break all routing including outbound traffic.
