Dear Community,
I am planning to setup a own boinc server for a small company. Because I am a newbie with boinc, I tried to setup a boinc-vm with a cplan test project first.

I followed these steps on the official boinc documentation:
https://boinc.berkeley.edu/trac/wiki/ServerIntro

I also installed the boinc-client and the boinc-manager on my host system (Ubunut 16.04) via apt.

When I start the boinc-manager and try to add the boinc-vm with my test project, it connects to the server and asks me for my account credentials. After entering my credentials, the process fails without any helpful error messages. It just says "Adding project failed. Please try it again later."

On the other hand, I can successfully log in via the web-ui of the project.

I also tried the given, already configured boinc-vm, but the problem still remains.
https://boinc.berkeley.edu/trac/wiki/VmServer

When I use the boinccmd on my host system, I will get the following message:

$ boinccmd --lookup_account http://127.0.0.1:8080 my_email_adress my_password
status: Success
poll status: operation in progress
poll status: permanent HTTP error

If you need the output of a log file or any other information, please do not hesitate to ask me. I will be grateful for any suggestion.

Regards

@admins: I do not know if this thread belongs to the topic. Please feel free to move it if necessary.

This is probably a problem with how you setup your project. When running make_project on the server it uses the current IP of the server to create the project. This IP is added in several places and later send to clients when they connect. If the client then can't reach the IP it fails with the errors you describe.

So in short you should check on the server what values are set in config.xml as master_url and what is in html/user/scheduler.txt. You need to make sure that the correct information is in those files. Ideally both would contain the "public" IP of the server or a servername that can be resolved by your clients. This part depends on whether you want your project to be public (reachable via Internet) or company internal.

Please note that changing the master_url is not easily possible for public facing projects.

Turns out that I forgot to change the server address in the scheduler.txt file, my mistake. Thank you very much for the hint :)

I suspected as much. We should definitely get rid of this dependency or at least have an easy way to detect an inconsistency there.