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

    Snort Port 443 Timed Out

    Scheduled Pinned Locked Moved IDS/IPS
    2 Posts 2 Posters 351 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.
    • K
      kbohlken
      last edited by

      What happening here? Is my firewall not seeing the internet?

      Starting rules update... Time: 2022-01-14 13:02:31
      Downloading Snort Subscriber rules md5 file snortrules-snapshot-29190.tar.gz.md5...
      Snort Subscriber rules md5 download failed.
      Server returned error code 0.
      Server error message was: Failed to connect to www.snort.org port 443: Operation timed out
      Snort Subscriber rules will not be updated.
      Downloading Snort GPLv2 Community Rules md5 file community-rules.tar.gz.md5...
      Snort GPLv2 Community Rules md5 download failed.
      Server returned error code 0.
      Server error message was: Failed to connect to www.snort.org port 443: Operation timed out
      Snort GPLv2 Community Rules will not be updated.
      Downloading Emerging Threats Open rules md5 file emerging.rules.tar.gz.md5...
      Emerging Threats Open rules md5 download failed.
      Server returned error code 0.
      Server error message was: Failed to connect to rules.emergingthreats.net port 443: Operation timed out
      Emerging Threats Open rules will not be updated.
      The Rules update has finished. Time: 2022-01-14 13:07:50

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        That's how it appears. Or at least it "thinks" it can't see the Internet. The connection attempts on port 443 (HTTPS, or SSL connection) is timing out. That means either the remote site is down, or your personal connection is unable to reach the remote site.

        Since this is happening for both Snort and Emerging Threats rules, I would think it unlikely for BOTH remote sites to be down at the same time. Thus that would point the finger over to your end of the connection as where the problem is likely to reside.

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