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

    Intermittently unable to login after 2.4 upgrade

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 507 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.
    • B
      brainyron
      last edited by

      Hello,

      I'm hoping someone here may have additional suggestions as to things I should try/look for to troubleshoot and resolve this problem:

      Since upgrading my pfSense router to 2.4 (from 2.3.4) I've been intermittently hitting issues with my router including:

      • 502 Bad Gateway and 504 Gateway Timeout errors from the admin portal

      • SSH logins hang indefinitely without ever letting me get to a prompt

      • Random bad behavior from the router – connections failing, services in a wedged state and showing ports in use that should not be, etc

      No configuration changes were made from when the upgrade was made to when this issue started occurring (within 24 hours of the upgrade, IIRC). Thinking this was related to the memory leaks noted in bsnmpd, I have tried disabling all queries to SNMP, disabling SNMP entirely, and even upgrading to the 2.4.1RC hoping to fix that.  And again this morning, I found myself unable to login to the router.  In an effort to gather more information, I've upped my log file sizes significantly and have enabled remote logging to another server on my network as it would be very difficult to get connected to the physical console on this machine.

      Currently installed packages:
      acme
      mtr-nox11
      openvpn-client-export
      pfBlockerNG
      suricata

      Currently active services:
      dhcrelay
      dnsbl
      dpinger
      ipsec
      miniupnpd
      ntpd
      radvd
      sshd
      suricata
      syslogd
      unbound

      Running with an IPSec tunnel enabled for remote access, but this is used only occasionally.  Other VPN services are not currently in use/enabled.

      Hardware:
      Qotom Q355G4 (https://www.amazon.com/gp/product/B06XNWLR3J/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1)
      Core i5-5250U
      8GB RAM
      4x Intel NICs
      30GB SSD

      1 Reply Last reply Reply Quote 0
      • P
        PiBa
        last edited by

        Maybe give this possible fix a try?: https://forum.pfsense.org/index.php?topic=137103.msg758174#msg758174

        1 Reply Last reply Reply Quote 0
        • B
          brainyron
          last edited by

          @PiBa:

          Maybe give this possible fix a try?: https://forum.pfsense.org/index.php?topic=137103.msg758174#msg758174

          For some reason that thread didn't come up when I last searched this.  I've applied the patch and I'll report back if I don't see the problem again for ~48 hours since it's yet to go that long.

          1 Reply Last reply Reply Quote 0
          • B
            brainyron
            last edited by

            Going on three days and hasn't crashed on me since patching (and I noted that there was an official update to pfBlockerNG that included this).  I think we can say it was the cause of the issue.

            Thanks!

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