Hi all!

For reasons unknown i can no longer connect to the boinc client with boinc manager on a remote system. boinccmd locally works fine. The changes i made prior to this problem occurring were to account_boinc.bakerlab.org_rosetta.xml and boinc_client_flags= in /etc/rc.conf - changes restricted to account keys only!

client: BOINC 7.8.6
Operating System: FreeBSD 11.3-RELEASE-p6

manager: BOINC 7.14.2
Operating System: Debian GNU/Linux 10 (buster)

sample sockstat output from the boinc client host.
boinc boinc_clie 31471 6 stream -> ??
boinc boinc_clie 31471 8 tcp4 127.0.0.1:31416 *:*
boinc boinc_clie 31471 12 tcp4 10.0.0.66:28187 128.95.160.157:80
boinc boinc_clie 31471 14 tcp4 10.0.0.66:12385 128.95.160.156:80

Scan from boinc manager host on boinc client host.
Nmap scan report for xxxx.xxx (10.0.0.66)
Host is up (0.0013s latency).

PORT STATE SERVICE
31416/tcp closed boinc

31416 is bound to 127.0.0.1:31416 and not 10.0.0.66:31416, could that be the problem? if so, how do i change it?

boinccmd from the command line on the remote host returns "can't connect to 10.0.0.66". The gui version gives no errors, sometimes the bottom right icon changes to disconnect or is stuck on connecting.

Thank you for your time!

/etc/rc.conf

# Enable BOINC on start-up
boinc_client_enable=YES
boinc_client_flags="--allow_remote_gui_rpc --attach_project http://boinc.bakerlab.org/rosetta/ my-account-key"

i found out what was causing this.
In cc_config.xml <allow_remote_gui_rpc> got set to 0 - not sure how :)

changing it to 1 resolved my problem.

I thought the start up script boinc_client_flags="--allow_remote_gui_rpc" would set it to 1, but apparently not.