@allkemyst said in Can't connect to 9443 port on a host in the same subnet:
Subnet: 20.0.0.1/24 | DHCP4 on
while technically that can work, its a horrible idea to use public IP space internally. Not not just 10.0.1/24 as your lan2 network?
I try to test the port on PfSense, i can reach the port 22, but can't reach the other ports, including 9443.
that screams firewall on that box or your vm host..
To validate this to yourself sniff on your lan 2 interface while you send a test to these ports.. Do you see the traffic leave pfsense, but not get an answer.. But you can ping and ssh works - that screams host firewall to me.
edit: or the config of whatever service this is set to listen on IP 192.168.1.x (whatever your old network was) and not 20.0.0.x
Unless the traffic is routed over pfsense, pfsense has nothing to do with the traffic - if it is routed, maybe your doing a policy route and this is sending traffic out your wan gateway. Without seeing the rules we really have no idea, maybe you set the rule to allow tcp, but this is udp?