Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Blocked page by Squid Proxy is not Squid's default page

    Scheduled Pinned Locked Moved Cache/Proxy
    5 Posts 2 Posters 2.0k 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.
    • emammadovE
      emammadov
      last edited by

      Hello,

      I have installed and setup Squid Proxy and SquidGuard and blocked some categories in Common ACL. I enter websites which I blocked, blocked page contains following sentences:

      400 Bad Request
      The plain HTTP request was sent to HTTPS port
      nginx

      But I want Squid default blocked page to be shown to users like in the second attached picture. How can I do it?
      Untitled-1.jpg
      Untitled-1.jpg_thumb
      squiddefaultpage.jpg
      squiddefaultpage.jpg_thumb

      Elvin

      1 Reply Last reply
      Reply Quote 0
      • T
        Tecnergy
        last edited by

        how to even get the behavior on the second pic? I thought HTTPS sites couldn't show the squid error page.

        For the first problem:

        try to modify the option protocol inside webConfigurator located in System/Advanced/Admin Access. Change it to HTTP (not advised but I don't know how else to bypass it)

        1 Reply Last reply
        Reply Quote 0
        • emammadovE
          emammadov
          last edited by

          The second picture is Squid's default page blocked which I have found on google.
          The problem is when I check WebGUI redirect, Squid replaces default block page with 400 Bad Request.

          Changing HTTPS TO HTTP is not insecure?

          Elvin

          1 Reply Last reply
          Reply Quote 0
          • T
            Tecnergy
            last edited by

            @emammadov:

            The problem is when I check WebGUI redirect, Squid replaces default block page with 400 Bad Request.

            If you enable webgui redirect, all requests for the pfsense ip will go through port 80 (HTTP), I guess nginx does not like it when HTTPS traffic goes through there.

            @emammadov:

            Changing HTTPS TO HTTP is not insecure?

            Yes, but I don't know how else to get pfsense to show the error page on HTTP sites with squidguard. If I select HTTPS, I get your first error image.

            I need guidance too.

            1 Reply Last reply
            Reply Quote 0
            • emammadovE
              emammadov
              last edited by

              Thank you for your reply. I leave it as it is.
              In TCP Port, section is empty. Default 80 for HTTP, 443 for HTTPS. How can I add two port in the same section? It only allows one port number. If I add for example 445, then it should apply both?

              Elvin

              1 Reply Last reply
              Reply Quote 0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              • First post
                Last post
              Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
              Privacy Policy · Cookie Policy