• Upgrading on Proxmox KVM from 2.3.2 to 2.3.2_1 kills Disk Image

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • 2.3.2-p1 amd64 ntopng resets

    2
    0 Votes
    2 Posts
    2k Views
    R
    If I go to DIAGNOSTICS / ntopng Settings / Access ntopng, I can accept the certificate and enter ntopng. From DIAGNOSTICS / ntopng, I get a reset. the https: is missing in the DIANGOSTICS / ntopng item link. I am using port 3000.
  • Error installing squid pkg

    4
    0 Votes
    4 Posts
    1k Views
    S
    Perhaps try this related solution which fixes a few things: https://forum.pfsense.org/index.php?topic=119290.0 Let me know if it solves your issue.
  • 2.3.1_1 update with crash and error [solved]

    11
    0 Votes
    11 Posts
    5k Views
    w0wW
    Updated 2.3.2 to 2.3.2_1 and got the same error. Solution is the same. But… what is wrong?
  • Error upgrading from 2.3.2 to 2.3.2_1

    9
    0 Votes
    9 Posts
    3k Views
    O
    Update finished successfully: >>> Setting secondary partition as active... done. Upgrade is complete.  Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense_wrap... done. Success Thanks!
  • MOVED: Upgrading from 2.3.2 -> 2.3.2-p1 - DNS Resolver service failed

    Locked
    1
    0 Votes
    1 Posts
    583 Views
    No one has replied
  • Upgrading 1.2.3 to 2.3.2 - XMLRPC Sync not working

    5
    0 Votes
    5 Posts
    1k Views
    dotdashD
    I'd try wiping the secondary and setting it up from scratch. You just have to get the basic settings done and sync it.
  • I can't get internet access on my LAN

    1
    0 Votes
    1 Posts
    621 Views
    No one has replied
  • Upgrading from 2.3.2 -> 2.3.2-p1 issue - fetching packages times out

    19
    0 Votes
    19 Posts
    3k Views
    P
    Seems like the pfsense package repositories are struggling with the load.  Have you considered putting Cloudflare in front of it?  It could cache all the packages for you and serve them from the global CDN.
  • Cant update to 2.3.2-p1

    1
    0 Votes
    1 Posts
    966 Views
    No one has replied
  • HP install stuck at BTX loader

    3
    0 Votes
    3 Posts
    1k Views
    M
    This isn't specific to PFSense. I think it is a FreeBSD issue. I had the same problem on a 6005 and DC5850. Ended up using something Intel instead.
  • Pfsense on freebsd

    5
    0 Votes
    5 Posts
    5k Views
    W
    Transip runs KVM for it's VPS-es and has pfsense available as an install option. Don't know of any other provider doing this. Maybe some others let you install your own ISO though.
  • UNABLE TO INSTALL Pfense on BLANK SATA 2 DRIVE

    2
    0 Votes
    2 Posts
    910 Views
    pttP
    @muhammadanish: Hi I am trying to fresh install on SATA HARDDISK Version: pfSense-CE-2.3.2-RELEASE-2g-i386-nanobsd-vga Please Check/Read:  https://www.pfsense.org/download/  (Pick Your Platform) Pick Your Platform USB Memstick Installer The USB memstick image is meant to be written to disc before use and includes an installer that installs pfSense software to the hard drive on your system. This is the preferred means of running pfSense software. The entire hard drive will be overwritten, dual booting with another OS is not supported. The USB memstick file is named pfSense-memstick-2.3.2-RELEASE-arch.img.gz. where arch is i386 or amd64, depending on the CPU architecture of your system. **Embedded (NanoBSD) The embedded version is meant to be written to disc before use and is specifically tailored for use with any hardware using flash memory (mostly Compact Flash) rather than a hard drive.** Flash memory can only handle a limited number of writes, so the embedded version runs read only from flash, with read/write file systems as RAM disks. The NanoBSD platform has two OS slices and a config slice. One OS slice is used to boot from, the other is used for upgrades, and the config slice is where the configuration resides is held separately. There are two variations of the NanoBSD platform: The default version which uses a serial console, and another that supports using a VGA console. Each of those variations also comes sized for different sizes of storage media. The filename for NanoBSD downloads is laid out as follows: pfSense-2.3.2-RELEASE-size-arch-nanobsd.img.gz. In that filename, size can be one of 1g, 2g, or 4g. The arch, as above is for i386 or amd64. The nanobsd part can is either nanobsd for serial console, or nanobsd_vga for the VGA-enabled version.
  • Cloning 2.1 to 2.3

    3
    0 Votes
    3 Posts
    887 Views
    DerelictD
    Try it. It will work fine. Particularly so if the interface names do not change. Not sure where you read that you cannot load a 2.1.X config onto 2.3.2.
  • Virtual Web Server

    7
    0 Votes
    7 Posts
    2k Views
    T
    Ok so figured out how to get this done with HAProxy.  I like it.  Thank you.
  • 2.3.1_1 and just got another 502 error

    7
    0 Votes
    7 Posts
    2k Views
    A
    Same here, using the IPSec widget on the dashboard causes PHP-FPM to die after a random amount of time. Removing it from the dashboard for now…
  • Bypass boot prompts

    3
    0 Votes
    3 Posts
    3k Views
    O
    Tried manually adjusting the xml via the console, but no luck. Adjusted the config via the Web Gui to make the interface hn0. Saved, powered down. Uploaded the new VHD and bingo, all good now. Thanks for the pointer.
  • Pfsense Installation

    2
    0 Votes
    2 Posts
    783 Views
    KOMK
    Is pfSense LAN set for DHCP?  Do you have a DHCP server on LAN to serve it an address?
  • 2.3, No Update Available

    2
    0 Votes
    2 Posts
    806 Views
    jimpJ
    What size CF card do those have? (Check the dashboard) Probably they have a CF card size that is no longer offered due to size limits. Only 2GB and 4GB CF cards work currently.
  • AD Integration to Pfsense (With NTLM Authentication)

    4
    0 Votes
    4 Posts
    6k Views
    C
    Winbind will, somehow, encapsulate LDAP requests, although with some side effects (due to caching if I understand well) especially with group membership. This said, rather than looking for "how to", why not explaining more in detail what works and what doesn't in your configuration? I believe it will be much more efficient than asking for yet another documentation that you will follow but which may not fix issue you're facing.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.