Very simple, it can't even find that (http(s)) server because you have a typo in your URL or a DNS error...

And why would those 4xx error codes be grouped under "Client response codes"?
In that case, any 4xx error source if totally irrelvant, as the error code returned for failing download in the BOINC client is a "503 Service unavailable"...

Ralf

Does anyone have issues with downloading again?

Currently my boinc has 4 hour backoff.


It has error:

scheduler request faile. couldn't resolve hist name
internet access ok - project servers may be temporarily down

Yes, yes, yes.

And the issues seem to have reappeared since ARP has started up again - surely not just a coincidence. I'm set up to NOT accept ARP WUs but I'm getting them anyway and they have recurrent download problems !! Even worse is the fact that all my other downloads (OPN and MCM) are also now similarly infected with the problem whereas, before ARP restarted, all downloads were running just fine.

Please, please, please scrub ARP totally till things are sorted.

No point in cancelling tasks, it’s a problem at the server end and nothing to do with the specific task trying to download.

This is the normal process. After 4 download failures all others go on pending.
You must click on the "Tools" menu then on "Retry pending transfers" to reactivate them all.
Or create a cron task to do it for you with "/usr/bin/boinccmd --network_available" with a delay from 10sec if you have no fear to 15min if you are a little shy thing.