Hi all,
I'm wondering why I don't see the option for "Web Proxy" under Services... I see the following:
Captive Portal
Snsmasq DNS
Intrusion Detection
ISC DHCPv4
ISC DHCPv6
Kea DHCP [new]
monit
Network Time
OpenDNS
Unbound DNS
Since 24.1 its a plugin. Search for os-squid and install it.
awesome thanks!
is there another way to install it offline? my opnsense is not connected to internet
I had a similar issue, and what worked for me was adjusting the rule order under Firewall → NAT since OPNsense can sometimes hit another rule before the one you're setting. Also, if you're testing with Mobile Proxies (https://infatica.io/mobile-proxies/), make sure you're matching the correct IP ranges and not hitting unexpected blocks or redirects. For some mobile IPs, I had to add more specific allow rules.
I need help, I installed Squid Proxy ON OPNSENSE 25.1.6_2, but when starting the psquid service it displays the following error.
Segmentation fault
Starting squid.
CPU Usage: 0.006 seconds = 0.000 user + 0.006 sys
Maximum Resident Size: 32 KB
Page faults with physical i/o: 0
2025/05/09 10:11:08| Processing Configuration File: /usr/local/etc/squid/squid.conf (depth 0)
2025/05/09 10:11:08| WARNING: empty ACL: acl bump_nobumpsites ssl::server_name "/usr/local/etc/squid/nobumpsites.acl"
2025/05/09 10:11:08| Not currently OK to rewrite swap log.
2025/05/09 10:11:08| storeDirWriteCleanLogs: Operation aborted.
2025/05/09 10:11:08| FATAL: Unable to find configuration file: /usr/local/etc/squid/pre-auth/*.conf: (13) Permission denied
2025/05/09 10:11:08| Squid Cache (Version 6.12): Terminated abnormally.
/usr/local/etc/rc.d/squid: WARNING: failed to start squid
I've hit permission errors like this before when setting up Squid on OPNsense. In my case, I copied over the config files manually, but forgot to check file ownership and permissions, which caused squid to fail on startup. Once I adjusted the permissions (making sure everything under /usr/local/etc/squid/ was owned by the correct user and readable), it started up fine. Sometimes the permission denied issue pops up if you restore a config backup from another machine or after upgrading.
If you're handling proxies and access for multiple networks or large data projects, I've found that reliable tools for smart proxy handling can make these issues less frequent. I first heard about solutions like this while researching CrawlBase (https://crawlbase.com/), which had some details on troubleshooting proxy configs and secure access.