Why does Squid3 work for a while and then stop?

Question

linux

Hello.
I downloaded Squid3 on Debian (via sudo apt-get install squid3) to create a caching proxy server, and, accordingly, to speed up the loading of php scripts for a site on the MediaWiki engine.
I tried to do everything according to the documentation from the official site , from there I took the config for squid.conf.
Actually, here it is:

http_port 207.142.131.205:80 transparent vhost defaultsite=oecumene.wiki
cache_peer 127.0.0.1 parent 80 3130 originserver
acl manager proto cache_object
acl localhost src 127.0.0.1/32
acl web_ports port 80
http_access allow web_ports
http_access allow manager localhost
http_access deny manager
acl purge method PURGE
http_access allow purge localhost
http_access deny purge
http_access deny all

The problem is that the first run of squid went without any errors. There were no errors in the cache.log either.
But for no apparent reason, squid just stopped working, and the site loading speed also decreased. There was nothing like that in cache.log.
Nothing changed after the restart, but squid issued a few warnings:

[email protected]:~$ sudo service squid3 restart
[sudo] password for sadaffairs:
[ ok ] Restarting Squid HTTP Proxy 3.x: squid3[....]  Waiting.....................done.
2017/03/14 16:07:18| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1'
2017/03/14 16:07:18| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable
2017/03/14 16:07:18| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost'
2017/03/14 16:07:18| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1'
2017/03/14 16:07:18| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable
2017/03/14 16:07:18| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost'

And a suspicious line also appeared in cache.log:

2017/03/14 16:07:18| commBind: Cannot bind socket FD 15 to 207.142.131.205:80: (99) Cannot assign requested address

Now I just can't figure out why squid worked without errors for a while and then stopped? How should squid.conf be modified to fix these errors?

Answer 1

I'm probably showing off... but, IMHO, installing squid for acceleration is the last century.
There is nginx for such things. And the setup is much easier and caches with a bang.
And on business - at you squid tries to be hooked on the 80th port, but it is already occupied by someone.