How to configure SSL

Configuring SSL/TLS in Glassfish & QMetry

Default configuration in Glassfish & changes required in QMetry configuration

By default, http-listener-2 is configured in Glassfish in server-config. The port set is 8181 as shown in the below image.


If one tries to access the QMetry application, e.g. URL https://localhost:8181/qmetry , then QMetry login page opens as below .

When you enter the credentials, an error message “Invalid Client” pop's up, as highlighted in below mentioned image.

To solve this issue, the domain URL has to be set in the client table in QMetry database as follow :

Login to database and update domain name as follows: 

    • /opt/mysql/bin/mysql -uroot -pqmetry
    • mysql> USE qmetry;
    • mysql> UPDATE client SET domain='localhost:8181' limit 1;
    • mysql> \q

If default ports used are : 80 for HTTP & 443 for HTTPS, then port number will not present in the domain URL, so no change is required in the domain URL.


The documentation regarding Certificates & SSL in Payara 4.1 Open Source edition is in the Security Guide.


Starting QMETRY 

You can access QMETRY from any computer with network access to your QMETRY server by opening a supported web browsers on the computer and visiting this URL: 

  • http://<domain_name>:8080/qmetry 


  • <domain_name> is the name which you gave at the time of installation.
  • The default QMetry Login Credentials are: admin/qmetry1@#4, automation/qmetry1@#4

QMetry On-Demand

If you do not have the resources to set up and maintain a QMetry installation locally, consider QMetry hosted solution. We can run and maintain your installation of QMetry, handling all the testing, monitoring and upgrading processes for you. For more information, please refer to the information about QMetry On-Demand on our website. 

Contact QMetry 

Please contact QMetry if you face any issues during installation. You can email us at which will automatically create a ticket in our support portal which will allow all of us to monitor the status on the issue until it is resolved. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk