F@H Browser Control Access from another computer

[Tad Bittoomuch]

Hi everyone,

 

I'm currently trying to access a F@H computer on my local network using the web control, but I keep getting the error '401 Unauthorised'.

 

I've followed the steps in this guide and restarted the computer and client many times.

For reference:

• 192.168.1.101 (F@H Computer)
• 192.168.1.193 (Computer I'm trying to access the web control with)

 

Local configuration:

 

Browser error (different computer):

 

F@H Client log (local) (192.168.1.193 is the computer I'm trying to access the web control from)

 

 

Has anyone else encountered this issue/what did you do to fix it, or is it just that in the two years since the guide was written F@H has removed this functionality?
 

[Oshino Shinobu]

Your configuration seems to show it set to port 36330 but you're trying to access it via port 7396. 

[Tad Bittoomuch]

10 minutes ago, Oshino Shinobu said:

Your configuration seems to show it set to port 36330 but you're trying to access it via port 7396. 

I'm only trying to access the browser control, which is port 7396.  I don't need the advanced control:
If for example I put 192.168.1.101:36330, chrome spits out ERR_INVALID_HTTP_RESPONSE.

 

On 11/3/2018 at 3:57 AM, Gorgon said:

The WebControl runs on TCP Port 7396
~snip~
In order to permit access to either the Web Control or using the Advanced client on another PC you have to allow access on the remote system.

 

This is essentially what I've done, and on the F@H computer if I type localhost:7396 into the browser it goes to the web control.
The problem I'm having is that despite having added my local network IP range into the IP address restriction in the advanced client configuration on the F@H computer, it still denies access to the web control from any other computer on the network

[Gorgon]

20 minutes ago, Tad Bittoomuch said:

I'm only trying to access the browser control, which is port 7396.  I don't need the advanced control:
If for example I put 192.168.1.101:36330, chrome spits out ERR_INVALID_HTTP_RESPONSE.

 

 

This is essentially what I've done, and on the F@H computer if I type localhost:7396 into the browser it goes to the web control.
The problem I'm having is that despite having added my local network IP range into the IP address restriction in the advanced client configuration on the F@H computer, it still denies access to the web control from any other computer on the network

You have to restart the Folding Client for it to reload the config. On Windows systems a reboot may be required. In some instances if your Windows Firewall is confused and your home network is in some zone other than home it will cause issues.

[Tad Bittoomuch]

5 minutes ago, Gorgon said:

You have to restart the Folding Client for it to reload the config. On Windows systems a reboot may be required. In some instances if your Windows Firewall is confused and your home network is in some zone other than home it will cause issues.

I restarted the F@H computer and F@H client individually and set both the network locations to 'Home' however that didn't seem to do anything.

 

Do I need to allow anything specific in Windows Firewall Inbound/Outbound rules/Allowed applications?

e.g. Inbound/outbound rules:

 

e.g. allowed applications:

 

[Tad Bittoomuch]

Console Log of config:

 

The 192.168.1.0/24 address range is being saved, which is why this is inexplicable:

[acewingman]

Does it need a dash in the ip range?

[Tad Bittoomuch]

43 minutes ago, acewingman said:

Does it need a dash in the ip range?

I added the dash to explicitly specify the range, however it didn't do anything different.

 

The browser access still returns 401 unauthorised.

 

As a test I added a password but that still didn't work.

[Gorgon]

1 hour ago, Tad Bittoomuch said:

Console Log of config:

 

The 192.168.1.0/24 address range is being saved, which is why this is inexplicable:

That should work. Try disabling the windows firewall. I suspect this is what is screwing you over.

 

I don’t run Windows on any of my folding rigs but my Daily Driver is Windows 10.

 

I also use the Advanced Control Folding application installed on my monitoring system rather than the browser so you could try installing the FAHClient software without any slots configured then adding the remote system to see if that works but that will only tell you if TCP Port 33600 is open not 7396 used by the web client. Or a a quick test using a Telnet client that understands Unix (I.e. Not the one built into Windows) such as PuTTY one opening TCP port 33600 and typing “help”

 

The FAHClient Advanced Control is just basically a Python Wrapper around a telnet Client to give a pretty GUI

[Tad Bittoomuch]

Solution from Page 121 of the LTT Covid-19 Emergency Response Megathread

On 3/23/2020 at 1:30 AM, CWP said:

The web interface uses a separate tag <web-allow v='(ip ranges)' />. The <allow> tag is for the advanced control only.

Thanks to CWP for providing this solution!

If anyone is wondering how to enable browser access (Web control) for a machine on your local network (not with the advanced client), you can either:

 

a) Edit your F@H config.xml file to include <web-allow v='(ip ranges)' />.

This is useful if you don't have a screen attached to your F@H computer and are able to SSH into it to edit /etc/fahclient/config.xml.

For example, this section of my config reads:

<config>

	-stuff-

	<!-- Web Server -->
	<web-allow v='127.0.0.1 192.168.1.0/24'/>
    
    	-more stuff-
    
</config>

Meaning it will allow web access from localhost (127.0.0.1) as well as any other machine on your local network, assuming your DHCP range is 192.168.1.0/24.

If yours is something different, i.e. 192.168.0.x or 10.0.2.x then you'd replace it with 192.168.0.0/24 or 10.0.2.0/24.  Replacing the x with 0/24 is like shorthand for representing the entire DHCP scope, i.e. 192.168.1.0 - 192.168.1.255.

Alternatively if you only want a single machine on your local network to be able to access the browser control, then you can put single IP addresses in there, separated by spaces.

For example if you wanted only the IP addresses 192.168.1.188 and 192.168.1.62 (or whatever yours is) to be able to access the browser control, your config would look like this:

<config>

	-other stuff-

	<!-- Web Server -->
	<web-allow v='127.0.0.1 192.168.1.188 192.168.1.62'/>
    
    	-other more different stuff-
    
</config>

 

b) Using the Advanced Control GUI on the F@H machine.

This is easier than having to dig through Windows to find the config.xml file for F@H.  Open the 'Expert' tab in the 'Configure' menu and add the following, obviously making sure the DHCP scope matches your local network.

 

Click save and pause all active work units, then either restart your computer or F@H to reload the new config.

 

When you're done, you should be able to go to any computer on your local network (or the ones you specifically specified) and enter http://local_ip_of_F@H_computer:7396.

Replace local_ip_of_F@H_computer with the IP address of your F@H computer - for example mine is http://192.168.1.101:7396.