Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Can't log into google sites

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 4 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z Offline
      zedutchman
      last edited by

      So this has plagued me for the last 2 months since switching to PFsense.

      The problem is when I try and log into any google service (gmail, Youtube, Drive) with using any internet browser I get either a 1x1 pixle image or I get an error that states that there is a wrong setting associated with HSTS.

      So the setup is as follows:

      I use Centurylink DSL (I know, but I don't have random internet drops with the other service in town), My centurylink modem is bridged with everything turned off (firewall, DHCP) My Pfsense box does the PPPOE auth as well. I have Snort (no alerts show blocking), PFblocker (don't see it blocking in the logs within 10 seconds of trying), I thought maybe there was an issue with Squid and have since removed the package. I've killed Snort and pfblocker and i couldn't connect to their login page.

      I'm lost, trying to figure this one out. Not sure where to go from here. Wish I could drop an adsl2+ modem card in my box and eliminate the stupid modem anyway, but thats just a complaint.

      PFsense 2.3.1-RELEASE-p5 (nanobsd):

      Asrock AD2550R/U3S3 (Atom D2550), 4GB RAM, Intel X3959 PRO/1000 PT DUAL

      1 Reply Last reply Reply Quote 0
      • H Offline
        Harvy66
        last edited by

        The 1x1 pixel image is from PFBlocker. You must have it setup to block Google.

        1 Reply Last reply Reply Quote 0
        • BBcan177B Offline
          BBcan177 Moderator
          last edited by

          Thanks Harvy, yes the 1x1 is indicative of a DNSBL blocked Domain.

          zedutchman, you should however be getting Alerts in the DNSBL tab. Do you have a multi-segmented Lan? If so, you might need to enable the DNSBL permit rule option in the DNSBL tab. Also it shouldn't be blocking Google per se.

          Run the following to see what Google Domains are in DNSBL:

          grep "google" /var/unbound/pfb_dnsbl.conf
          

          "Experience is something you don't get until just after you need it."

          Website: http://pfBlockerNG.com
          Twitter: @BBcan177  #pfBlockerNG
          Reddit: https://www.reddit.com/r/pfBlockerNG/new/

          1 Reply Last reply Reply Quote 0
          • Z Offline
            zedutchman
            last edited by

            Looks like it was pfblocker. Not sure why. Didn't look at the logs before I did a fresh install. I've setup my essentials (OpenVPN, Squid) for now till I have a stable setup and I know I have no issues from before. That was my fix.

            I was running with top 20 ipv4 blocked. Followed a guide online and it did not work out. Probably didn't help that as a newb I ran Snort with PFblocker and had everything getting blocked.

            PFsense 2.3.1-RELEASE-p5 (nanobsd):

            Asrock AD2550R/U3S3 (Atom D2550), 4GB RAM, Intel X3959 PRO/1000 PT DUAL

            1 Reply Last reply Reply Quote 0
            • M Offline
              molykule
              last edited by

              @zedutchman:

              Looks like it was pfblocker. Not sure why. Didn't look at the logs before I did a fresh install. I've setup my essentials (OpenVPN, Squid) for now till I have a stable setup and I know I have no issues from before. That was my fix.

              I was running with top 20 ipv4 blocked. Followed a guide online and it did not work out. Probably didn't help that as a newb I ran Snort with PFblocker and had everything getting blocked.

              Hi,

              I had same issue 2 days ago. I am running squid-snort and pfblocker with dnsbl enabled. I think its your firewall. You need to allow port TCP/UDP on 8081 and 8443,
              Also, i found this in the forum. Please make sure that you have dns-resolver turned on and inside there dns-forwarder is unchecked.
              Also, to check if things are working go to 10.10.10.1 and you got to see 1x1 gif square of white color.
              Hope it helps

              Firewall > NAT > Port Forward> Edit
              Interface LAN
              Protocal TCP/UDP
              Click Invert match select LAN Address
              Destination port range From Port DNS and to Port DNS
              Redirect target IP 127.0.0.1
              Redirect target port DNS
              NAT reflection Use system default
              Filter rule association Create new associated filter rule
              Create rule that allows TCP/UDP from LAN net to  LAN address on port 53
              Create rule that allows TCP/UDP from This Firewall to Any on port 53

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.