Page 1 of 1

Lost Web Control After Setting Up Remote Access

Posted: Tue May 12, 2015 3:59 am
by KE4EST
Hello All. I started folding in 2007, stopped in 2012 and just got back into it.
I have 2 older computers running as dedicated folding machines.
On my main computer I set up remote access so that I could look at them with out having to physically go to them.
Everything thing is on the same network. After a couple of tries I finally have it so I can see them in the advanced viewer.
Now though that I did that, I can not get web control to work in any browser on the main machine.
On the main machine all I care about in Web Control is seeing what is going on with that machine.

Anyway after I got it set up and working now web control will not connect goes through the 30 sec count down and displays the generic msg, that I need to install FAH.
I did have to put a password on it to get it to work on the remote stuff, which I thought was optional, but I guess not.
Can someone walk me though what to do? Do I need to change something in a config file?

Thanks in advance.

Re: Lost Web Control After Setting Up Remote Access

Posted: Tue May 12, 2015 5:36 am
by bruce
Whether the password is optional and which network addresses are accessible are very closely tied to the IP settings on the bottom of the Remote Access tab. That's probably where your problem lies, though I can't be certain.

Access to the other machines on your network will be available when you add something of the form 192.168.1.0./24 (your router may use a different range of addresses). Access to the local machine always uses the address 127.0.0.1 and it should NEVER be removed. Mine looks like this: ALLOW: 127.0.0.1,192.168.1.0./24 DENY: 0/0

The data on the connection tab might also be causing your problem. That defines the local machine and it must be compatible with settings on the Remote Access tab INCLUDING the local machine.

Remember that you MUST restart FAHClient (or reboot) after changing any of these setting.

Re: Lost Web Control After Setting Up Remote Access

Posted: Tue May 12, 2015 10:55 am
by KE4EST
Thanks Bruce!!!
My IP address range is different but using your example I had mine set like this:
ALLOW: 192.168.1.0./24 DENY: 0/0
instead of:
ALLOW: 127.0.0.1,192.168.1.0./24 DENY: 0/0

Adding 127.0.0.1 and restarting the client fixed it. I knew it was something really simple.
Thanks again!!