There is something going on with the project, unable to upload or download any new or completed wu's

See that milkyway-new.cs.rpi.edu is not resolving to an IP?
;milkyway-new.cs.rpi.edu. IN A

added line to hosts to map the milkyway.cs.rpi.edu to -new
128.113.126.54 milkyway-new.cs.rpi.edu

And that allowed complete work unit to be uploaded.

Don't know if a new update needs to be done??

We have changed the DNS setting such that milkyway-new no longer exists and the url milkyway.cs.rpi.edu points directly to the server IP and is not longer a cname for the server.
I am going through and changing everything on the server to reflect that change.

Marcin wrote:

another issue to report!
I am getting hostname resolution errors now:
[code]34852: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Sending scheduler request: To report completed tasks.
34853: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Reporting 1 completed tasks
34854: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Not requesting tasks: don't need (job cache full)
34855: 19-Nov-2023 11:13:42 (low) [] Project communication failed: attempting access to reference site
34856: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Scheduler request failed: Couldn't resolve host name

[quote]It seems that I can eliminate the issue locally in the client by shutting down the client, removing the <scheduler_url>url</scheduler_url> line from client_state.xml, and restarting the client. But that's just a workaround of course, the real fix needs to happen on the server.

I hadn’t been paying attention for a while—seems my iMac hasn’t done any work since June. Is there any point to remaining attached to this project, or is it the end of the road?

I don't see anything (official) on website where the correct URL is.

It appears Kevin needs to let Willy @ BAM! know what the correct URL is because it's not pointing to it.

I posted to the thread in the number crunching but apparently that info hasn't been relayed over...

I'm on WIndows 10 with latest BOINC client and can't get any work.

Go to your preferences and enable tasks for Milkyway@home N-Body Simulation

Respectfully
Bill F

Nbody was checked on both main and work preferences. The only thing not checked was run other applications on work. I checked it, saved it and tried it again...

First try, I had a moment and smacked myself for not turning work fetch on...

Second try client requested work, but didn't get any:

