Does the lookup command give you the same key?

Same response...

can't connect to local host

---

Radjin~

Always someone trying to do things the hard way ;-) I use Monitors on All my machines. Try adding the password cmd from here, https://boinc.berkeley.edu/wiki/Boinccmd_tool
~/BOINC$ ./boinccmd --project_attach http://setiathome.berkeley.edu --passwd <weak key>
At least we know both boinc & boinccmd work. I'm going to leave it to others, I use the GUI...

Always someone trying to do things the hard way ;-) I use Monitors on All my machines. Try adding the password cmd from here, https://boinc.berkeley.edu/wiki/Boinccmd_tool
~/BOINC$ ./boinccmd --project_attach http://setiathome.berkeley.edu --passwd <weak key>
At least we know both boinc & boinccmd work. I'm going to leave it to others, I use the GUI...

My main computer is not the web server, hence a headless unit. I would expect I could apt install a package and have it just work. All this configuration is kind of fun for a while; a distraction of sorts, but if something is just broken the fun begins to fade away.

I noticed that all this fiddling seems to have stopped outgoing traffic for my VPN. I wonder how that is related? I can still apt update and ping so all communication is not stopped.

Same response:
can't connect to local host

I think the syntax is right, there’s something else not allowing communication.

Thanks for the corrections and help though.

---

Radjin~

I don't know how you have your machines setup, But, the Berkeley BOINC can be easily moved from one Linux machine to another. Just make sure to Zip the BOINC folder before moving it from one machine to another to preserve the Execute bits. You can Zip the BOINC folder, move it to another machine, attach the Host, then move the zipped BOINC folder back to the headless machine. That should work without any trouble.

You are dealing with rpc's, remote procedure calls when using boinccmd. First thing is to make sure you have port 31416 open and not blocked by a firewall. Then you need to either reset the gui_rpc_auth.cfg file with your own password or delete the file and restart boinc. The boinccmd has to be able to talk to the client boinc and the password has to match.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You are dealing with rpc's, remote procedure calls when using boinccmd. First thing is to make sure you have port 31416 open and not blocked by a firewall. Then you need to either reset the gui_rpc_auth.cfg file with your own password or delete the file and restart boinc. The boinccmd has to be able to talk to the client boinc and the password has to match.

When you say 31416 open, you mean for incoming and TCP.

---

Radjin~

Yes, for both outgoing and incoming on tcp port 31416 for localhost.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You are dealing with rpc's, remote procedure calls when using boinccmd. First thing is to make sure you have port 31416 open and not blocked by a firewall. Then you need to either reset the gui_rpc_auth.cfg file with your own password or delete the file and restart boinc. The boinccmd has to be able to talk to the client boinc and the password has to match.

Using find there were two instances of gui_rpc_auth.cfg; both deleted

There firewall is not active

sudo /sbin/iptables -L

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

---

Radjin~

Did you ever get the OpenSSL dependencies loaded??

Did you ever get the OpenSSL dependencies loaded??

Yes, using TBar’s instructions from https://setiathome.berkeley.edu/forum_thread.php?id=84658&postid=2012111#2012111.

ldd shows all dependencies met.

---

Radjin~

Why you not try to run in a more "conventional" way?

Start the boincmgr program, use his GUI to attach to the project, let him create all the needed files and links, be sure is running and crunching and then exit it.

Then go to control with boinccmd as apparently you wish to do?

Not believe you have troubles with the dependencies anymore since both programs (boinc client & manager) are running fine. As you posted.

This is exactly what this post suggest:

At least we know both boinc & boinccmd work. I'm going to leave it to others, I use the GUI...

---

ldd shows all dependencies met.

Hmmm. Well, I am able to get the BOINC AIO running in Debian 10 through both the boincmgr GUI, and via boinccmd, using both SSL versions of the boinc file. Must be a problem with your specific machine. I did this all through the Gnome DE, so perhaps that is a factor, but I don't see why it would be for the command line operations.

Why you not try to run in a more "conventional" way?

Start the boincmgr program, use his GUI to attach to the project, let him create all the needed files and links, be sure is running and crunching and then exit it.

Then go to control with boinccmd as apparently you wish to do?

Not believe you have troubles with the dependencies anymore since both programs (boinc client & manager) are running fine. As you posted.

This is exactly what this post suggest:

At least we know both boinc & boinccmd work. I'm going to leave it to others, I use the GUI...

A headless system is likely more conventional and running a GUI would take resources, adding a monitor and a desktop install.

I appreciate all the help but I will continue to use the command line on my headless unit for those who can spare the time to assist.

---

Radjin~

I think the problem is he isn't using the method for Remote RPC. Remote is different than Local RPC. The instructions are here, https://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely
You might look into this thread, Problems with Boinc Tasks and linux

ldd shows all dependencies met.

Hmmm. Well, I am able to get the BOINC AIO running in Debian 10 through both the boincmgr GUI, and via boinccmd, using both SSL versions of the boinc file. Must be a problem with your specific machine. I did this all through the Gnome DE, so perhaps that is a factor, but I don't see why it would be for the command line operations.

Since starting to play with boinc I seem to have killed the http/https out from my system as it also has killed my VPN out to the web.

---

Radjin~

Since starting to play with boinc I seem to have killed the http/https out from my system as it also has killed my VPN out to the web.

Maybe try deleting the soft links you created earlier for the SSL libraries, if you haven't already, especially since they should no longer be needed. It's a complete guess, but may create issues for programs requiring the 1.1 version.

how are you accessing the system since it's headless and no monitor, etc?

ssh on the local network? VPN+ssh to a remote machine?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

how are you accessing the system since it's headless and no monitor, etc?

ssh on the local network? VPN+ssh to a remote machine?

Just ssh locally from my Mac or via an app on the iPad.

---

Radjin~

Since starting to play with boinc I seem to have killed the http/https out from my system as it also has killed my VPN out to the web.

Maybe try deleting the soft links you created earlier for the SSL libraries, if you haven't already, especially since they should no longer be needed. It's a complete guess, but may create issues for programs requiring the 1.1 version.

Thank you for reminding me... I deleted them directly then wondered If I should have done so via a command or if it matters.

---

Radjin~

Since starting to play with boinc I seem to have killed the http/https out from my system as it also has killed my VPN out to the web.

Maybe try deleting the soft links you created earlier for the SSL libraries, if you haven't already, especially since they should no longer be needed. It's a complete guess, but may create issues for programs requiring the 1.1 version.

Thank you for reminding me... I deleted them directly then wondered If I should have done so via a command or if it matters.

No change, I still cannot use my VPN through the server or register the key file with “./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>”. I am pretty sure the two are related, both calling URL’s; the browser saying can’t reach server and the key reg saying cannot connect to localhost. Just need to figure out what broke.

Just learned I can ping an IP address and a URL so not a total system block on outgoing requests.

---

Radjin~