Hi! I've a got a problem with my FaH-client it just won't connect, it says at the top : "Client: local Connecting Inactive". I've got it to work before, and then i did something can't remember what i think it was something to connect it with my Windows computer.
What i've tried:
Reinstalled FaH client
Checked on the internet for answers, none were found.
Also in the Configure tab/window you can only configure the connection, there's not even tabs for all the other things as where there before.
Thanks!
Sorry for my English!
Last edited by Olivert on Wed Jul 24, 2013 5:09 pm, edited 1 time in total.
Which version of the F@H client are you using? Also did you use the default install, or something different? The message you are getting comes from the FAHControl app or Web Control not finding the FAHClient process running in the background as the default install would set up. So you may have managed to stop that process. Normally it should restart on its own after a short time, I forget how often the system checks. If it does not restart on its own a reboot of the Mac should restart the FAHClient process.
If that does not get your system folding again, could you post your log here. Include the beginning of the log which shows the version and system information, as well as your configuration settings. If the log will not display in FAHControl, you can find it here:
Library --> Application Support --> FAHClient --> log.txt
This is the system-wide Library folder, not the one in each account. Older logs are kept in a logs folder in the same location. With the information in the log we may be able provide further suggestions to get your system back to folding.
ChristianVirtual pointed out the error in the network portion of your configuration. If FAHControl still can not connect to the client to be used to modify that configuration, you have a few options available to correct it.
Simplest would be to reinstall after uninstalling completely including the files in folder where the logs are located.
A second option would be to revert to an older configuration and restart. The current config.xml file is stored in that folder, and by default older ones are in a folder named configs. Copying an old enough one, use it to replace the current config.xml and then rebooting should get things connecting again enough to modify the configuration again.
Finally if you are careful, you can use TextEdit to modify the current config.xml. But it is easy to corrupt the file, we usually recommend letting the client create one as it has some error checking.
