• Traffic Graph Issue

    1
    0 Votes
    1 Posts
    705 Views
    No one has replied
  • Moving Rules on iOS

    6
    0 Votes
    6 Posts
    1k Views
    K
    You made my day. Thank you very much.
  • Monitoring (RRD) graphs have bugs

    20
    0 Votes
    20 Posts
    6k Views
    D
    https://github.com/pfsense/FreeBSD-ports/pull/432
  • Prevent webGUI from binding on WAN interface - Oh, the horror

    14
    0 Votes
    14 Posts
    2k Views
    S
    I was thinking about that, too. I can't explain it why I could see the management interface before from a public IP despite this apparent interception of packets. I frequently disconnect my phone from WiFi and use it to test how my IP appears from the open internet. I'm fairly confident that I didn't forget to turn off WiFi when I noticed that the admin interface was available via WAN.  Also, other threads on this forum corroborate that the management interface binds on all Interfaces. Seems like a security problem to me, but no one other than the OPs seems to care in those other threads. Rather than fighting pfsense, the easier path is to just move the management ports (as our testy friend suggested) and keep them blocked rather than doing something risky and more complex like trying to keep the standard ports but not binding on certain interfaces. Getting back to the mystery of how some packets are intercepted before hitting my firewall and some aren't.  I wouldn't put it past a cable provider or cable modem manufacturer to be interfering with my connection, maybe even in intermittent ways.  I will know more after I set my reverse proxy back up after tearing it down thinking it was somehow interfering with critical aspects of the firewall.
  • Unable to retrieve package information

    3
    0 Votes
    3 Posts
    1k Views
    F
    Was temporary down it seems, all good now.
  • WAN disabled, no WebGUI on OPT1

    1
    0 Votes
    1 Posts
    467 Views
    No one has replied
  • [SOLVED] NET::ERR_CERT_COMMON_NAME_INVALID in Chrome with new Certificate

    10
    0 Votes
    10 Posts
    78k Views
    K
    @robatwork: @kpa: If you happened to have a self-signed certificate that was created before the change linked below the newer browsers definitely didn't like it because they now require the FQDN of the system in the SubjectAltName field of the certificate. Which is where we came in  :) I don't think I will start any arguments about whether Chrome is an upstart baby browser or fully mature 9 year old browser which eclipses all other browsers by market share I meant newer versions of the mainstream browsers, not any of the completely new browsers or new forks of the existing ones. Chrome did what they had to with the validation requirements, hence the issue.
  • Pfsense returns to default certificate after reboot.

    2
    0 Votes
    2 Posts
    598 Views
    jimpJ
    With a cluster, the certificates are shared between both nodes. If you import a cert for the secondary directly on the secondary it will be overwritten by the certs from the primary during the next config sync. You can do two things: 1. Use a single certificate to cover both nodes (SANs include hostnames for primary, secondary, and a hostname for the CARP VIP for other purposes, or perhaps a wildcard cert) and then select this for use as the GUI cert on both nodes. This is simple with ACME and the way we usually recommend doing it. 2. Import the primary and secondary GUI certs to the primary node, so they will be synchronized to both units. Then pick the certificate in the GUI settings after that.
  • 0 Votes
    7 Posts
    1k Views
    M
    Ok it seems nginx IS running and 'netstat -l -p tcp-a -n|grep 80' confirms this. I had some mark values in my routing and tried ping's -m but that route is for tcp. Ping -r for ignoring routing did not work. Sincerely, JC Magras
  • Webgui keeps dying

    11
    0 Votes
    11 Posts
    1k Views
    M
    MY problem( just ahead of yours in list) shows nothing when 'ps ax| grep nginx' !  Et tu?
  • How to translate the keyword "System" in the system language pack

    6
    0 Votes
    6 Posts
    1k Views
    D
    Good. Just for illustration, you really can break this with anything; e.g. here I replaced the string "NTP" with "NTP Lets Break This" in /usr/local/www/status_logs_common.inc, resulting in: [image: brokentabs.png]
  • 0 Votes
    6 Posts
    987 Views
    jimpJ
    That is dangerously incorrect. There is more to HTTPS than encryption when used properly.
  • Adding user adds the user…but not really - Missing from User Manager

    4
    0 Votes
    4 Posts
    705 Views
    D
    Do a fresh install and stop messing with /etc/passwd.
  • Maybe a bug in status_interfaces.php or other include file

    2
    0 Votes
    2 Posts
    653 Views
    P
    A first simple override of the up/down for disabled interfaces: https://github.com/pfsense/pfsense/pull/3820 but perhaps there is more that can be done underneath to actually find out the hardware state even when at the pfSense software level the interface is disabled.
  • AD users SSH connection not working

    6
    0 Votes
    6 Posts
    2k Views
    jimpJ
    It's not on anyone's radar or to-do list that I'm aware of.
  • MOVED: [HOWTO] Squid/Lightsquid Logs with MAC addresses - pfSense 2.3.2

    Locked
    1
    0 Votes
    1 Posts
    666 Views
    No one has replied
  • States Summary 504 Timeout

    1
    0 Votes
    1 Posts
    507 Views
    No one has replied
  • Bug in webgui under services -> dncp server -> Domain Search List

    2
    0 Votes
    2 Posts
    517 Views
    jimpJ
    Looking at the backend code of the page, and the GUI, it will accept either space or ; as a separator and they both work. Be sure when using ; that you don't use both a space and a ;. So either: "example.com movie.edu" OR: "example.com;movie.edu"
  • Rearrange Interfaces

    5
    0 Votes
    5 Posts
    1k Views
    jahonixJ
    PS: RRD graphs are a bit irritating now, that's absolutely correct. Since that's data from the past I can live with it.
  • Route edit does not reflect original

    2
    0 Votes
    2 Posts
    488 Views
    P
    That was a general problem due in many places in the UI to a js change. It should be fixed in recent builds by: https://github.com/pfsense/pfsense/commit/a7c47d85270fcf8c784e6af61ea2fd09f9d4f5ac related issue https://redmine.pfsense.org/issues/7625
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.