From the Operational Status tab on Jurisica's Lab page (you know where to look): "BOINC scheduler and uploads are projected to be up Monday, September 29th, 2025".

That doesn't look like a 'promise'. To me, it sounds as an expectation.

Adri

> so I don't know if we can call this "progress" when we change the error message to a new one...

Actually this seems like a great progress. In fact the previous message "HTTP service unavailable" was telling us that no server were answering this request. While the new one "Error 403" tells us that the server answered us but we do not have the correct credentials. So at least the service is up. But authentication is probably broken on this endpoint.

As a technical user, I would love a post-mortem on this migration in order to understand what went wrong. In fact we often hear about success stories but rarely about failures. And in this case there is probably a lot to learn.

I hope you will be able to resolve the remaining issues in the upcoming week. Even though you owe us nothing, World Community Grid is one of the sole medicine project on BOINC with constant work units, as an end user it is kind of frustrating not being able to contribute to research on this field.

I've been checking daily, including today (9/30/25) and the servers are not responding. All my tasks are still "uploading" or "ready to report' with the "Scheduler request pending" message.

The Web site seems to be up for about a week but work cannot be reported or scheduled.

Hi Paul try https://www.cs.toronto.edu/~juris/jlab/wcg.html go to tab operational status at right. Otherwise, UnixChick has a good status page at https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,47541 - 1st post is the status. - Ian

Short simple version. They are closer, but things are still messed up.

Gemini translates it to this:

The technology team is experiencing several problems with the science cluster.

Key Issues
Software Problems: There are issues with the WAS container configuration and the BOINC daemon builds. This means some of the core software isn't working correctly.

Storage Access: A significant problem is that a portion of the science nodes (one-sixth of them) cannot access the /science filesystem.

Permission Blocks: The team also lacks the necessary permissions to add the IP address to the NFS share, which is preventing them from mounting the file system on the affected nodes.

These issues are hindering the full functionality of the cluster and preventing some nodes from performing certain tasks. While the problems aren't currently stopping all work, they are a blocker for using those specific nodes for particular roles until the NFS share can be properly mounted.

Which for us means:
What it means for you: 💻
Your tasks might not run: The WAS container configuration and BOINC daemon builds are essential for running certain tasks. If they're not working, your jobs might fail or not start.

Some nodes are unavailable: A portion of the cluster's nodes can't access a critical data storage area (/science filesystem). This means your work cannot be scheduled on these specific nodes.

Slower performance: With some nodes out of commission, the overall workload will be distributed among fewer machines. This could lead to longer wait times for your jobs to complete.

In short, the team is working on problems that could directly affect the availability and performance of the cluster you rely on. Your tasks might be stuck or slower until they fix the issues.

And because of this it is still Error 403
which would be these two issues:

Incorrect Permissions: The file or directory you're trying to access has specific permissions that restrict who can view it. Your account may not be on the list of approved users.

Missing Index File: In some cases, a server is configured to prevent directory listings. If you try to access a directory without a default homepage (like index.html), it can return a 403 error instead of showing the file list.