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

    Squid proxy reports (transparent) how to log https traffic?

    Scheduled Pinned Locked Moved Cache/Proxy
    4 Posts 2 Posters 3.4k 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.
    • E
      eirikr
      last edited by

      I am looking at my proxy report for my computer and I stream youtube and twitch a lot and I don't see it listed? i can see imgur but a lot of websites are missing.

      I run it as transparent, this is how I want it.

      How can I monitor my https traffic?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        In transparent mode, squid only captures HTTP traffic. To transparently capture HTTPS requires SSL interception and installing a custom root CA on your clients, and even then it's a bad idea in general.

        Block outbound HTTPS and configure your proxy settings in the browser/OS to use squid directly, then it can properly capture HTTPS requests.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • E
          eirikr
          last edited by

          my goal is not to touch the host os/browser/computer at all, I might give consideration to something that allows gpo to push out the anything needed.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Search for squid 3 ssl interception then, many threads out there already. You may be able to push a CA via GPO, but there is no way to get HTTPS without some client-side modification. That's the whole point of HTTPS, to prevent MITM attacks from breaking the chain of trust. You have to trust your own CA which then makes fake certs to break into the connections (to put it simply). It's a really bad practice.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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