Pfsense not loading websites

Here is the setup.

  • Fiber service without static IP service provider blocks all incoming ports. But cloud services work. Waiting for my static IP in a day or to.
  • Fresh install of pFsense on a Protectli Vault FW4B - 4 Port, Firewall Micro Appliance/Mini PC - Intel Quad Core, AES-NI, 4GB RAM, 32GB mSATA SSD
  • HP-Switch-48-PoE.

Out of the blue, websites will not load. Google search page works but when I click on any of the search page links pulls up the connection issue page. Even if I go to a page I know, like youtube or even this forum. Then 5 mins later will start working again. keeps doing muetple times a day.

CPU running fine. The only thing I see in the Firewall System log is Default deny rule IPv4 (1000000103) nothing else. The only firewall rule I have setup right now is to Allow all traffic on the lan ports. I even plugged my computer directly into the lasn port to make sure it was not an issue with the switch and still having issues. not seeing any wan dropouts in the logs.

post the rules for WAN and LAN (Firewall > Rules > WAN then LAN)

Your logs don’t show any blocked connections from the LAN interface, only from WAN and IOT. Based on the screenshots, this is expected.

What is the exact error you get in the browser? There should be a button on the error page to get more details.

It could be a DNS issue. The next time you have this problem, see if you can ping an address directly (like 1.1.1.1).

As already mentioned, pinging an IP whilst the browser is not connecting will determine whether this is an Internet connection interruption or a DNS resolution issue. I usually have an ongoing ping running in the background e.g. ping 8.8.8.8 -t, whilst troubleshooting such issues.

If DNS resolution issue, do you have any ad-blocking services running? A lot of Google search results these days include campaign tracking data, which some ad-blockers will block.

Once, my ip provider gave me a static IP. The dropping connection stopped. Been working fine since then. Not sure what the issue was.