D2
Local Standard Time UTC -7 hours
Created 11 May 2011, 1:12:24 UTC
Total credit 7,298,273
Average credit 1,361.20
Cross project credit BOINCstats.com Free-DC
CPU type GenuineIntel
Pentium(R) Dual-Core CPU E5400 @ 2.70GHz [Family 6 Model 23 Stepping 10]
Number of processors 2
Coprocessors NVIDIA GeForce GT 430 (1024MB) driver: 320.49 OpenCL: 1.1
Virtualization None
Operating System Microsoft Windows 7
Home Premium x64 Edition, Service Pack 1, (06.01.7601.00)
BOINC version 7.2.42
Memory 6 GB
Cache 2048 K
I brought this old thing back on line last week and it is running Seti just fine.
Einstein was it's back up project and that ran fine for years.
It could not connect to E@H.
I detached from Einstein and tried to reattach, no joy.
As a test I tried attach to asteroids and that went well.
For some reason it can't connect to Einstein, any ideas from the smart people?

Did you check to see if your Einstein account was deleted or marked inactive due to the GDPR laws the were implemented last year? (Submitted on 28 Nov 2018 17:11:05 UTC)

GDPR: NEW WEBSITE FEATURES AND STATISTICS EXPORT OPTION

Well since I'm posting from my daily driver which is an E@H computer exclusively and is getting and processing work 24/7 I would say that is not the case.

Could the URL for Einstein in the old computer be incorrect in account_einstein.phys.uwm.edu.xml file?

Well it worked ~ 2mos ago and on the second hand after I detached it from the project and then tried to reattach I would think Boinc would use the current info.

Anything in the event log about what IS happening? (Or not.)

Anything in the event log about what IS happening? (Or not.)

The event log shows nothing, how ever a clue did pop up when I tried to reattach.
Boinc said

This project is not accepting new accounts

Then it showed my email and asked me to enter my pass word.
which I did so it asked me if I forgot my password.
The bottom line is no joy.

Einstein is pretty hot on respecting the new GDPR European privacy laws.

You're asking (I think) to reconnect to an old account: you shouldn't trigger a 'new account' message. (They might be refusing - still - to accept new accounts via BOINC Manager, unless you're using the latest client which can show you the 'terms of use' page and record your acceptance).

It would help if you could describe exactly how you're trying to make this re-connection: they might have a problem after all the privacy upheavals, but we can't get them to fix it if we don't know exactly what you're doing.

I go to add project in account manager, then I select E@H, this time Boinc manager said,

Failed to add project please try later. Click finish to close.

Event log says:
5/4/2019 4:35:59 PM | | Fetching configuration file from http://einstein.phys.uwm.edu/get_project_config.php
5/4/2019 4:36:04 PM | | Project communication failed: attempting access to reference site
5/4/2019 4:36:07 PM | | Internet access OK - project servers may be temporarily down.
Which is exactly the same message I was getting prior to uninstalling E@H

---

When I paste that url into a browser, I get a perfectly good reply from

https://einsteinathome.org/get_project_config.php

so there's some redirecting going on. Try pasting that url into the address box on the attach page.

Richard no joy there,

it failed to add project

Probably will need to set http_debug in the Event Log logging options. I wonder did Einstein make changes to their security protocols to go along with the GDPR requirements?

Does your browser have the necessary TLS 1.2 or event the latest TLS 1.3 protocols? The logging should give more details about why you can't connect.

5/4/2019 4:36:04 PM | | Project communication failed: attempting access to reference site

That is a clue which means BOINC couldn't even access google.com by the client.

Probably will need to set http_debug in the Event Log logging options.

Great idea but I have no clue how to do that.

Does your browser have the necessary TLS 1.2 or event the latest TLS 1.3 protocols

I don't know but the browser is Chrome

Probably will need to set http_debug in the Event Log logging options.

Great idea but I have no clue how to do that.

Does your browser have the necessary TLS 1.2 or event the latest TLS 1.3 protocols

I don't know but the browser is Chrome

How old is the client? What version?
[Edit] Went back to the OP and see it is the old 7.2.42 client. That is really old and outdated. You really should update to the latest client. There have been a lot of changes regarding security in the client since the days of the 7.2.42 client.

Keith, excellent find, that fixed it.
Thanx

Great news, glad that fixed it. I am constantly surprised that people running clients as old as the 6.10.60 client are still able to interact with any project. Think those are only running the Seti project though. I had a hunch that Einstein with its aggressive stance toward personal information security enforced to be compliant with GDPR rules may have come into play.

I would have liked to have seen what the http_debug output for a connection request would have shown.

Yes, the log would have been conclusive, but never mind.

The security certificate bundle that BOINC uses for https links was updated around v7.10, so the older version could have had that problem.

But

5/4/2019 4:36:04 PM | | Project communication failed: attempting access to reference site
5/4/2019 4:36:07 PM | | Internet access OK - project servers may be temporarily down.

indicates that google.com could be contacted, not as stated. So there's still a query there.

Keith in my 73 years I have learned the hard way that if it ain't broken don't fix it. In this case it was broken.
Once again thanx.

indicates that google.com could be contacted, not as stated. So there's still a query there.

Thanks for the comment Richard, I see that I have been misinterpreting the client responses. I always read each line as the action:response.
Now I see that each line is self-contained, in this case the first line is the response:action of contacting the reference site and the response is in the next line.
Thanks for furthering my understanding of the client.