Linux Install and Configure Folding@home on Ubuntu Server


Folding@home is a distributed computing project started by Stanford University to help understand protein folding, misfolding, and related diseases. The project uses the idle processing resources of thousands of personal computers belonging to people that have installed the Folding@home software on their systems. In this post I will describe how to install and configure the Folding@home client software on Ubuntu server. All steps assume that the Apache http server on Ubuntu server is installed and operating correctly.

Software versions used in this post were as follows:

  • Ubuntu server 16.04.3 LTS
  • fahclient_7.4.4_amd64.deb
  • So let’s get started…

    Download and Install

    First, update your package list:

    Then download and install the latest 64-bit version of the Debian-based Folding@home client to a location of your choice. In this example we’ll use the user’s home directory:

    Note that fahclient_7.4.4_amd64.deb was the most current version of the client at the time this post was published. You may need to update the file name in this command in order to fetch the most recent version of the software.

    Now lets install the client:

    The installer will request you to enter a Folding@home donor name, team number, passkey (optional), whether the client should be automatically started at system boot, and how much of your system resources should be used (See Figures 1-5, repectively).

    If you have an existing Folding@home donor name enter that name here, else enter a new donor name:

    Screenshot showing the install message regarding the folding at home user name

    Figure 1

    If you’re joining an existing Folding@home team, enter that team number here, else simply enter 0 for no team:

    Screenshot showing the install message regarding the folding at home team number

    Figure 2

    The Folding@home passkey is a unique identifier that ties your Folding@home contributions directly to you (not just those with your username). The passkey uniquely identifies you as an individual donor and is associated with the results that you have completed. If you have an Folding@home passkey and would like to use it enter it here. If you don’t have a passkey and would like one, you can request one from Folding@home. Else simply select “Ok” here to move to the next screen:

    Screenshot showing the install message regarding the folding at home passkey

    Figure 3

    Choose whether or not you want the Folding@home client to startup automatically when the Ubuntu server boots:

    Screenshot showing the install message regarding the folding at home start up

    Figure 4

    Finally, you can select how aggressively the client uses your system’s CPU resources:

    Screenshot showing the install message regarding the folding at home resource use

    Figure 5

    The installer will finish and automatically start the Folding@home client. You can verify that the client is running using the following command:

    You can now delete the installation Folding@home package fahclient_7.4.4_amd64.deb from your home directory, if desired.


    Now that the Folding@home client has been installed it’s time to configure Web Control, Folding@home’s graphical interface. Web Control is the default control program for monitoring your Folding@home client via an easy to use web page.

    First, stop your running Folding@home client:

    Then use sudo and your favorite editor to append the following lines to /etc/fahclient/config.xml, which will grant access to the Web Control dashboard to a specific IP address. Unfortunately Web Control can only grant access to a single IP address. In this example we’ve chosen to grant access to the host with the IP address

    Finally, restart the Folding@home client:

    You should now be able to access the Folding@home Web Control dash board at http://your-ubuntu-server-IP-address:7396/ (See Figure 6)

    Screenshot showing the folding at home Web Control dashboard

    Figure 6

    There you have it. A few minutes of your time and you can easily have Folding@home up and running on your Ubuntu server. I think Folding@Home is a great cause and have created my own Folding@Home team to contribute some of my spare CPU cycles. How about you? If you have a few cycles to spare how about dedicating some to Folding@home’s efforts? You’re also welcome to join join my team. To join, simply enter the team number 78746 when you install folding@home.


    Tags: , ,

    News Update to Creative Commons License


    I have updated the Creative Commons Attribution license used on this site from version 3.0 to version 4.0. Version 4.0 features a number of improvements, primarily in the area of terminology that should now be better understood worldwide. What hasn’t changed is the rights granted by the license. Like its predecessor, the Creative Commons Attribution 4.0 license allows you to freely copy, distribute and transmit content made available on this site, to adapt it to something you may be working on, even make commercial use of the content. All I ask is that you attribute the original content to me in some way.

    If you have any questions or seek additional information, please don’t hesitate to contact me.


    News Wither Mint


    Back in 2012 I installed Mint, a self-hosted web site analytics program, to this site. Since that time Mint has been anonymously collecting information on about who is referring readers to this site, which posts are most popular, top searches, etc. Sadly, the Mint development team has announced that sales and support has been suspended. I have no desire to use software that isn’t going to be maintained so effective immediately I will no longer be using Mint on this site.

    So what did I learn from Mint while in use?

  • This site receives on average 8,472 unique visitors per month.
  • Unsurprisingly most of the referrals to post on this site come from Google.
  • The top three posts in terms of popularity at the time of this post were:
    1. How To Create And Configure VLANs In pfSense
      How to Install and Configure MRTG on Ubuntu
      How to Dual Boot Windows 7 and Linux using BCDEdit
  • 58% of you use the Chrome browser, while 30% use Firefox. Safari and Internet Explore receive honorable mentions at 6% and 1% respectively.
  • At the moment I have no plans to replace Mint with another web site analytics program. Should I decide to do so I will let you know. Rest assured though that anything I may decide to use will not collect personal data of any kind.


    Hardware How to Remove Those Old Laptop Stickers


    Tired of those old stickers you adorned your laptop with? Me too. No, I don’t mean yours. I’m sure yours are fine; well, except for that Bieber Rocks! one. What were you thinking!? Anyway, here’s couple of tips on how to remove Bieber and his sticky cousins.

    Screenshot showing a Lenovo laptop with numerous stickers

    First, power down your laptop, unplug it, and close the lid. Try to remove as many of those old stickers by simply peeling them off. Some will come off cleanly, many won’t. Don’t worry if some of the residue is left behind. Now head to your kitchen and grab that good old no-stick cooking spray and apply liberally to a small section of the laptop surface. Don’t be stingy. The idea is to keep the area you’re working on soaked in the stuff for at least 10-15 minutes – the longer, the better though. Make sure to not let it run down the sides and creep into cooling vents, on to your keyboard, etc.

    Screenshot showing a can of no-stick cooking spray

    Now grab one of those plastic paint scrapers (emphasis on the word plastic here) you’d find at any big-box hardware store and start gently scraping off the remaining sticker residue, reapplying the cooking spray as necessary. Continue working your way across the surface of your laptop by applying the cooking spray, letting it soak in, then gently scraping.

    Screenshot showing a plastic paint scraper

    Once you’ve exhausted the capabilities of that paint scraper, any remaining residue can usually be removed with a little more cooking spray and a nylon scrubbing pad.

    Screenshot showing a nylon scrubbing pad

    This simple combination of cooking spray, gentle scraping and patience should remove those old stickers and any remaining residue they leave behind. If for some reason the cooking spray isn’t getting the job done for you then WD-40 or a citrus base adhesive remover like goo gone may be a good alternative. Both should be safe to use on your laptop but of course you should test these products first on someplace inconspicuous.

    Screenshot showing a can of WD-40

    Screenshot showing a bottle of goo gone

    As a final step gently clean off the surface of the laptop using a clean wash cloth, warm water and dish washing soap, then dry using a clean cloth or paper towel.

    Screenshot showing a Lenovo laptop after stickers have been removed

    There you have it. A couple of tips on how to remove those old laptop stickers using materials you can easily find around the house. Do you have more tips or ideas? Leave them in the comment section.


    Windows How to Install and Configure a TeamSpeak Server With a Different Voice Port


    TeamSpeak is a voice communication tool for online gaming, education and training, internal business communication, and similar use cases. This post will describe how to install TeamSpeak server on the Windows operating system, configure it to listen for incoming voice connections using a non-default UDP port, and test the installation/configuration using the TeamSpeak client application. Also discussed is how to remove your TeamSpeak server from the list of publicly available servers. The versions for the software discussed in this post are as follows:

  • Windows 7 Pro x64
  • TeamSpeak Server 64-bit
  • teamSpeak Client 64-bit
  • Let’s get started…

    Install and Configure the TeamSpeak Server

    Start by downloading the TeamSpeak server and extracting the folder contained within the zip file to a location of your choice. We’ll use C:\ in our example. After the folder is extracted we should see the folder C:\teamspeak3-server_win64.

    Open this folder and create a shortcut to C:\teamspeak-3-server\ts3server_win64.exe to somewhere convenient. Right-click on the shortcut, navigate to Properties, and append createinifile=1 to C:\teamspeak3-server_win64\ts3server_win64.exe in the Target field (e.g. C:\teamspeak-3-server\ts3server_win64.exe createinifile=1) then select “OK” to save and close the window.

    Double-click on this shortcut to start the TeamSpeak server. You should see a new icon in the notification area of the windows task bar indicating that the TeamSpeak server has started. When the TeamSpeak server is started for the first time a pop-up window will appear showing the Server Query credentials and the Server Admin Token (See Figure 1). You can disregard this information for now and close the window.

    Screenshot showing the Server Query credentials and Server Admin Token after initial TeamSpeak server startup

    Figure 1

    Now open the folder C:\teamspeak3-server_win64 and you should see several new files, including ts3server.ini and ts3server.sqlitedb.

    Stop the TeamSpeak server by right-clicking on the icon in the notification tray and selecting “Exit”. Delete the file C:\teamspeak3-server_win64\ts3server.sqlitedb. Open C:\teamspeak-3-server\ts3server.ini and change the value of default_voice_port value to the port number desired. We’ll use 12010 in our example.

    Once again right-click on the shortcut, navigate to Properties. Replace createinifile=1 with inifile=ts3server.ini in the Target field (e.g., C:\teamspeak-3-server\ts3server_win64.exe inifile=ts3server.ini) then select “OK” to save and close the window.

    Restart the Teamspeak server and a new C:\teamspeak3-server_win64\ts3server.sqlitedb file will be created containing the new port number. The pop-up window showing the Server Query credentials and the Server Admin Token will again appear. This time you’ll want to copy at least the Server Admin Token somewhere as this key is needed to gain administration rights to your TeamSpeak server. I also recommend copying the Server Query credential somewhere as well. This will be needed should you ever want to use ServerQuery, a command line based administration tool supported by TeamSpeak.

    Now let’s verify that the TeamSpeak server is using the new voice port. Navigate to C:\teamspeak3-server_win64\logs and open the most recent file (e.g., ts3server_2016-03-18_11_36_31.481617_1) You should see the entry “listening on”. This confirms that new port is now in the database file c:\teamspeak3-server_win64\ts3server.sqlitedb and listening for incoming voice connections.

    Test Using the TeamSpeak Client

    Okay, now that we have the TeamSpeak server installed and configured let’s install the TeamSpeak client and test to ensure that you can connect to it.

    Download the TeamSpeak client application and install it. Start the TeamSpeak server and then start the TeamSpeak client. Once the TeamSpeak client has started select Connections->Connect (or use CTRL+s). In the Server Address field enter the host name of the Teamspeak server followed by the port number the server is listening on for incoming voice connections. These two entries should be seperated with a colon. Since our Teamspeak server is located on the same machine as the TeamSpeak client we’ll use the host name localhost. The port number will of course be the one we configured for this Teamspeak server, port 12010 (See Figure 2):

    Screenshot showing a new TeamSpeak server address and UDP port being configured in the TeamSpeak client application

    Figure 2

    Select “Connect” and you’ll will be connected to your TeamSpeak server. A window will appear indicating that this is newly created Teamspeak server and that the administrative privileges have not yet been claimed. Enter your Server Admin Token, then select OK. Note that this pop-up window will occur each time you connect to the TeamSpeak server until you’ve used the Server Admin Token. An unused Server Admin Token can be entered at any time after you’ve connected to the TeamSpeak Server by selecting Permissions->Use Public Key.

    Now that you’ve verified that you can connect to your TeamSpeak server locally, make sure to forward the correct UDP port (12010 in our example) in your NAT gateway so that, if desired, TeamSpeak clients outside of your local network can connect to your Teamspeak server.

    Generating additional Server Admin Tokens

    What if you want to add administrative privileges to another TeamSpeak client so, for example, you can administer the TeamSpeak server remotely? No problem. Using the TeamSpeak client you used previously to enter your Server Admin Token with connect to your Teamspeak server and navigate to Permissions->Privilege Keys and select “Create”. In the next window select Server Admin from among the options in the Group field. Enter a description if desired then select “Create” (See Figure 3). You can use this new Server Admin Token with another TeamSpeak client by connecting to the TeamSpeak server and selecting Permissions->Use Public Key.

    Screenshot showing where to create a new Server Admin Token

    Figure 3

    You can revoke tokens at any time by navigating to Permissions->Privilege Keys, highlighting the desired token and selecting “Remove.”

    Prevent your TeamSpeak server from appearing in the public server list

    TeamSpeak servers are automatically added to a list of publicly available servers when installed. This may not be desirable. To remove your server from this public server list connect to your server using a TeamSpeak client with administrative privileges. Right-click on your server’s name and select Edit Virtual Server. Select the Misc tab and uncheck the option “Enable reporting to server list” then select “Apply” (See Figure 4).

    Screenshot showing where to disable public server listing in the TeamSpeak server configuration

    Figure 4


    Well there you have it. A post describing how to install TeamSpeak server on the Windows operating system. The developers of TeamSpeak should make it easier for server administrators to make simple modifications like changing the default ports. Until they do this article should help you make those changes.