Why cant I access the public IP-Adress of my pfSense VM?

Question

Hello together,

I am currently creating a pfSense firewall environment in Azure as part of my final project of the training. I have
already created two test client VMs and taken the pfSense machine from the market place.
In the assigned NSG, I have created the inbound rules for SSH and HTTPS.
Unfortunately, the IP address is not reachable, pingable or visible via nslookup.

Best Regards,
Tim

Answer 1

Hi @Tim Negele,

Thanks for contacting Microsoft Q&A platform.

Below are some possible reasons for this behavior, please check and let us know.

1. Ensure that the NSG associated with your pfSense firewall allows inbound traffic on ports 22 (SSH) and 443 (HTTPS). Verify that the NSG rules are correctly configured and applied to the network interface of the firewall VM.
2. Double-check the configuration of pfSense to ensure that it is properly configured to accept SSH and HTTPS traffic. Verify that the firewall rules allow incoming connections on ports 22 and 443.
3. Verify that the pfSense virtual machine is running and has the correct network configuration. Ensure that it has a valid IP address assigned and that the network interface is attached to the correct virtual network.
4. Check the subnet and virtual network configuration to ensure that the pfSense firewall VM is deployed in the correct subnet and virtual network. Ensure that the subnet allows inbound and outbound traffic as necessary.
5. Enable NSG flow logs to monitor traffic and check if the traffic is being blocked by NSG rules. Review the logs to identify any denied traffic and adjust NSG rules accordingly.
6. Verify that there are no Azure-specific networking issues, such as route table misconfigurations or network connectivity problems within the Azure environment. Check the Azure portal for any service health advisories or incidents related to networking.
7. If possible, try to connect to the pfSense firewall VM from another VM within the same virtual network to see if the issue is specific to external connectivity or affects internal communication as well.

Hope this helps you.

Answer 2

Hi @v-vvellanki-MSFT ,

thank you for your advise. I entered the Public-IP of the VM instead of the private one at the destinations of my NSG rules.

Now its working for me