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

    IPv4 using ASN returns SSL certificate problem: self-signed certificate

    Scheduled Pinned Locked Moved pfBlockerNG
    6 Posts 3 Posters 484 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.
    • J
      jskeen
      last edited by

      Screenshot 2024-06-10 at 12.00.53 PM.png

      J GertjanG 2 Replies Last reply Reply Quote 0
      • J
        jskeen @jskeen
        last edited by

        @jskeen

        I forgot to mention. Don't know when this broke, but know it used to work. I running pfblockerNG 3.2.0_10 on pfsense 24.03.

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

          @jskeen

          IPv4 using ASN returns SSL certificate problem: self-signed certificate

          What where when ?

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

          J 1 Reply Last reply Reply Quote 0
          • J
            jskeen @Gertjan
            last edited by

            @Gertjan I did a force update this morning, The pfblockerNG log file shows:
            [ AS3356_Level3_hulu_v4 ] Reload [ 06/11/24 09:35:26 ] . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS11483_Conviva_hulu_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS13335_Cloudflare_hulu_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS15133_Edgecast_hulu_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS22822_LimelightNetworks_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS40027_Netflix_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            [ AS54113_fastly_hulu_v4 ] Reload . completed ..
            Empty file, Adding '127.1.7.7' to avoid download failure.

            and the error log shows:
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ AS16625 ] [ 06/10/24 09:56:14 ]
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ AS20940 ] [ 06/10/24 09:56:14 ]
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ as16625 ] [ 06/10/24 09:57:55 ]
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ as20940 ] [ 06/10/24 09:57:55 ]
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ as16625 ] [ 06/10/24 09:58:10 ]
            [PFB_FILTER - 2] Invalid URL (not allowed2) [ as20940 ] [ 06/10/24 09:58:10 ]

            Didn't get the self signed certificate error this time.

            johnpozJ 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @jskeen
              last edited by

              @jskeen so your issue your having is the asn your trying to download are not downloading?

              I tried to duplicate your problem - but working here.

              What version of pfsense, what version of the pfblocker package?

              duplicates.jpg

              Are you routing traffic through a vpn, or using an upstream proxy?

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              J 1 Reply Last reply Reply Quote 0
              • J
                jskeen @johnpoz
                last edited by

                @johnpoz

                I'm running pfblockerNG 3.2.0_10 on pfsense 24.03. I have been doing the updates through a vpn, which has been working without a problem. I changed it to force the update out the wan, which worked.

                Taking a look at the vpn logs, it has started showing some udp write errors, although the vpn channel would come up and appear to function properly. Since it works through the WAN, it must be the vpn causing the problem. Will have to take a closer look at that.

                I appreciate your help! I wouldn't have suspected the vpn, if you hadn't asked the question.

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