WARNING, this is going to be a long post.

If you upgraded to the latest BOINC version during the number of hours when Christian had set the URL for BOINC attaching to https://www.worldcommunitygrid.org/ instead of the original http://www.worldcommunitygrid.org/, then the latest recommended version of BOINC has this auto-adjust, already introduced in 7.16.11, which "let a project master URL change from http: to https: without involving the user." So your BOINC may still be attached with HTTPS, if you had the latest version during the period when Christian had set the URL to HTTPS.

A number of hours later Christian decided to flip it back again to HTTP, which WCG has always had, when he cleaned up the config.
Unfortunately though, the auto-adjust function in BOINC does not work the other way around.So, therefore your message in BOINC now likely is "This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/"

So check in the properties of the project (in BOINC) if you are attached with HTTPS. If that's the case, you must detach again, and make sure you attach with http://www.worldcommunitygrid.org/ , and not https. If you are using BOINC manager to attach to the project, make sure to change the URL to HTTP only, because the latest auto-downloaded "all_projects_list.xml" which BOINC use for its list of project, has WCG as a HTTPS project, which they now decided it should not be.

Since this project has no plan to use HTTPS in the URL you attach with, that message will not go away, unless you make sure that you are really attached with HTTP, and not HTTPS.

Post the message you get in BOINC exactly, but I'm almost sure it is:"This project seems to have changed its URL. When convenient, remove the project, then add http://www.worldcommunitygrid.org/"

So, there is a drawback with this auto-adjust, if the project decide to flip back to HTTP from HTTPS.

The same happened to me with my newest recommended version of BOINC. I downloaded and installed v7.16.20. Shortly after I had done that, Christian started configuring the server, and changed the URL to HTTPS. Consequently my new version of BOINC auto-adjusted the HTTP URL I was attached with, to the "new" HTTPS URL, and dropped this line into the BOINC log." Project URL changed from http:// to https://"

Some hours later people started to complain that they were getting "You are attached to this project twice. Please remove projects named World Community Grid, then add https://www.worldcommunitygrid.org/" in their logs, which really is a nonsensical message. Then Christian went on a hunt for that issue, and discovered other places in the config that had the wrong URL-prefix. At that time, he decided to use HTTP again, instead of HTTPS, and I suddenly began to get the message in BOINC about removing the project and attach it with HTTP from the HTTPS setting BOINC had auto-adjusted to. So that's what I did, and now my log is clean from crap again.

So, in this case TPCBF, you are wrong. It is still an issue for people with either newer BOINC versions that auto-adjusted during the hours WCG was using HTTPS, or for those who removed the project, and reattached with the master. erroneous URL, that infested the logs for a while. Both of those types of users, must now manually detach and attach again, and make sure they are using the HTTP address. The BOINC auto-adjust works only from HTTP>HTTPS, and not the other way around. Of course, you can ignore it and live with the message, BOINC will still work normally, but if you want to get rid of the message, you must detach, and attach with the right URL-prefix.

Those who have earlier versions of BOINC, and those who did not follow the erroneous "master." crap that infested the logs for a while, are not affected by this issue. They stayed om the original HTTP WCG address, which we are now back to, and WCG have no intention at least for now, to change it to a HTTPS address.

Good Kirel2

Yes, that is likely, and as I said, the auto-adjust only goes in one direction from HTTP>HTTPS, it can not switch back to HTTP if the project config changes back. I guess the developers thought it unlikely that once you switched to HTTPS, you would switch back again.

Unfortunately as Christian at WCG mentioned, it was never meant that they would change the URL we attach to. He writes: "The bad URL, both the HTTPS and the wonky hostname earlier resulted from config details accidentally copied over from our test environment by our build tools"

So, let's hope that part of all issues are over now, and that those who need to detach and reattach, to get rid of that annoying message, succeed like you did.

But of course, if people never look in the log or Notices from BOINC, or can live with the message in question, they do not NEED to do anything. BOINC will work anyhow, without any problems.

If the project is greyed out in BOINC Manager, it means that you have attached through an account manager, and not through BOINC. What you have to do then, is something you must find out with the account manager you used (Science United, BAM, or some other account manager). I've never used any external account manager, so I do not have a clue what you need to do.