Switch to using SSL (Secure Socket Layer)

Message boards : News : Switch to using SSL (Secure Socket Layer)

To post messages, you must log in.

Previous · 1 . . . 6 · 7 · 8 · 9

AuthorMessage
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 904
Credit: 10,364,290
RAC: 4,453
Message 97228 - Posted: 4 Jun 2020, 20:26:55 UTC - in response to Message 97218.  
Last modified: 4 Jun 2020, 20:28:55 UTC

Hello there,

I wasn't getting any downloads or uploads to work so I read the post about reattaching to https://boinc.bakerlab.org/rosetta. I removed Rosetta @ Home and tried to add the project again. If I select it from the menu or copy and paste the new URL in and click on next it gives me the error message "Failed to add project. Try again later.".

Are others having this issue? Am I doing something wrong?

Thanks for any thoughts.

What operating system does your computer use?

For most versions of Windows, you'll need to shut down BOINC, upgrade BOINC to 7.16.7, and then start the new version.

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

Some of the older versions of Windows won't allow installing that version of BOINC, and therefore don't have a fix available yet.
ID: 97228 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
jjhunt

Send message
Joined: 25 Nov 14
Posts: 2
Credit: 4,202,918
RAC: 1,202
Message 97289 - Posted: 8 Jun 2020, 15:49:37 UTC - in response to Message 97228.  

Window 7. Good news! I uninstalled BOINC and re-installed it and I can now attach to Rosetta and got a work unit so I'm up and running again. Thanks so much to all for the good advice.
ID: 97289 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Logan

Send message
Joined: 8 Oct 08
Posts: 1
Credit: 3,363,725
RAC: 2,172
Message 97296 - Posted: 9 Jun 2020, 3:55:49 UTC

I can't attach via BOINC for Android v. 7.4.53 on a Samsung Galaxy S9. HTTP Debug log:


Client Messages