[11/15/23 7:26:44 PM | Milkyway@home | [sched_op] CPU work request: 34560.00 seconds; 1.00 devices
11/15/23 7:26:47 PM |  | Project communication failed: attempting access to reference site
11/15/23 7:26:47 PM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Server version 721
11/15/23 7:26:47 PM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/
11/15/23 7:26:47 PM | Milkyway@home | No tasks sent
11/15/23 7:26:47 PM | Milkyway@home | Project requested delay of 91 seconds
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Deferring communication for 00:01:31
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Reason: requested by project
11/15/23 7:26:48 PM |  | Internet access OK - project servers may be temporarily down.

It did an auto-try a couple mins later and failed to get any work again.

As mentioned by others, credit stats export is not working yet. I am not sure where 3rd party sites (free-dc, boincstats, …) got their stats files from before the maintenance downtime. But at least the expected place http://milkyway.cs.rpi.edu/milkyway/stats/ (or https, or/and milkyway-new if you will) is empty.

This should be working now (at least the stats seem to be in the directory). Let me know if there is still an issue with stats.

Well, it worked! Went to “simple view”, deleted Milky Way. Then I added it back in. Said that I was an existing user, just like as if I got a new computer. Sure enough, I got 1 task, then a whole bunch of them. So a couple of questions, do I need to do this to all my machines? If so, should I do it now, or wait until they finish up the work units that they have? Thanks everyone for the help. Angie

How do I even remove the project? In the BOINC client under the projects tab the remove button is greyed out for me for this project?

Did you select the MilkyWay Project on the list first?

A 2nd question is why would you? If you are done crunching just set it to no new tasks and then suspend it as well, no communications between your Boinc and the Project will happen again until you unsuspend the Project. The Admin said that changing because of the "-new" address is not needed because they are linking to both the site with the "-new" as well as the site witout the "-new".

1. Yes, I have the project selected

2. I thought earlier they asked to remove and re-add the project? I missed the other message. In the BOINC client it still says "Milkyway@home: Notice from BOINC
This project seems to have changed its URL. When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/"

How do I even remove the project? In the BOINC client under the projects tab the remove button is greyed out for me for this project?

It's definitely certificate related on my Linux Docker.
Running this command on my mac works, but on my container it returns an error.

curl https://milkyway-new.cs.rpi.edu/milkyway/get_project_config.php -v

Results on Docker:

root@84d5ad767049:/tmp/certs# curl https://milkyway.cs.rpi.edu/milkyway/get_project_config.php -v
*   Trying 128.113.126.54:443...
* Connected to milkyway.cs.rpi.edu (128.113.126.54) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

The root CA is in my ca-certificates.crt file, so I am not sure what is going on yet.

Seems my previous user data wasn´t migrated correctly.
On the "old" website I can still log on with my current user data. But on milkyway-new....... it seems my account isn´t there.....

I´d appreciate your assistance....

Thanks,
Joachim from Germany

It’s that time of year again where I startup a number of new machines using BOINC, where I’m OK with the additional ambient heating. I installed BOINC on a machine that has an Intel motherboard GPU (Raptor Lake-H/P/PX 80/96E) and a 13th gen Intel Core i7-13700H CPU (more issues in another thread).

The problem is this… Milkway will NOT download work units if any non-Intel GPU’s are selected in the preferences. Disabling GPU work units in the Milkway preferences does NOT help.

The work-around was to remove check marks from both Nvidea and AMD GPU’s and then reconnect and download CPU work units. This is OK for now but more functionality is needed for my other machines that do have Nvidea GPU’s. Ideally, this would be handled with separate preferences by specific machine. Unfortunately, this does not seem to be an available option in BOINC.

Thank you for everyone working on the connection issue with MilkyWay@home. I have a couple Boinc processes happening on Linux (ubuntu, ubuntu server) and they are all experiencing the same issue. I removed the MilkyWay@home connection, tried to reconnect (or add new project), and I have tried with both the -new address and the old one. All attempts result in "Failed to connect, try again later". I am aware of the issue with certificates, and I am patient in waiting for the solution.

Someone on our Discord Server asked if there was a problem connecting and I gave them a link to this thread.

I look forward to a solution and I am willing to try to connect whenever you want to try to see if a solution works.

Cheers and keep up the good work.

Yes I did
sudo update-ca-certificates
yields no updates

The client, in fact, all of Boinc, is installed by the package manager. Latest version. I even reinstalled it.

opeSuse Linux Tumbleweed
bpinc 7.24.1 x64
I deleted the milkyway project and changed the url to add -new, i also did an update-ca-certificates
but I still can not add the project. in each case i shutdown boinc and restarted it - nothing fixed the issue for me
Someone mentioned adding 2 certs but, where do they go and what name do i give them?
Is it going to fix this?

[---] Fetching configuration file from https://milkyway-new.cs.rpi.edu/milkyway/get_project_config.php
[---] Project communication failed: attempting access to reference site
[---] Internet access OK - project servers may be temporarily down.

Does anyone have a working answer to this problem ? If so, I would love to hear it.

Hello,
As you all know, it has become necessary to delete MW and then add it back on all you machines. So far, I have done this on 3 machines of various versions of Windows without any problems. However, I have been trying to get my linux machine to add it back and it keeps giving me the error,

Fri 03 Nov 2023 07:04:20 PM EDT | | Fetching configuration file from https://milkyway.cs.rpi.edu/milkyway/get_project_config.php
Fri 03 Nov 2023 07:04:21 PM EDT | | Project communication failed: attempting access to reference site
Fri 03 Nov 2023 07:04:22 PM EDT | | Internet access OK - project servers may be temporarily down.

Is there something wrong with MW or is it something else? I've tried it several times over the last couple of hours.
Thanks,
Allen

PS oh ya, it also says, Failed to add, try again later.
Also, on Boinc Tasks, it says Error-184

That url does not work on Linux Mint.
It does not even get to the login screen.

Quote:

There is no new version of BOINC Manager available for download.

There is no version to update according to my client. Am I supposed to have some secret signal?[/img]