After Upgrade to 17.7.8 Proxy is not starting

Started by PotatoCarl, November 22, 2017, 06:00:38 PM

Previous topic - Next topic
Hi

I just updated from 17.7.7 to 17.7.8 and found that the Squid WebProxy is shown as "stopped". It will not start and I do not find any reason for that.

Strangely enough, some of the webpages still work, others don't.

I have configured the proxy as transparent proxy.

I only found one message that made sense to me:
kid1| FD 14, 127.0.0.1 [Stopped, reason:Listener socket closed job826385]: (53) Software caused connection abort

Any help how to get it going?

Thank you.

BR

Okay, found the problem. In the squid config a bungled hostname was found ("x.x.x..x"). No idea how it got there. Anyhow, I removed it from command line (where I could see this error message when trying to invoke "squid") and look there, it starts again.

A manual hostname or from a remote list?


Cheers,
Franco

One hostname in the "Banned Host List".
My old Squid Conf did exclude the whole network, but whitlisted a few. This does not seem to work as I cannot enter in the GUI 192.168.1.0-192.168.1.255 for example. So instead I work with "banned" lists.
Actually I would love to have a better gui which makes use of more SQUID options, so that I can control the access to the outside world more fine granulated. E.g. I would like to have specific allow lists for some hosts, etc.

Ok, you can open feature requests over at GitHub and people there will take up your suggestions based on need and time:

https://github.com/opnsense/core/issues


Cheers,
Franco