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

    Unable to access web interface.

    General pfSense Questions
    2
    4
    824
    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.
    • T
      TomT
      last edited by

      Hi

      pfSense 2.3.2-RELEASE-p1 (amd64)
      There have been NO config changes made in the last 3-4 days.

      Not had any issues and was able to log into the Web Interface earlier today.
      Just tried to log in and it times out trying to get to the Web Interface.
      I've tried from different browsers with the same result.

      No issues getting online or accessing the box via SSH.

      Any idea how I can get access again, ideally without having to fully restart ?

      Thanks

      1 Reply Last reply Reply Quote 0
      • T
        TomT
        last edited by

        Hi

        It seemed to start working again, but has now do it again.

        top shows the following and there is not a lot happening on the network at this time.

        last pid: 61424;  load averages:  0.91,  0.56,  0.38   up 53+15:36:15  13:26:30
        50 processes:  2 running, 48 sleeping
        CPU: 19.3% user,  0.0% nice,  6.9% system,  0.2% interrupt, 73.6% idle
        Mem: 70M Active, 2419M Inact, 991M Wired, 144K Cache, 871M Buf, 4350M Free
        Swap: 16G Total, 16G Free
        
          PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
        14264 root          1 102    0 45180K  9404K CPU2    2   2:39  99.85% pkg
        61563 root         17  20    0  1178M  1041M nanslp  3  20.6H   1.27% ntopng
        61408 root          3  30    0 28124K  9168K uwait   2  92:49   0.00% redis-ser
        84937 unbound       4  20    0 96744K 72120K kqread  0  40:40   0.00% unbound
        16033 root          1  20    0 16676K  2312K bpf     3  15:23   0.00% filterlog
        82251 root          1  52   20 17000K  2568K wait    0   8:13   0.00% sh
        41035 root          1  20    0 14504K  2308K select  1   7:41   0.00% syslogd
        71571 root          5  20    0 19108K  2376K accept  2   7:38   0.00% dpinger
        23780 root          1  20    0 14408K  1952K select  3   4:51   0.00% powerd
        40446 root          1  20    0 21036K  5200K select  3   3:39   0.00% miniupnpd
        71407 root          1  20    0 30140K 17968K select  1   2:52   0.00% ntpd
        25379 root          1  20    0 39136K  7360K kqread  2   2:51   0.00% nginx
        25596 root          1  20    0 39136K  7524K kqread  3   1:53   0.00% nginx
          269 root          1  20    0   262M 25140K kqread  1   1:51   0.00% php-fpm
        90245 dhcpd         1  20    0 24812K 13748K select  2   1:33   0.00% dhcpd
         5966 root          1  20    0 50312K  6924K select  0   1:09   0.00% mpd5
        23820 root          1  52    0   287M 49128K piperd  1   0:23   0.00% php-fpm
        

        And now it's just started working again.
        top is currently showing:

        last pid: 98640;  load averages:  0.84,  0.67,  0.44   up 53+15:38:08  13:28:23
        48 processes:  1 running, 47 sleeping
        CPU:  1.6% user,  0.0% nice,  1.9% system,  0.2% interrupt, 96.3% idle
        Mem: 69M Active, 2417M Inact, 991M Wired, 144K Cache, 876M Buf, 4353M Free
        Swap: 16G Total, 16G Free
        
          PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
        23820 root          1  52    0   287M 49256K accept  1   0:23   3.86% php-fpm
        61563 root         17  20    0  1178M  1041M nanslp  1  20.6H   1.27% ntopng
        61408 root          3  30    0 28124K  9168K uwait   2  92:50   0.00% redis-ser
        84937 unbound       4  20    0 96744K 72120K kqread  1  40:40   0.00% unbound
        16033 root          1  20    0 16676K  2312K bpf     1  15:23   0.00% filterlog
        82251 root          1  52   20 17000K  2568K wait    2   8:13   0.00% sh
        41035 root          1  20    0 14504K  2308K select  1   7:41   0.00% syslogd
        71571 root          5  20    0 19108K  2376K accept  2   7:38   0.00% dpinger
        23780 root          1  20    0 14408K  1952K select  3   4:51   0.00% powerd
        40446 root          1  20    0 21036K  5200K select  3   3:39   0.00% miniupnpd
        71407 root          1  20    0 30140K 17968K select  3   2:52   0.00% ntpd
        25379 root          1  20    0 39136K  7360K kqread  3   2:51   0.00% nginx
        25596 root          1  20    0 39136K  7524K kqread  0   1:53   0.00% nginx
          269 root          1  20    0   262M 25140K kqread  0   1:51   0.00% php-fpm
        90245 dhcpd         1  20    0 24812K 13748K select  3   1:33   0.00% dhcpd
         5966 root          1  20    0 50312K  6924K select  0   1:09   0.00% mpd5
        93112 root         10  20    0 52660K  3584K uwait   1   0:16   0.00% filterdns
        
        

        What is pkg and why does that seem to occasionally take CPU resources ?
        Thanks

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Disable the upgrade checks on dashboard (and remove the packages widget if it's there).

          1 Reply Last reply Reply Quote 0
          • T
            TomT
            last edited by

            Thanks I've disabled the update checks.
            Only things left are System Information, Interfaces, Service Status, Interface Statistics and IPSec.

            I'll see how that goes.

            Thanks

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