The error log says "blah... transient http error".

That is exactly when you should activate http_debug logging - that's what it's there for.

It will give you details, including what sort of transient error it was.

01/06/2020 21:25:15 | | BOINC can't access Internet - check network connection or proxy configuration.

I, obviously, can.

<edit>
I have just had a TNGrid unit finish, and upload without issue. I keep seeing BOINC can't access the net.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I've managed to edit and save the BOINC APK, using APK Editor version 1.8.20, but when I try to install my modified APK, I get a warning that the app exists.

I still have a few WCG tasks in progress, and 1 other LHC, apart from the stuck reports.
I'm going to wait until these are finished before I try again.

I'm hoping that LHC can fix things on the server, or BOINC can release an official update for Android, before my LHC results expire.

I'm currently looking into a way of editing the BOINC APK file. If I succeed, I will post a workaround on this forum.

As far as I can see from Github the developers there are in the process of releasing a new 7.4.53, perhaps with the adjusted certificates file. They run into different difficulties though.

---

Thanks Jord.
I have joined GitHub, but I haven't posted there yet.
I don't fully understand how GitHub works, is there a Welcome area for New Users ?
I've just found https://guides.github.com/activities/hello-world/

Look in https://github.com/BOINC/boinc/issues though (for any and all Android issues)

---

01/06/2020 21:25:15 | | BOINC can't access Internet - check network connection or proxy configuration.

That's not a debug message - we all see that from time to time.

Enable DEBUG logging to see WHY it failed.

I noticed that credits from one of my affected projects hadn't been added to my account at BOINCstats. Willy has confirmed that the same certificate expiry had prevented him collecting the exported credit stats from the affected projects.

Willy's site is working again now (https://www.boincstats.com/forum/5/12516,1), and I've written to the stats mailing list, but please check your own stats totals on your own preferred stats aggregation site, and tell the operator if you find a problem.

BOINCstats did miss yesterday’s update from Rosetta but managed to pick it up today and update twice so we should be all square.

I've seen that Android error before when trying to install a 32bit APK over a newer 64bit version of the same app.

I think many APKs now contain both 32bit and 64bit code, but the 64bit version will be installed in preference to 32.

Google require that all new apps uploaded to Google Play store after 1 August 2019 must support 64bit.

https://play.google.com/store/apps/details?id=sk.styk.martin.apkanalyzer should be able to tell you.

I don't want to use beta versions or versions from other source than Play Store.
Please, update the official apk (it's 4 years old)

Update to 7.16.7 seems to have worked. My transfer list is cleared. I don't think I've ever seem it that big before! I'll role the update out on my other systems as I come to them.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Hi, domain berkeley.edu is using expired intermediate certificate (root). You can check it here:
https://www.ssllabs.com/ssltest/analyze.html?d=berkeley.edu&hideResults=on
Expired 30 May 2020.
Update the expired certificate on the server.

They know: https://calnetweb.berkeley.edu/calnet-technologists/incommon-sectigo-certificate-service/addtrust-external-root-expiration-may-2020

---

It doesn't look like that much, considering that they have old certificates on the server for berkeley.edu/berkeley.org. But OK :-)

No connections to projects because of this issue.
Well, seems BOINC doesn't need my computing power anymore, ok.

EDIT: BTW, why nothing in BOINC notices about this issue?
They so verbose with different junk, but when REALLY user attention required they are silent! WTF!

---

Notices are not for user attention, or things the user needs to change or adjust. They're for news and other non-intrusive messages. No action needed things.

---

No connections to projects because of this issue.
Well, seems BOINC doesn't need my computing power anymore, ok.

EDIT: BTW, why nothing in BOINC notices about this issue?
They so verbose with different junk, but when REALLY user attention required they are silent! WTF!

Are you still having problems with this on any projects ?

LHC has updated the server https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5441&postid=42767#42767
Rosetta has also fixed the issue https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14006
I'm only aware of one other affected project. https://numberfields.asu.edu/NumberFields/forum_thread.php?id=460

Are there still any projects that are having problems ?