We are experiencing multiple issues, e.g. hitting an undocumented upload size limit, and others. Please be patient.

https://blog.hubspot.com/website/413-request-entity-too-large?

Thanks :)

---

We are experiencing multiple issues, e.g. hitting an undocumented upload size limit, and others. Please be patient.

Have you tried file compression, or splitting the large file into multiple pieces that will be combined after they are unloaded?

Is this project still going? I rarely get work units anymore.

https://blog.hubspot.com/website/413-request-entity-too-large?

And another:

Thu 30 Sep 2021 17:11:04 BST | GPUGRID | Started upload of e2s116_e1s44p0f981-ADRIA_AdB_KIXCMYB_HIP-0-2-RND2716_2_9
Thu 30 Sep 2021 17:11:05 BST | GPUGRID | [http] [ID#7007] Received header from server: Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_auth_gssapi/1.3.1 mod_auth_kerb/5.4 mod_fcgid/2.3.9 PHP/5.4.16 mod_wsgi/3.4 Python/2.7.5
Thu 30 Sep 2021 17:11:05 BST | GPUGRID | [http] [ID#7007] Sent header to server: Content-Length: 540810054
Thu 30 Sep 2021 17:11:06 BST | GPUGRID | [http] [ID#7007] Received header from server: HTTP/1.1 413 Request Entity Too Large

Task 32645986

You'll need to re-configure Apache.

+1 can't upload 27079276

i'm getting peer certificates cannot be authticated with given CA certificates.

---

Also seeing message:
9/30/2021 10:55:06 AM | GPUGRID | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates

That message jogged a memory.
Could it be another license expiry like last year about this time?

---

"Together we crunch
To check out a hunch
And wish all our credit
Could just buy us lunch"

Piasa Tribe - Illini Nation

I doubt it - the licence expiry related to the science application (ACEMD), and the Peer certificate relates to https internet traffic.

But I've just dealt with a Peer certificate error reported for two other projects, on the BOINC web site. So something might be brewing.

Lo and behold, I've got

30/09/2021 18:09:14 | GPUGRID | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates

on this machine, and I've got a task just 7.5% short of finishing. Alarm bells are starting to ring.

Nope. Not that issue. I already pinged Toni about the license renewal.
He said this year it is not his responsibility.

Went back through my BOINC logs and my GPUGrid scheduler connections have been working fine and normal.

Wonder what is different with your two hosts?

1) This problem only started happening today - I'll try to find a start time.
2) It only affects Windows hosts - Linux is not affected.

Hourly contact at 14:21 today was good, failed at 15:22 - times are British, UTC+1

I do see the same issue on my Windows host as well. Just happened a few hours ago.

Edit: Adding the project on a Win machine via the BOINC manager also temporarily fails.

If the project is using LetsEncrypt, then apparently there's some fairly widespread issues with that at the moment.

Turned out that an expired https certificate was the culprit. Workarounds as suggested on the main BOINC or WUprop forum worked fine and behavior is back to normal for me.

For Windows:
- make a backup from "C:\Program Files\BOINC\ca-bundle.crt"
- open it as administrator in an editor
it is a text file
- delete "DST Root CA X3" until "-----END CERTIFICATE-----"
- restart boinc
the needed "ISRG Root X1" is already contained


see https://boinc.berkeley.edu/forum_thread.php?id=14413
and https://letsencrypt.org/certificates/

---

I just tried this on one of my hosts and the upload started up right away.

I copied the edited ca-bundle file to another system and that seems to work too.

Need to go through the rest of them and copy the updated file now.

Seems an instance of https://it.slashdot.org/story/21/10/02/2318202/millions-experience-browser-problems-after-long-anticipated-expiration-of-lets-encrypt-certificate

Yes - and the Windows version on BOINC wasn't ready to handle it. The secondary problem was BOINC's continued use of an old version of OpenSSL, long deprecated.

There's some hope of an emergency release of a replacement Windows client within (possibly) 24 hours. I've also been kicking some butt at GitHub, and I've extracted a sort-of promise that there will be an improved version of BOINC across all platforms by mid-December.