No LAN connections
-
Hello, I need some help.
I created a proxmox environment with a firewall and 2 vm's. 1 vm for the pterodactyl web panel and for a web hosting environment and 1 vm for the pterodactyl wings. But when I executed the command curl mydomain, I got this error: curl: (7) Failed to connect to mydomain port 443 after 1 ms: Connection refused, also for port 80. I also get the error in other VMs within the LAN network if I execute curl to the same domains.
But when I can reach the panel and the domains that point to the web hosting server with my browser.
Port 80 and 443 are forwarded and allowed in the firewalls.
I found that this is only true from the VMs, i.e. within the network, maybe I am doing something wrong in the pfsense firewall for the local network, I don't know right away, everything are still at default.
And if I turn those rules off, I get no response to curls.
-
-
Yes, I had also found something about that but it doesn't want to work.
I then also found this but don't understand what they mean by External Address to Interface Address.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/nat-reflection.html#:~:text=To%20fix%20this%2C%20edit%20the,DNS%20must%20be%20used%20instead. -
I found it and then it works if I apply that fix from my last post but then it doesn't work from my own browner, does this mean I need to make different forwards? 1 for the WAN address as the destination address and 1 for the public ip?
-
Where exactly are you testing from?
What does mydomain resolve to?
-
@stephenw10
I'm testing in a VM on the same network as the web server and the mydomain resolves the public ip address of the physical interface. -
@jobbedf said in No LAN connections:
mydomain resolves the public ip address of the physical interface
The external Proxmox NIC? So not the pfSense WAN?
In that case NAT-reflection wouldn't work directly because the port forward would be from the pfSense WAN IP to the VM behind it not the public IP so would not match outbound traffic to it.
It's better to use split-DNS anyway though which would work fine here.
-
@stephenw10
Yes right, the Proxmox NIC.It can be correct because due to NAT reflection, only LAN access now works and not from my own browser.
But does split-DNS work if I have already forwarded port 53?
-
Forwarded it from where to where?
If you're testing from a VM behind pfSense and that VM is using pfSense for DNS then adding host override there will work.
