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

    SSL_ERROR on bloqued pages

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 396 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.
    • M
      mauricio2669
      last edited by

      Hello, we can configure squid+lightsiquid. The next step for us is configure squidguard (succefull). In "block" tab appears this line

      "9.01.2020 14:57:45 192.168.XXX.XXX/192.168.XXX.XXX connect.facebook.net:443 Request(default/blk_BL_socialnet/-) - CONNECT REDIRECT "

      but in user`s browser its show
      ERR_SSL_PROTOCOL_ERROR in crhome, we suppose that its certificates problem.

      reading forums here, (because we have a transparent proxy) we create a .html ext page (can reach succefull) and configurate to "redirect mode" to ext url. But its same.

      another option wich i read is configure GUI to http. without succefull.

      im dissapointed because show error page its de last touch to close this proyect.

      Somebody know where look? reggards

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @mauricio2669
        last edited by Gertjan

        @mauricio2669 said in SSL_ERROR on bloqued pages:

        because we have a transparent proxy

        You have read Transparent Proxies and HTTP/HTTPS ?

        My conclusion when I read that part, is : ok for http - and forget about https.
        Also : all big sites use https these days, http will be an unused protocol very soon now.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • M
          mauricio2669
          last edited by

          thanks for reply! nop, i dont read those info. i think that no transparent proxy is the next step.

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