Just update the entire BOINC package. Don't bother with the certificate file edit when the entire new package just works. BOINC version 7.16.20

https://boinc.berkeley.edu/download_all.php

There is nothing wrong with any of the projects if you just fix the BOINC client in the first place.

My client is up-to-date, but I haven't gotten any jobs from GPUGrid in a very, very long time. I've tried resetting the project, removing and re-adding it, etc. with no luck. In my GPUGrid settings here on the website, I'm enabled to get any task from any project type.

My other projects are getting tasks. Rosetta stopped, but that's because it apparently wants VirtualBox now, but I don't want to install that version of BOINC w/ VB.

OS: Windows 10 64-bit
BOINC: 7.16.20 (x64)

Are there just no projects right now other than the Python beta? Is said beta Linux only?

Are there just no projects right now other than the Python beta? Is said beta Linux only?

your assumption is correct; unfortunately :-(

Obviously, they now concentrate only on Python beta, so no ACEMD tasks; I am afraid it will go like this for a while :-(

That's fine. At least I know it's not just me. :)

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.

Has this trashing of results finally been resolved after months?
I have stopped contributing with the RTX 3080 (and all other cards) until this is fixed.

Michael.

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.

NET::ERR_CERT_DATE_INVALID
Subject: www.ps3grid.net
Issuer: R3
Expires on: 2021. nov. 27.
Current date: 2021. nov. 28.
I can reach the forum only through http.
All of my hosts are set to https, they can't reach the servers because the certificate has expired.

GPUGRID | Scheduler request failed: SSL peer certificate or SSH remote key was not OK

Please fix it as soon as possible.
It could take days, or even weeks, so I've suspended GPUGrid on my hosts.

Is there a way to make boinc overlook certificate problems? S

NET::ERR_CERT_DATE_INVALID
Subject: www.ps3grid.net
Issuer: R3
Expires on: 2021. nov. 27.
Current date: 2021. nov. 28.
I can reach the forum only through http.
All of my hosts are set to https, they can't reach the servers because the certificate has expired.

GPUGRID | Scheduler request failed: SSL peer certificate or SSH remote key was not OK

Please fix it as soon as possible.
It could take days, or even weeks, so I've suspended GPUGrid on my hosts.

New tasks cannot be downloaded either :-(

It also prevents the upload of completed work:

28/11/2021 08:51:47 | GPUGRID | [http] [ID#27114] Info: TLSv1.2 (OUT), TLS alert, certificate expired (557):
28/11/2021 08:51:47 | GPUGRID | [http] [ID#27114] Info: SSL certificate problem: certificate has expired
28/11/2021 08:51:47 | GPUGRID | [http] HTTP error: SSL peer certificate or SSH remote key was not OK
28/11/2021 08:51:48 | GPUGRID | Temporarily failed upload of e1s741_0-ADRIA_BanditGPCR_APJ_b0-0-1-RND2532_5_10: transient HTTP error
28/11/2021 08:51:48 | GPUGRID | Backing off 00:07:19 on upload of e1s741_0-ADRIA_BanditGPCR_APJ_b0-0-1-RND2532_5_10

Post here when it is fixed
I have subscribed.

I have managed (slowly, carefully) to upload and report completed tasks, by editing the urls in client_state.xml

And I have also managed (even more slowly, even more carefully, and with an error on the first attempt) to download and run new work.

But it's not for the faint-hearted: please restore normal service as soon as possible!

I have managed (slowly, carefully) to upload and report completed tasks, by editing the urls in client_state.xml

If you change project url from secure HTTPS to unsecure HTTP, it's wise to beforehand change authentication key( <authenticator></authenticator> ) in account_www.gpugrid.net.xml to weak account key( https://gpugrid.net/weak_auth.php ) to prevent account abuse if http traffic will be sniffed by someone.

Richard wrote:

And I have also managed (even more slowly, even more carefully, and with an error on the first attempt) to download and run new work.

oh, I see, so this was you :-)
I was wondering how come that in on the project status page, the number of unsent tasks was slightly decreasing.

But it's not for the faint-hearted: please restore normal service as soon as possible!

I am out after only a couple of days. It was fun while it lasted.

I have managed (slowly, carefully) to upload and report completed tasks, by editing the urls in client_state.xml

Thank you, Richard, once more time.
Guided by your clue, I uploaded all my finished tasks without losing their deserved bonus.
But I reverted everything to https, and I'm waiting for the problem to be solved on project's side before downloading new work.
Weekend, bad moment for the Informatics on duty at a University to be aware to solve emerged problems...
(We usually think of infrastructure maintenance staff as being omnipresent, but surely they also need to take their weekly rest to recharge energy :-)

I have managed (slowly, carefully) to upload and report completed tasks, by editing the urls in client_state.xml

And I have also managed (even more slowly, even more carefully, and with an error on the first attempt) to download and run new work.

But it's not for the faint-hearted: please restore normal service as soon as possible!

Hello Richard,
I have try your proposal (editing)
I found my pending upload WU, but still problem ! Now Transiant (CA error disapeared)But still unable to report.
Like you say, it is a possible solution. But very long.
More and more there are problems with this project.
Thank you for all your informations.
Best regards

Since then, I've posted full details of the basic technique in message 57912, and possible reasons for the failure to report in message 57930.

Both are in the Stuck on 'uploading' thread, Server and website area. Read the whole thread for context.

Just tried the trick but it did not work. Can't get past 24 hour backoff.

deleted

deleted