Install SSL Certificate

testgrinder service will be discontinued on January 31, 2025

testgrinder SMPC was discontinued as of February 1, 2024

To avoid a security warning when accessing testgrinder via https, you will need to supply a valid SSL certificate for the domain on which testgrinder will be responding to user requests.

You supply SSL certificate to tg-app instances by either manually placing files ssl_cert.crt and ssl_private_key.key in /home/testgrinder/tg-app/config/provision on tg-app instances, or via the User Data mechanism. Both ways are described in Configuration Files.

Make sure the SSL certificate is issued to the domain to which tg-app is configured to respond (see DOMAIN_WEB in .env Configuration File)

Once SSL certificate is supplied and tg-app instances are restarted, you should no longer see a security warning when accessing testgrinder.

Modifying ssl_cert.crt and ssl_private_key.key

You may modify the SSL certificate files using the following commands:

• Substitute my-tg-app with public DNS name of tg-app

• cat commands below are used to copy text from the console input to the files; after invoking the command, paste the contents of the file, and then complete the action with Ctrl+D

$ ssh ubuntu@my-tg-app
$ sudo su - testgrinder
$ cd ~/tg-app/config/provision
$ cat > ssl_cert.crt
$ cat > ssl_private_key.key

Make sure that ssl_private_key.key is only readable by the user:

$ chmod 600 ssl_private_key.key
$ ls -la ssl_private_key.key 
-rw------- 1 testgrinder testgrinder 3272 Nov 10 14:09 ssl_private_key.key