FYI: I was getting this Permanent Error message on both my Linux Mint computers. Noticed that the automatic updater had 20+ updates for the system. After doing the updates on one of them, about 30 minutes later I was able to get a work unit.

The other machine was still giving the permanent error message. Updated it and was able to get a work unit. Both of them took about 30 minutes or so after the update before it would connect.

I did the same on Ubuntu 24.04. The software updater downloaded a newer version of Boinc and the 403 error is gone.
I don't know if it's a the newer version of Boinc or some other piece of software/library that was updated, but it's worth to try a system update.

What about the others still having Boinc version 7.x? I am also not having any work and after detaching, now indeed I cannot attach to the project.

It is definitely the newer version of Boinc which is needed. The old 7. versions will no longer work here.

Cheers

8.0.4 doesn't work for me on Ubuntu but does work with Fedora 40 and 41.

What I haven't tried is a delete and complete re-install of the same BOINC client. Problem is, I have about 30 projects defined to BOINC and each has an app_config file. I don't want to have to rebuild all of that.

I just updated and restarted Xubuntu 24.04, still get the same error:

57 https://denis.usj.es/denisathome/ 4/13/2025 5:14:55 AM Scheduler list fetch from https://denis.usj.es/denisathome/ failed: permanent HTTP error

It is definitely the newer version of Boinc which is needed. The old 7. versions will no longer work here.

Cheers

At least 1 in this thread has work with 7.20:
https://denis.usj.es/denisathome/forum_thread.php?id=307&postid=2783

8.0.4 does not work for all, see other posts in this thread.
I upgraded Ubuntu LTS from 20.04 with BOINC 7.16.6 to 22.04 with BOINC 7.18.1 then 24.04 with BOINC 7.24 and finally upgraded BOINC to 8.0.4 and NONE work.

It is not clear what causes some to fail and some work, it is not as simple as BOINC version or Linux version.

I wonder if ISP provider is also a factor, I am on Sky.

---

Paul.

It is definitely the newer version of Boinc which is needed. The old 7. versions will no longer work here.

Cheers

it's not that simple. it's a user agent issue in their cloudflare configuration.

newer clients on linux seem to have a better rate of success, most likely because the newer client is using a trusted user agent most times.

but there are cases shown where 7.x.x clients DO work, and cases where 8.0.x DON'T work. so it's not so black and white.

I just updated and restarted Xubuntu 24.04, still get the same error:

57 https://denis.usj.es/denisathome/ 4/13/2025 5:14:55 AM Scheduler list fetch from https://denis.usj.es/denisathome/ failed: permanent HTTP error

I'm on Comcast/Xfinity for ISP.

i dont think ISP has anything to do with it. I have some hosts that connect and some hosts that dont behind the same ISP.

It is definitely the newer version of Boinc which is needed. The old 7. versions will no longer work here.

Cheers

it's not that simple. it's a user agent issue in their cloudflare configuration.

newer clients on linux seem to have a better rate of success, most likely because the newer client is using a trusted user agent most times.

but there are cases shown where 7.x.x clients DO work, and cases where 8.0.x DON'T work. so it's not so black and white.

I stand corrected.
Probably some change the gremlins in charge in Spain made.
Perhaps they will correct it.

Cheers

That is not to say that an update of a BOINC client is bad ... across the years many improvements for both Windows and Linux as well as some MAC's have been implemented in newer versions. Especially on the Windows side. Volunteers running Windows older than 7.24.x should consider 8.0.2

Bill F

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

On my Windows PC that has BOINC 8.02 installed I continue to get no tasks. I recently rebuilt one of my Pies so it has 64 bit Raspberry OS, but if I try to add Denis to Boinc 7.20.5 I get error -224. Looking in the log, the only message relating to this attempt is:

897 14/04/2025 08:52:03 Fetching configuration file from https://denis.usj.es/denisathome/get_project_config.php

I can open this file in a web browser.

On my Windows PC that has BOINC 8.02 installed I continue to get no tasks. I recently rebuilt one of my Pies so it has 64 bit Raspberry OS, but if I try to add Denis to Boinc 7.20.5 I get error -224. Looking in the log, the only message relating to this attempt is:

897 14/04/2025 08:52:03 Fetching configuration file from https://denis.usj.es/denisathome/get_project_config.php

I can open this file in a web browser.

it's the same user agent problem that everyone else has.

Has anyone tried using WINE to run windows BOINC & apps on Linux?

---

Paul.

😂 I love your post! 😆

---

Any update ?

There are many frustrated would be crunchers awaiting a fix.

---

Paul.

All my Windows hosts and also my newer Linux hosts receive a steady flow of work now. Still not possible to attach again to the project.

---

Connected Finally

---

[img]https://stats.free-dc.org/badgesbanner.php?cpid=f78b6e501c0b04a4b25ec91bd1607237[img]

Dear project administrator,
Please take a look at get_project_config.php.

https://denis.usj.es/denisathome/get_project_config.php
https://www.primegrid.com/get_project_config.php
https://lhcathome.cern.ch/lhcathome/get_project_config.php
https://milkyway.cs.rpi.edu/milkyway/get_project_config.php

Denis@Home get_project_config is different from other @home projects.
For example the <platforms> field is empty.

Are you sure the root cause is Cloudflare?
Regards
Paolo

Dear project administrator,
Please take a look at get_project_config.php.

https://denis.usj.es/denisathome/get_project_config.php
https://www.primegrid.com/get_project_config.php
https://lhcathome.cern.ch/lhcathome/get_project_config.php
https://milkyway.cs.rpi.edu/milkyway/get_project_config.php

Denis@Home get_project_config is different from other @home projects.
For example the <platforms> field is empty.

Are you sure the root cause is Cloudflare?
Regards
Paolo

how would this cause it to work fine with new clients but break older clients?

many others have shown that the error messages where it gets stuck in communication is the cloudflare human challenge. it's def a cloudflare based issue.