Nick Howitt wrote:

So you are saying both start correctly, but browsing fails?

That is what it looks like
After a reboot some pages work and some don’t. I can not figure out what is the reason some are blocked.

So you are saying both start correctly, but browsing fails?

Hi Nick

/usr/lib/systemd/system/dansguardian-av.service lookk sook to my opinion

[Unit]

Description=DansGuardian Content Filter

After=syslog.target network.target squid.service

BindsTo=squid.service

Oct  3 13:03:14 pdebrabander squid[1578]: Squid Parent: will start 1 kids

Oct  3 13:03:14 pdebrabander squid[1578]: Squid Parent: (squid-1) process 1609 started



Oct  3 13:03:20 pdebrabander dansguardian[2956]: Started sucessfully.

The boot order looks good if you look at time of start

Have a look at /usr/lib/systemd/system/squid.service for the proxy and /usr/lib/systemd/system/dansguardian-av.service for the content filter. The content filter is set to require squid to be running and starts squid if it needed. I have a feeling some other issue is at play here. I son't normally use ither and I'm running a test on my microserver which won't finish until the 6th so I can't reboot it until then and that is the machine I test the proxy with.

Can you have a look at your logs and see if anything else is causing it to fail? I don't think the network target in the unit file is meaningful and could possibly be changed to network-online.target. You could try that (or add it) then try rebooting. Otherwise I can't test for a few days.