Mon Jun 08 23:48:09 EDT 2020||Internet access OK - project servers may be temporarily down.
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Info:  Connection #3 to host www.google.com left intact
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server:
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Set-Cookie: NID=204=o_IONoAupPOO_lgYqKh8Sj3Fp6fVnzWAserodhHdHW_ZQe-0X8QxeEstEO5zlem16YB8KusQ2eXlC81ScCopI9oXPwysi1gt1XFF0QfNt1cwJMwwPyODGWTAS2HbtJX2t1l8GC3iE4YMhNIw96YgI2OrEYlctk99m2TJNsr-DY8; expires=Wed, 09-Dec-2020 03:48:10 GMT; path=/; domain=.google.com; HttpOnly
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Set-Cookie: 1P_JAR=2020-06-09-03; expires=Thu, 09-Jul-2020 03:48:10 GMT; path=/; domain=.google.com; Secure
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: X-Frame-Options: SAMEORIGIN
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: X-XSS-Protection: 0
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Content-Length: 5270
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Server: gws
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Content-Encoding: gzip
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Content-Type: text/html; charset=ISO-8859-1
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Cache-Control: private, max-age=0
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Expires: -1
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: Date: Tue, 09 Jun 2020 03:48:10 GMT
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Received header from server: HTTP/1.1 200 OK
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server:
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: Accept: */*
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: User-Agent: BOINC client (aarch64-android-linux-gnu 7.4.53)
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: Host: www.google.com
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Sent header to server: GET / HTTP/1.1
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Info:  Connected to www.google.com (2607:f8b0:4002:c06::63) port 80 (#3)
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Info:  Re-using existing connection! (#3) with host www.google.com
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#0] Info:  Found bundle for host www.google.com: 0x7addeccb40 [can pipeline]
Mon Jun 08 23:48:08 EDT 2020||[http] HTTP_OP::init_get(): http://www.google.com/
Mon Jun 08 23:48:08 EDT 2020||Project communication failed: attempting access to reference site
Mon Jun 08 23:48:08 EDT 2020||[http] HTTP error: Peer certificate cannot be authenticated with given CA certificates
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (OUT), TLS alert, Client hello (1):
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  Closing connection 12
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  SSL certificate problem: unable to get local issuer certificate
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (OUT), TLS alert, Server hello (2):
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Mon Jun 08 23:48:08 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (IN), TLS handshake, Server hello (2):
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (OUT), TLS handshake, Client hello (1):
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  TLSv1.2 (OUT), TLS header, Certificate Status (22):
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:    CApath: none
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:    CAfile: ca-bundle.crt
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  successfully set certificate verify locations:
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  ALPN, offering http/1.1
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  Connected to boinc.bakerlab.org (2607:4000:406::160:156) port 443 (#12)
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:    Trying 2607:4000:406::160:156...
Mon Jun 08 23:48:07 EDT 2020||[http] [ID#2] Info:  Hostname boinc.bakerlab.org was found in DNS cache
Mon Jun 08 23:48:07 EDT 2020||[http] HTTP_OP::init_get(): https://boinc.bakerlab.org/rosetta/get_project_config.php
Mon Jun 08 23:48:07 EDT 2020||Fetching configuration file from https://boinc.bakerlab.org/rosetta/get_project_config.php
Mon Jun 08 23:48:07 EDT 2020||Internet access OK - project servers may be temporarily down.
Mon Jun 08 23:48:06 EDT 2020||[http] [ID#0] Info:  Connection #3 to host www.google.com left intact
Mon Jun 08 23:48:06 EDT 2020||[http] [ID#0] Received header from server:
Mon Jun 08 23:48:06 EDT 2020||[http] [ID#0] Received header from server: Set-Cookie: NID=204=vj2JphR10SLwVd-rU8-XYMQp58Oet2OGsn6yGlw5Ixx54pSQfSJohTp1vDFjvuxb9kJKt_jrncbrottYcFNVrIPCEda2AMMBigbFVzvE-EE8Z85Q8fSH4Ob_Y-C1ys9fwcCtvNUPmRoaarB925WjGOu2Q9cpvbH7aniYJL2iyI8; expires=Wed, 09-Dec-2020 03:48:08 GMT; path=/; domain=.google.com; HttpOnly
ID: 97296 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Bill F
Avatar

Send message
Joined: 29 Jan 08
Posts: 25
Credit: 765,759
RAC: 754
Message 97297 - Posted: 9 Jun 2020, 4:12:04 UTC - in response to Message 97296.  

Android version v. 7.4.53 has a Certificate issue in it and it can not connect with Rosetta ( and a few other projects). The BOINC programmers started working last week to recompile 7.4.53 with the current Certificates and post for user upgrade. Hang in there lots of people affected,

Bill F
ID: 97297 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Peter Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 237
Credit: 2,511,883
RAC: 24,509
Message 97306 - Posted: 9 Jun 2020, 13:55:38 UTC - in response to Message 97297.  

Android version v. 7.4.53 has a Certificate issue in it and it can not connect with Rosetta ( and a few other projects). The BOINC programmers started working last week to recompile 7.4.53 with the current Certificates and post for user upgrade. Hang in there lots of people affected,

Bill F


Why use 7.4.53 when 7.16.3 has been released? You're running an out of date version. 7.16.3 is working fine for Rosetta and LHC on my Android 7.0 and Android 4.5 phones.
ID: 97306 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 904
Credit: 10,364,290
RAC: 4,453
Message 97307 - Posted: 9 Jun 2020, 14:16:21 UTC - in response to Message 97306.  

Android version v. 7.4.53 has a Certificate issue in it and it can not connect with Rosetta ( and a few other projects). The BOINC programmers started working last week to recompile 7.4.53 with the current Certificates and post for user upgrade. Hang in there lots of people affected,

Bill F


Why use 7.4.53 when 7.16.3 has been released? You're running an out of date version. 7.16.3 is working fine for Rosetta and LHC on my Android 7.0 and Android 4.5 phones.

Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

https://boinc.berkeley.edu/download_all.php
ID: 97307 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Peter Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 237
Credit: 2,511,883
RAC: 24,509
Message 97309 - Posted: 9 Jun 2020, 14:38:34 UTC - in response to Message 97307.  
Last modified: 9 Jun 2020, 14:38:57 UTC

Android version v. 7.4.53 has a Certificate issue in it and it can not connect with Rosetta ( and a few other projects). The BOINC programmers started working last week to recompile 7.4.53 with the current Certificates and post for user upgrade. Hang in there lots of people affected,

Bill F


Why use 7.4.53 when 7.16.3 has been released? You're running an out of date version. 7.16.3 is working fine for Rosetta and LHC on my Android 7.0 and Android 4.5 phones.

Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

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


Why on earth would you say I haven't noticed? I can read you know. I always use beta versions of everything, never had a problem. And in this case it's certainly miles better than the "official" one, which is clearly not working at all for this project! You can't get worse than no connection can you? I've also been running 7.16.5 (no idea why they actually went backwards in version numbers) for a couple of months.
ID: 97309 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Keith Myers
Avatar

Send message
Joined: 29 Mar 20
Posts: 57
Credit: 54,908
RAC: 343
Message 97310 - Posted: 9 Jun 2020, 16:09:55 UTC - in response to Message 97307.  


Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

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

Gawd, I wish they would remove any labels of beta or development from the BOINC releases. Causes more confusion than anything. Any release at the BOINC site is perfectly functional and ready to use. The only thing different from a "development" version from an "official" version is that it could be in a state of flux where they might be still changing it with minor updates. But it functions just as well as the "official" version, better in fact usually, as all the pending bugfixes have been applied since the last "official" release.
I can think of only one instance recently where the "development" version was bad or non-functional and it was pulled in a matter of hours once the testers reported an issue that was somehow undiscovered in beta testing.
ID: 97310 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Peter Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 237
Credit: 2,511,883
RAC: 24,509
Message 97311 - Posted: 9 Jun 2020, 16:22:29 UTC - in response to Message 97310.  
Last modified: 9 Jun 2020, 16:22:44 UTC


Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

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

Gawd, I wish they would remove any labels of beta or development from the BOINC releases. Causes more confusion than anything. Any release at the BOINC site is perfectly functional and ready to use. The only thing different from a "development" version from an "official" version is that it could be in a state of flux where they might be still changing it with minor updates. But it functions just as well as the "official" version, better in fact usually, as all the pending bugfixes have been applied since the last "official" release.
I can think of only one instance recently where the "development" version was bad or non-functional and it was pulled in a matter of hours once the testers reported an issue that was somehow undiscovered in beta testing.


Indeed.

This is the same with any software from anyone. Official releases can have bugs too. I just ignore the word beta and download whatever has the highest version number.

Even people who believe the beta could be more buggy, shouldn't they be helping out Boinc by finding those bugs? Somebody has to. And with the current SSL problem, the beta is the best choice anyway! I'll take a possible minor bug over one I know will stop my project running.

At the end of the day, my phone works. It's doing Rosetta. Without the beta Rosetta doesn't get work done. Easy choice for me to make.
ID: 97311 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1316
Credit: 24,249,761
RAC: 12,118
Message 97314 - Posted: 10 Jun 2020, 8:05:16 UTC - in response to Message 97311.  

Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

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

Gawd, I wish they would remove any labels of beta or development from the BOINC releases. Causes more confusion than anything. Any release at the BOINC site is perfectly functional and ready to use. The only thing different from a "development" version from an "official" version is that it could be in a state of flux where they might be still changing it with minor updates. But it functions just as well as the "official" version, better in fact usually, as all the pending bugfixes have been applied since the last "official" release.
I can think of only one instance recently where the "development" version was bad or non-functional and it was pulled in a matter of hours once the testers reported an issue that was somehow undiscovered in beta testing.

Indeed.

This is the same with any software from anyone. Official releases can have bugs too. I just ignore the word beta and download whatever has the highest version number.

Even people who believe the beta could be more buggy, shouldn't they be helping out Boinc by finding those bugs? Somebody has to. And with the current SSL problem, the beta is the best choice anyway! I'll take a possible minor bug over one I know will stop my project running.

At the end of the day, my phone works. It's doing Rosetta. Without the beta Rosetta doesn't get work done. Easy choice for me to make.

Well...

Following my Boinc Android problems, I downgraded from 7.16.3 and reinstalled 7.14.53. Unfortunately, it's incapable of adding Rosetta as a project.
Returned to 7.16.3 and added Rosetta fine, grabbed some tasks (before adjusting my settings, so it downloaded too many - sigh) and then got exactly the problems reported here - a state of perpetual download, never completing, nothing to run.

Not that this is a problem, because the issue I had was that either Boinc got knocked out of memory or it wouldn't run as a background task, so that nothing ran over the course of the entire 3-day deadline, they timed out and got sent to someone else. Disastrous.

And then I did a little more searching and discovered the Boinc Android FAQ which finally explains why my Android 9 phone runs like a proverbial sack of brown stuff. Nothing to do with Samsungs, as snidely suggested, but because Boinc Android is beyond any and all hope. Thus explaining why it seemed to run ok on my old Samsung.

So if you're running Rosetta at all, be grateful. Whatever you do, learn from me, don't try to change anything because you'll lose everything.

I've now re-added WCG successfully, grabbed some tasks and it seems to be running.
And I've taken advice from that Android FAQ above and tried to make the changes it suggests so Boinc doesn't run so badly or drop out.

Good grief...
ID: 97314 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Peter Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 237
Credit: 2,511,883
RAC: 24,509
Message 97320 - Posted: 10 Jun 2020, 11:53:28 UTC - in response to Message 97314.  

Looks like you haven't noticed that the BOINC download site still describes 7.16.3 as a possibly unstable development version. It appears to need more testing and reporting the results of those tests before it is officially released.

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

Gawd, I wish they would remove any labels of beta or development from the BOINC releases. Causes more confusion than anything. Any release at the BOINC site is perfectly functional and ready to use. The only thing different from a "development" version from an "official" version is that it could be in a state of flux where they might be still changing it with minor updates. But it functions just as well as the "official" version, better in fact usually, as all the pending bugfixes have been applied since the last "official" release.
I can think of only one instance recently where the "development" version was bad or non-functional and it was pulled in a matter of hours once the testers reported an issue that was somehow undiscovered in beta testing.

Indeed.

This is the same with any software from anyone. Official releases can have bugs too. I just ignore the word beta and download whatever has the highest version number.

Even people who believe the beta could be more buggy, shouldn't they be helping out Boinc by finding those bugs? Somebody has to. And with the current SSL problem, the beta is the best choice anyway! I'll take a possible minor bug over one I know will stop my project running.

At the end of the day, my phone works. It's doing Rosetta. Without the beta Rosetta doesn't get work done. Easy choice for me to make.

Well...

Following my Boinc Android problems, I downgraded from 7.16.3 and reinstalled 7.14.53. Unfortunately, it's incapable of adding Rosetta as a project.
Returned to 7.16.3 and added Rosetta fine, grabbed some tasks (before adjusting my settings, so it downloaded too many - sigh) and then got exactly the problems reported here - a state of perpetual download, never completing, nothing to run.

Not that this is a problem, because the issue I had was that either Boinc got knocked out of memory or it wouldn't run as a background task, so that nothing ran over the course of the entire 3-day deadline, they timed out and got sent to someone else. Disastrous.

And then I did a little more searching and discovered the Boinc Android FAQ which finally explains why my Android 9 phone runs like a proverbial sack of brown stuff. Nothing to do with Samsungs, as snidely suggested, but because Boinc Android is beyond any and all hope. Thus explaining why it seemed to run ok on my old Samsung.

So if you're running Rosetta at all, be grateful. Whatever you do, learn from me, don't try to change anything because you'll lose everything.

I've now re-added WCG successfully, grabbed some tasks and it seems to be running.
And I've taken advice from that Android FAQ above and tried to make the changes it suggests so Boinc doesn't run so badly or drop out.

Good grief...


Ouch, looks like Android 9 is to blame then, shutting off something because it's in the background? Don't they know what multitasking is? Glad I got a cheaper phone (6 months ago) with Android 7. Android is quite odd in that the higher number versions come with more expensive phones. Whereas with a PC, you don't get Windows XP because you bought a budget machine. Oh well, I guess you just have to fiddle about or try different projects until it's happy. And if I were you I'd report that as an OS bug to Google.
ID: 97320 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
bunnybooboo

Send message
Joined: 15 Apr 20
Posts: 8
Credit: 66,579
RAC: 446
Message 97322 - Posted: 10 Jun 2020, 12:20:12 UTC - in response to Message 97314.  
Last modified: 10 Jun 2020, 12:29:32 UTC

Sid, I'm also on Android 9 and have tweaked my setting above the defaults described here in that post you linked to. Reflects how I had it set and fully operational under v7.4.53 before this security certificate issue.

In relation to the FAQ's I'm not entirely certain that issue regarding BOINC running in the background is still relevant. At least using v7.16.3 under Android 9 (V30b-234-30), when navigating to Settings >> General >> Apps & Notifications >> App info >> BOINC >> Data usage - it appears that "Background data" is by default toggled ON. As I've been unable to attach to Rosetta in a refreshed v7.4.53 I can't ascertain if this is change in those BOINC version jumps. If so, then the FAQ's will need updating to reflect this improvement on Play Store version jump.

EDIT: Using the settings changes I mention I previously have been able to use BOINC throughout the day and night, running in the background, rarely causing issues with other apps like YouTube, and utilising the battery instead of only when attached to a charger. Will update if I observe problems.
ID: 97322 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1316
Credit: 24,249,761
RAC: 12,118
Message 97361 - Posted: 13 Jun 2020, 13:15:36 UTC - in response to Message 97322.  

Sid, I'm also on Android 9 and have tweaked my setting above the defaults described here in that post you linked to. Reflects how I had it set and fully operational under v7.4.53 before this security certificate issue.

In relation to the FAQ's I'm not entirely certain that issue regarding BOINC running in the background is still relevant. At least using v7.16.3 under Android 9 (V30b-234-30), when navigating to Settings >> General >> Apps & Notifications >> App info >> BOINC >> Data usage - it appears that "Background data" is by default toggled ON. As I've been unable to attach to Rosetta in a refreshed v7.4.53 I can't ascertain if this is change in those BOINC version jumps. If so, then the FAQ's will need updating to reflect this improvement on Play Store version jump.

EDIT: Using the settings changes I mention I previously have been able to use BOINC throughout the day and night, running in the background, rarely causing issues with other apps like YouTube, and utilising the battery instead of only when attached to a charger. Will update if I observe problems.

Thanks for your efforts. My settings compared to yours are:

Deselected "Pause computation when screen is on" - same
"Power sources for computation" Selected "Battery" - same
"Used CPU cores" selected "3" (The device has 4) - selected 2 (device has 8)
"Pause CPU usage above" selected "70%" - same
"RAM limit" selected "60%" - 70%

So I think I've selected fewer tasks in a larger proportion of RAM - using 7.16.3 as well.
My phone is a Samsung S8 using Android 9 (I don't know where you've picked up that other version detail from, but I'm fully updated)

I've found that setting for Boinc data usage (after a struggle) and "Allow background data usage" is also on.
I had another setting below it "Allow app while Data saver on" which was off, which I've now turned on - maybe that will help

I only have WCG running (which also stops after a short time). I'll monitor if that performs any better first.
So very tiresome...
ID: 97361 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
mauro flores

Send message
Joined: 29 Mar 18
Posts: 1
Credit: 135,063
RAC: 10
Message 97468 - Posted: 19 Jun 2020, 20:06:35 UTC

Copio y pego la nueva SSL en mi ordenador, pero no me funciona.
ID: 97468 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Falconet

Send message
Joined: 9 Mar 09
Posts: 61
Credit: 190,072
RAC: 886
Message 97469 - Posted: 19 Jun 2020, 20:32:50 UTC - in response to Message 97468.  

Copio y pego la nueva SSL en mi ordenador, pero no me funciona.


Instala de nuevo: https://boinc.berkeley.edu/download.php
ID: 97469 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Yavanius

Send message
Joined: 29 Dec 18
Posts: 5
Credit: 19,301
RAC: 11
Message 97473 - Posted: 20 Jun 2020, 5:24:47 UTC - in response to Message 95768.  

I'm still looking for this in linux flavours.

I'm afraid to touch /var/ xxx etc too far

bad outcomes



The latest BOINC version can be found at this PPA:

https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

(Visit the link, don't just add that URL)

Gianfranco maintains BOINC for Debian/Ubuntu. No need to wait for the latest version to get added to your Linux distro archives.

~Yavanius
ID: 97473 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
jackielan2000

Send message
Joined: 5 Sep 06
Posts: 13
Credit: 10,939
RAC: 1
Message 97475 - Posted: 20 Jun 2020, 18:20:55 UTC - in response to Message 95682.  

We updated our project to use SSL. The project URL has thus been changed to https://boinc.bakerlab.org/rosetta. You can reattach the project using this updated URL at your convenience. Please post any issues regarding this update in the discussion thread.

The link doesn't work with my Android phone. BOINC version is 7.4.53. Do I need to download a new version?
ID: 97475 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Peter Hucker
Avatar

Send message
Joined: 12 Aug 06
Posts: 237
Credit: 2,511,883
RAC: 24,509
Message 97476 - Posted: 20 Jun 2020, 18:26:37 UTC - in response to Message 97475.  

We updated our project to use SSL. The project URL has thus been changed to https://boinc.bakerlab.org/rosetta. You can reattach the project using this updated URL at your convenience. Please post any issues regarding this update in the discussion thread.

The link doesn't work with my Android phone. BOINC version is 7.4.53. Do I need to download a new version?


Yes, at the bottom of this page: https://boinc.berkeley.edu/download_all.php
Or direct link: https://boinc.berkeley.edu/dl/boinc_7.16.3.apk
Doesn't seem to be updated on Google Play yet.
ID: 97476 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 . . . 6 · 7 · 8 · 9

Message boards : News : Switch to using SSL (Secure Socket Layer)



©2020 University of Washington
https://www.bakerlab.org