23.01 Squid issue
-
@hugoeyng dang I thought maybe you could do the rename .old trick and after revert the patched version back once it installs. Path under edit file would be /usr/local open the file and rename the name and resave it
-
The Patch seems to be working fine for my 2100-MAX it even caught a new virus with HTTPS intercept. Clam AV normalized. "VIRUS FOUND"
-
@jonathanlee the heart of the matter is that the error occurs during the installation and it is not possible to apply a patch before installing.
After the error during the instalattion squidGuard is actually not installed and not be able to start as a service, even the patch is applied. Is something like "sitllborn".
-
@hugoeyng have you attempted a firmware reinstall, My system had the firmware reinstalled before the package install. With 23.01 update
-
@jonathanlee In my case pfSense run on a PC, so I think a firmware update do not apply for me.
-
@hugoeyng do you have access to Virtualization software?
-
@jonathanlee like what?
-
@hugoeyng Firmware, in this case, is the pfSense 'firmware'.
-
@rcoleman-netgate sorry for my lack of knowledge. I installed pfSense on a personal computer that uses its own firmaware. So, what other firmware should I update?
-
@hugoeyng I believe they're suggesting reinstallation of pfSense but you'll have to ask @JonathanLee
-
@rcoleman-netgate Hmmm ... I got It. I think that is insane to reinstall pfSense as a solution to a package of pfSense to work.
Also, I think that even I reinstall pfSense will no solve the root of this question: squidGuard package will not install correctly while they do not correct the bug that causes this issue.
-
@hugoeyng reinstall software is considered 'firmware' in PfSense Netgate models
-
@hugoeyng Hypervisor, VirtualBox, VMware? Anything that you can spin up a machine you can load PfSense on to test without using your real equipment. They create a virtualized machine that you can install software on to test with. Windows 10-11 pro the software under features enable Hypervisor-V, Virtual box is free it's made by Oracle, VMware costs money. I recommend just using Hyper-V in Windows, it's really simple to use create a blank Virtual machine and load the software like you would on a normal machine it runs in a virtualized environment and you can test save snapshots test again and if you find something that works and doesn't have issues, repeat it with the real hardware. If you have access to a VM you can test it with a clean install, the reason is maybe your configuration is bonked up. You can test it outside the machine this way. I like virtual box too I use to use it with Palm Pre
https://www.ceos3c.com/pfsense/install-pfsense-on-virtualbox/
-
@jonathanlee A better guide is here: https://docs.netgate.com/pfsense/en/latest/virtualization/index.html
-
@hugoeyng said in 23.01 Squid issue:
I think that is insane to reinstall pfSense as a solution to a package of pfSense to work.
Yeah, that really should never be required. It looks like some part of the install/deinstall script is failing there. Since that doesn't happen for most people it's probably something in the config that already exists.
-
@stephenw10 What config would you bet on, since I've already uninstalled and reinstalled both Squid and SquidGuard.
In my point of view, the problem is that the squidguard.conf comes with the installation of SquiGuard and it is this "bugged" squidguard.conf that prevents the correct installation of the package.
Once the installation failed, changing the squidguard.conf doesn't solve it anymore, even applying the proposed patch.
The first question to fix is making SquidGuard appear in the menu and in the list of services, even stopped (red 'x' icon). If that happens, I guess the patch could solve the initial bug, about what this post discusses.
-
@stephenw10 I agree, a blank install and no user config should fix it. After apply the patches and once that is done put the config back on.
-
The package install script is hitting some php error and failing before it has added the require menu and service items into the main pfSense config.
Usually when I've seen that it's because the system has been upgraded and the php versions mismatch. But as I understand it that shouldn't be the case here? -
@stephenw10 Remember this was the same issue I had and it turned out I had to resave the reverse proxy to get it to stop. With that being said I thought maybe there is a different configuration item bonked up with his settings that is missing.
-
That issue prevented you making a config change in Squid but it did not prevent installing/uninstalling AFAIK.
