Ubuntu folding - default port blocked...how to change

[blueswitch]

so I'm using this installer script to put folding at home on an Ubuntu linux server...problem is the default port 8080 is blocked...so during install it errors out trying to connect to server to qualify the name. Which I pretty much restart the machine otherwise it just tries over and over again. I found a config file that lists the port in ~/opt/foldingathome/config/client.cfg and I can use nano to change it to something like 21...but it's like since the installer doesn't finish the command foldingathome start won;t work to run it...and a reinstall just resets the config file back to the default port. How can I get this to work?

[cw823]

Are you installing the console version?

[blueswitch]

Are you installing the console version?

yeah this is just straight up console, I'm not running gnome or anything on this machine. Actually this is a nested virtual machine in VMware.

[Adak]

I've put your question over on Stanford's FAH forum. I nosed around there, and on the FAH Wiki, but found no joy. :cry:

I don't recall ever seeing this question asked before.

[blueswitch]

I've put your question over on Stanford's FAH forum. I nosed around there, and on the FAH Wiki, but found no joy. :cry:

I don't recall ever seeing this question asked before.

thanks adak, really I'm screwing around with VMware before a corporate roll out....migth as well have the virtual machines do something constructive like fold right :beer:

[Shelnutt2]

edit your script?

[ChasR]

You have to have either port 80 or 8080 open for FAH to work.

[El<(')>Maxi]

I though ubuntu installed with all ports open? Maybe the installation is ****omized?

[blueswitch]

yeah it wants 8080 by default. Well th is is Ubuntu server so maybe it's being blocked on the servers firewall. I've not really messed around with it's firewall at all. I would think that the server could make outgoing requests though...usually it's incoming requests that get blocked.

EDIT: so after removing iptables from both the VM server and the hosting server I still get the same problem. I also found a google link with the same error 403 listed which had a test http link to try which turned out to test fine. So this is a really strange problem. The other thread found no resolve on this either, being a test server I guess it;s probably not worth my time messing with it anymore, thanks for the help though guys!