[Solved]trasparent proxy blocks all Squid+Squidguardian
-
hello again, no, I am building wpad now, but before I opened other thread the proxy were working fine, but suddenly I saw this error "connection error" while surfing on webpages. After that I opened other thread. But now I'm configuring WPAD. The thing I wonder is why the proxy worked fine and after few mins blocked all.
-
Check cache.log and see if it says anything. Usually, if squid is working it stays working. I've never seen a case where it's working ok and then just stops.
-
2016-03-02 21:35:32 [55408] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:35:32 [55408] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:35:32 [55408] logfile not allowed in acl other than default
2016-03-02 21:35:32 [56028] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:35:32 [56028] New setting: logdir: /var/squidGuard/log
2016-03-02 21:35:32 [56028] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:35:32 [56028] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:35:32 [56028] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:35:32 [56028] logfile not allowed in acl other than default
2016/03/02 21:36:45| pinger: Initialising ICMP pinger …
2016/03/02 21:37:42| pinger: Initialising ICMP pinger ...
2016-03-02 21:37:42 [94873] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [94873] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [94873] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [94873] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [94873] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [94873] logfile not allowed in acl other than default
2016-03-02 21:37:42 [95578] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [95578] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [95578] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [95578] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [95578] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [95578] logfile not allowed in acl other than default
2016-03-02 21:37:42 [95149] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [95149] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [95149] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [95149] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [95149] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [95149] logfile not allowed in acl other than default
2016-03-02 21:37:42 [97094] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [97094] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [97094] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [97094] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [97094] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [97094] logfile not allowed in acl other than default
2016-03-02 21:37:42 [98564] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [98564] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [98564] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [98564] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [98564] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [98564] logfile not allowed in acl other than default
2016-03-02 21:37:42 [96431] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [96431] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [96431] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [96431] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [96431] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [96431] logfile not allowed in acl other than default
2016-03-02 21:37:42 [99344] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [99344] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [99344] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [99344] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [99344] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [99344] logfile not allowed in acl other than default
2016-03-02 21:37:42 [97402] /usr/local/bin/squidGuard: can't write to logfile /var/log/squidGuard/squidGuard.log
2016-03-02 21:37:42 [97402] New setting: logdir: /var/squidGuard/log
2016-03-02 21:37:42 [97402] New setting: dbhome: /var/db/squidGuard
2016-03-02 21:37:42 [97402] init domainlist /var/db/squidGuard/SmrtBrdAllwdLnks/domains
2016-03-02 21:37:42 [97402] loading dbfile /var/db/squidGuard/SmrtBrdAllwdLnks/domains.db
2016-03-02 21:37:42 [97402] logfile not allowed in acl other than default
2016/03/02 21:43:30| pinger: Initialising ICMP pinger …
2016/03/02 21:43:33| pinger: Initialising ICMP pinger ... -
OK, you didn't mention squidGuard is involved. Disable squidGuard and see if the problem persists. To disable squidGuard, you must uncheck the Enable checkbox, then click Save, then click Apply (very important do it it this way or your changes won't work). Then try to access a website.
-
I have already done that. But yes it does, I even uninstalled squidguard but still persists.
-
Do you get an error in your browser or does it just timeout? Anything at all in squid's realtime view? Please post some screenshots of your squid General config page.
-
I'll after school ended.
-
Like you sai din your PM to me, you might be better off nuking everything and starting fresh. It doesn't take much time to factory reset and reconfigure.
-
The problem is here I have done alot of settings here and creating them from start is gonna be pain
-
Which version of pfsense is good x64 or x86?
-
x64. You can make a config.xml backup of your settings and exclude any packages via Diagnostics - Backup/Restore.
-
I made a clean install and configured all of the settings again. Now it's fresh and works perfect. But still thinking that should I set WDAP? I use arp table and am thinking that is WDAP still needs to set up ?
-
ARP and ARP table have nothing to do with WPAD. If you only have a few network clients that don't change, manual proxy config is best. If you have a dynamic network then WPAD will help some of those clients find the proxy by themselves. Other clients (like Android) will still need to be configured manually.
-
Thank you for helping me, btw I have found what is interfering with https rules. I created a limiter rule on in rules and when I activated it the rules causes to time-out of surfing and proxy works fine when I disabled the limiter rule.
-
There is an issue with limiters in conjunction with squid, if I remember right.
-
Maybe, but now I have figured out that the issue I was dealing with had happened because of the limiter. I formatted for nothing but a clean and fresh install afterall. Atleast I learnt something.
