Hello,

I am a volunteer helper and have been getting numerous emails lately for people stating that they cannot attach to projects. They are getting the following message from BOINC manager: "Project not found: The URL you supplied is not that of a BOINC-based project."

All users having issues are on windows, though I don't know the exact version. I have tried under a winXP setup under Parallels (I'm on a Mac) and attaching to project and stuff works with no issues.

Is this a known issue with the latest versions of BOINC?

No, this is not a known problem with any version of BOINC. Without one of these people venturing on here to tell exactly what they did, it's also very difficult to diagnose.

So the questions:
1. How do they attach to the project, through the project list or typing the address?
2. Which Project(s) is this with?
3. Which BOINC version is this with?
4. Are they behind a (corporate)(school) firewall?
5. Are they behind a proxy?

---

using the Boinc Manager 7.2.39
no firewalls and no proxies

when trying to connect to this project: http://www.rechenkraft.net/yoyo/

i am returned the following message: The Url you supplied is not that of a Boinc-based project.

Note I have several android devices that are currently on the same network and connected to that project with no issue. I have sent screen shots to the person above via email and am happy to forward them to another email if you provide.

-Wayne Barter (wbarter)

From the log:
2/25/2014 9:14:17 AM | | Fetching configuration file from http://www.rechenkraft.net/yoyo/get_project_config.php




I tried to access that link from a webpage Response when accessing that link from a webpage:

<?xml version="1.0" encoding="ISO-8859-1" ?>
- <project_config>
<name>yoyo@home</name>
<master_url>http://www.rechenkraft.net/yoyo/</master_url>
<web_rpc_url_base>https://www.rechenkraft.net/yoyo/</web_rpc_url_base>
<web_stopped>0</web_stopped>
<min_passwd_length>6</min_passwd_length>
<sched_stopped>0</sched_stopped>
- <platforms>
- <platform>
<platform_name>arm-android-linux-gnu</platform_name>
<user_friendly_name>Android running on ARM</user_friendly_name>
</platform>
- <platform>
<platform_name>arm-linux-gnu</platform_name>
<user_friendly_name>Linux running on ARM (arm-linux-gnu)</user_friendly_name>
</platform>
- <platform>
<platform_name>arm-unknown-linux-gnueabi</platform_name>
<user_friendly_name>Linux running on an ARM compatible CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>arm-unknown-linux-gnueabihf</platform_name>
<user_friendly_name>Linux running on Raspberry Pi</user_friendly_name>
</platform>
- <platform>
<platform_name>i686-apple-darwin</platform_name>
<user_friendly_name>Mac OS 10.4 or later running on Intel</user_friendly_name>
</platform>
- <platform>
<platform_name>i686-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an Intel x86-compatible CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>powerpc-apple-darwin</platform_name>
<user_friendly_name>Mac OS X 10.3 or later running on Motorola PowerPC</user_friendly_name>
</platform>
- <platform>
<platform_name>powerpc64-ps3-linux-gnu</platform_name>
<user_friendly_name>Sony Playstation 3 running Linux</user_friendly_name>
</platform>
- <platform>
<platform_name>sparc-sun-solaris</platform_name>
<user_friendly_name>Solaris 2.8 or later running on a SPARC-compatible CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>windows_intelx86</platform_name>
<user_friendly_name>Microsoft Windows (98 or later) running on an Intel x86-compatible CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>windows_x86_64</platform_name>
<user_friendly_name>Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>x86_64-apple-darwin</platform_name>
<user_friendly_name>Mac OS 10.5+ running on an Intel 64-bit CPU</user_friendly_name>
</platform>
- <platform>
<platform_name>x86_64-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
</platform>
</platforms>
</project_config>

Please before doing anything here, go to my next post first and try the new BOINC Manager.

Can you please open Notepad to make a cc_config.xml file and add into it:

<cc_config>
<log_flags>
<http_debug>1</http_debug>
<http_xfer_debug>1</http_xfer_debug>
</log_flags>
<options>
</options>
</cc_config>

File->Save as..
Filename: cc_config.xml
Save as type: All files (*.*)
Encoding: ANSI
Save path: Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC
Windows Vista/Windows 7/8/8.1: C:\ProgramData\BOINC
This directory will be hidden, so just fill the path in directly in Windows Explorer.
After saving check that the only extension is .xml, else rename and take off the extra extension.

Next open BOINC Manager, advanced view, Advanced menu, Read config files.
Next go to the Tools->Add project or account manager->Add project->Select select Yoyo@Home and click OK.
Then open the Event Log (CTRL+SHIFT+E) and copy all of the communication lines. Do not remove any of the IP addresses or other information, just post all the here.

