Ensure that you upgrade to the latest version. New features are regularly introduced to OoklaServer and some of these features may be required for your server to be enabled.

You may see a warning indicating that your copy of OoklaServer is out of date. You will need to restart both the interfering service and OoklaServer after changing the configuration. To resolve this investigate what is bound to that port and change that service's configuration to not bind to the port. Typically this means that your web server or another service is bound to the port you are testing and OoklaServer is not listening on that port. You can review port binding in the initial log output when starting OoklaServer.Īn error that the Server Tester got a 'wrong response' from OoklaServer indicates that while the tester was able to connect it did not receive the expected response from OoklaServer. You should also ensure OoklaServer is running and that is properly bound to the port being tested. This typically means that a firewall is blocking access to this port but it can also mean that OoklaServer is not running or not bound to that port.Ĭheck that the proper ports are opened in your server or other firewalls between the Server Tester and your server. If you get a connection refused error it indicates that your server refused the connection to port 8080 or whichever port you were testing. Many users have reported issues which were caused by simply using the wrong URL. Note the proper format of an OoklaServer URL below. For more information on OoklaServer setup review our installation instructions for both Unix/Linux and Windows.

This article covers common reasons you may see failures when using the Server Tester to test your OoklaServer installation.

Speed test by ookla upload speed