I have the IP addresses specified in both.
It is not a big issue. It runs on multiple servers in my garage. I just need to be mindful when I restart them to manually stop, kill and start again.
As long as they keep running and churning out folds they will likely not be restarted at all.
Remote access not working
Moderators: Site Moderators, FAHC Science Team
-
- Site Admin
- Posts: 7936
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: Remote access not working
Did you restart all systems' FAHClient process or reboot them after adding the necessary network addresses and the optional password? If you don not add a password for use on your own LAN, you need to add the addresses allowed to access without a PW.Teacfreak wrote:I'm new and have three machines running. One W10 and two Debian headless, while the W10 should also show the two headless systems.
I followed the discussion here but it seems that the "command port" 36330 is only open on the local 127.0.0.1 device. Connecting to the external device, even from the specific machine itself, telnet connection fails.
So how can I activate the external port? I did an all machines the standard installation with no custom config, except the account information of course.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Posts: 5
- Joined: Sat Mar 21, 2020 10:51 pm
Re: Remote access not working
https://www.youtube.com/watch?v=qEv-B2C ... bvlLYjZn0AThe second video is about setting up remote control.
-
- Posts: 3
- Joined: Sat Mar 21, 2020 7:33 am
Re: Remote access not working
Great, thanks for the videolink!