Tester Privileges and "Testing the Tester"
Because it uses low-level socket calls the tester itself usually has to run with root privileges (this is usually a PHP or OS setting). If you want to try and run under different environments you can do so from the command-line using the test/ping.sh and test/test.sh scripts.
ping.sh simply takes a hostname/IP and uses the FreeNATS ping test method. A zero result exactly (with no decimal places shown) indicates the test has failed.
test.sh takes the internal FreeNATS name of a test, the hostname and optionally a parameter for the test. Not everything is available to be checked using this and any tests should at most require the same rights as the ping test so using ping.sh to test is recommended.
You can also run the entire test session in the foreground and view detail as follows...
Running Test Sessions in the Foreground for Debugging
You can run bin/tester.sh with the FreeNATS nodeid as a parameter to run a test session in the foreground. This will output a large amount of data to the console.
Virtual Appliance Maintainance
You should ensure the Virtual Appliance is kept up-to-date via the rPath administration interface (https://THE.IP.ADDR:8003/) especially if it is in a live or exposed environment.