Hi,
I've had a lot of issues trying to connect my hosts to BAM account. In the past I had the same problem but trying to connect several times worked until now but it no longer work. I've tried on 3 differents machines on Windows 7, Debian and Fedora, I've tried to change my password, change my username and revert to the old one, attach account manager with boinccmd, nothing worked until now. Don't know what to do now since the issue seems to be on boincstats/BAM side.

Is anybody maybe have some workaround to try please ?

Thank you in advance and sorry for my bad English, feel free to ask if you need more informations !

Are all 3 systems on the same network? If so it could be a firewall/router that's blocking the ports that BOINC uses.
If not so: are you sure using the same credentials for activating the account manager as you use for logging into this website?
What versions of BOINC do you have installed?
Are there systems that are connected to BAM! ?
Although a bit outdated: have you read the FAQ-section for BAM! at https://www.boincstats.com/page/faq ?

Thanks for your answer,

Currently the systems are all on the same network, I don't think it's a firewall problem because I always had this issue and I've changed places many time and until now trying several times worked (without changing anything). I'm using strictly the same credentials as the website, as I always did.
Currently the boinc versions I'm using are 7.16.1 on Fedora, 7.12.1 on Windows 7,13.x on debian.
They were all connected to BAM few month ago and they all needed severals trials (with same credentials) to connect properly. Currently there's no machines effectively connected to BAM (fresh OS) despite my trials.
Yes, nothing's here to help me sadly, I'm not realy new (but clearly not realy old !) with boincstats and have no problem other than connecting my hosts to the account manager

Sorry for the delay, happy new year! Could you dig up some logging? The first 30 lines when BOINC starts (replace the name of your host and the ip with xxx) of one of the hosts.
The output of and after that the output of this command with your own credentials: That should give some clues to see where the problem could be.