- Install the ookla software daemon on the new server
https://support.ookla.com/hc/en-us/articles/234578528-OoklaServer-Installation-Linux-Unix - Set software to start at boot
https://support.ookla.com/hc/en-us/articles/234578588-Linux-Startup-Script-Options - Copy the OoklaServer.properties from the running machine if you think you made any changes from the default. Our software runs pretty great with the defaults.
- Confirm the host can get out on port 443 to request a certificate. From your server.
- curl -v https://host-api.speedtest.net/
- See your local host is working locally : http://10.0.10.XXX:8080/
- Turn off the old server.
- Move the IP to the new server, or update DNS (A & AAAA) records.
- Restart the Ookla software so it can request a fresh certificate from LetsEncrypt. OoklaServer will retry every five minutes until a certificate is installed.
- Lets Encrypt process will not start until the IP of the machine requesting the cert matches the IP of the DNS entry we have for your host.
- Your new server will not be available on speedtest.net web site until HTTPS is working.
There is a chance our internal monitoring fails the HTTPS check the next check. In this case, expect the host will return about two hours later at the next check. - Once the new server is available on the previous host name, and passing our public host tester https://www.speedtest.net/host-tester you can submit a ticket notifying support your replacement is complete. Our Team may be able to review and return the host online a quicker depending on our queue depth and staffing.
You can submit a ticket to support directly from the portal if you notice any issues.