Afterwards you can disable the lines in cc_config.xml like so:

<cc_config>
<log_flags>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
</log_flags>
<options>
</options>
</cc_config>

And again do open BOINC Manager, advanced view, Advanced menu, Read config files.

If you have a cc_config.xml file already, add in the lines in the <log_flags/> section. Or post its contents here and ask if someone can add the lines in the correct order.

---

I just went through old emails, and saw the following on the Alpha email list:
Rom Walton wrote:

For anybody running into the 400 error on Yoyo@Home can you give this private drop of BOINC Manager a try?

x64: http://boinc.berkeley.edu/dl/boincmgr.180214.x64.zip
x86: http://boinc.berkeley.edu/dl/boincmgr.180214.x86.zip

To use the drop, download the correct version of BOINC Manager. You can see if you have a 32bit (x86) or 64bit (x64) version by opening BOINC Manager->Help->About BOINC Manager. There it will state if it's a 32bit or 64bit version.

When you know this, download the above compressed file.
Next exit BOINC completely: File->Exit, Check Stop running tasks when exiting Manager?, OK. If you do not see this dialog, and you want to, open BOINC Manager again, then go Tools->Options and check "Enable Manager exit dialog?"->OK, then do File->Exit.
Next open the compressed file, Organize->Select all, Organize->Copy.
Now navigate to your BOINC Programs directory.

Default BOINC Program directories:
Windows 32bit: C:\PROGRAM FILES\BOINC
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC

In there do Organize->Paste.

Next restart BOINC Manager.
Start->All Programs->BOINC->BOINC Manager.

And let it make contact with Yoyo@Home.

---

Next open BOINC Manager, advanced view, Advanced menu, Read config files.
Next go to the Projects tab, select Yoyo@Home and click Update.

What projects tab, Ageless? They can't even attach to the project in question in the first place...

You're right, I had typed that on automatic pilot. Have adjusted it.
However, I'm also pretty certain that the new BOINC Manager will fix it.

---

Question...will installing a new Boinc manager mess up my existing tasks or do I want to complete first and prevent new tasks prior to changing?

BOINC Manager is merely the graphical user interface with which you control and command the client. Updating it, or the client, does not harm any tasks in the data directory in any way. As long as you follow the steps as detailed, w.r.t closing down BOINC completely before doing the update, nothing should go wrong.

The problem at hand is in the Add project wizard, which is part of the BOINC Manager program. A bug between the new wxWidgets 3.0 and the compiler used (VS 2010) caused the problem at hand. The updated BOINC Manager should have that fixed.

---

Thanks....will try and report back momentarily

Success....that fixed the issue. Will your fix be incorporated in the distributed boinc manager moving forward?

Yes. A new BOINC 7.2 should've already been had, but the HTC/BOINC on Android release threw that release back a couple of days. I'll let the developers know that there's a lot more people with the Yoyo@Home connect problem, so they can rush out 7.2.42 (if I guess correctly).

---

many thanks!

Hi,
I'm trying to add seti@home as a project to BOINC. I'm choosing it from the list of projects but I'm getting a message that "the internet address doen not belong to a BOINC- based project. Please check it and try again" (this is a transealtion. the wording in english might be a bit different).
can you assist with that?

I have installed BOINC manager version 7.2.39.

Thanks a lot!

Try the steps above...this resolved the problem for me.

-Wayne

Does this pertain to Macs with Mavericks installed? I had the "...does not belong..." message, I reinstalled BOINC 7.2.39 and that went away but now I am getting Error 400 messages from Yoyo. Seems to happen to me only with Yoyo.

Jim

---

Thanks,
Jim

Does this pertain to Macs with Mavericks installed? [--] I reinstalled BOINC 7.2.39 and that went away but now I am getting Error 400 messages from Yoyo. Seems to happen to me only with Yoyo

I've had the HTTP 400 error on Linux. For some reason Yoyo seems to be affected worst but I had it with Simap and Seti IIRC.

There's no hotfix for Macs so you need to go for a workaround. Try restarting the client and/or the Manager and/or setting a different language in Manager.

Restarting BOINC Manager seems to work. I love success even though I have no clue it is successful.

---

Thanks,
Jim

I am having the same problem with the linux x64 7.2.39 version. Can't attach to yoyo. Is there a work around for that?

https://dl.dropboxusercontent.com/u/55884901/choose.png
https://dl.dropboxusercontent.com/u/55884901/result.png
https://dl.dropboxusercontent.com/u/55884901/event2.png