This article applies to a HTTPS configuration of BioStar 2 server.
Normally if you have a HTTPS configuration for your web server, you can apply the certificate to make your connection secure.
Refer to the article below to make that configuration:
How to configure HTTP or HTTPS protocol
Caution: If you choose not to apply the HTTPS certification, your browser will experience slowness and various unknown side effects.
You will also always be prompted with the error message below
We have updated this article with a tool for Biostar 2.6 and above ONLY
Basic Troubleshooting
If you have applied the certification based on the instructions of the following article: How to configure HTTP or HTTPS protocol but still see the Not secure error as above, try stopping all chrome processes and launch chrome again.
Further Troubleshooting
Cause
If the issue still persists, we can suspect the issue below:
1. The server PC has more than one ethernet interface, and the server IP has been registered based on the redundant ethernet interface.
2. The server did not have an IP when BioStar Server was installed so the server IP was registered as 127.0.0.1
3. The server PC IP has been changed after the initial installation.
Checking the Certificate
In this case you can see if the registered server IP is the issue by checking the applied certificate.
1. Click on the Not secure button.
2. Click the Invalid link on the Certificate tab.
3. Check the Issued to / by IP and see if that is your server IP.
If it has the wrong server IP, proceed with the instructions below.
If it has the correct server IP, follow the Basic Troubleshooting section above again.
Changing the Server IP Register
UPDATE (Using HTTPS Certificate reset tool) :
We created a tool to simplify the above HTTPS Reset process.
Please download the following tool.
NOTE: 1. Above tool works only for BioStar2 v2.6 and above.
Procedure:
1. Run ResetHttpsCertificate.exe tool.
2. Select server IP address from the dropdown list and click [Update HTTPS Certificate].
3. Wait for a while until the tool finishes with the reconfiguration (about 2~3 minutes).
4. Once the configuration is finished, click [OK] from the diaglog box.
5. BioStar2 Enrollment Certification window will appear.
Input server IP and port then click [Enrollment].
6. Restart browser to apply the certificates.
Changing the Server IP Register
Manual Method
Caution: This configuration is irrelevant if you're using a HTTP web server connection.
Do not follow this procedure if you're using HTTP web server connection. Making this change will make your DB inaccessible.
1. Open BioStar Setting.
2. Stop all services.
3. Open the BioStar 2 installation path.
(default BioStar 2 installation 64bit path is : C:\Program Files\BioStar 2(x64) )
4. back up the following files in a safe location: system.conf, setting.conf
5. Delete the following files in the following folder C:/Program Files/BioStar 2(x64)/nginx/conf/
biostar_cert.crt
biostar_cert.key
biostar_cert.p12 (Biostar 2.6 or above only)
keystore.jks (BioStar 2.6 or above only)
6. If you have multiple ethernet interfaces, turn off all ethernet interfaces in the Control Panel except for the main one that has the server IP.
7. Run command prompt with admin privileges.
8. Change your directory to the BioStar 2 folder as below:
cd C:\Program Files\BioStar 2(x64)
9. Copy the command below and press enter.
biostar-server.exe install_information en true v2 443 51212
10. (For BioStar 2.6 and above only) Copy the command below and press enter.
java -cp "C:\Program Files\BioStar 2(x64)\util";"C:\Program Files\BioStar 2(x64)\util\lib\google-collect-1.0.jar";"C:\Program Files\BioStar 2(x64)\util\lib\gson-2.8.2.jar" BioStarSetup "C:\Program Files\BioStar 2(x64)"
11. Restore your backed up system.conf file and setting.conf file in C:\Program Files\BioStar 2(x64)
12. Open setting.conf file with Notepad.
13. Change the IP of the ssl_addr to the correct server IP.
14. Save the setting.conf file.
15. Open BioStar Setting.
16. Start your BioStar services.
17. Log in to BioStar web client and apply the certificate.
18. Check that the Not Secure error does not appear again and that the certificate IP is correct.
(remember to kill all chrome processes on task manager when restarting Chrome)