Troubleshooting
SSL/TLS Certificate Errors
SSL/TLS Certificate Errors
Secure connections to the remote server present the opportunity for several errors when attempting to connect. The errors typically involve the certificates used when connecting via SSL or TLS. This section highlights some of the most common issues involving the certificates.
Error | Cause / Solution |
|
|
"SSL certificate problem: self | One of the situations that prevent a successful connection is not |
signed certificate in certificate | having the correct Certificate Authority certificates installed on |
chain" | the remote server. Zebra requires that the Zebra Root Certificate |
| Authority and the Zebra Subordinate Certificate Authority be |
| installed on the remote server. This error typically indicates that |
| only one of the Zebra Certificate Authority certificates is |
| installed on the remote server. |
|
|
"SSL certificate problem: unable to | One of the situations that prevent a successful connection is not |
get local issuer certificate" | having the correct Certificate Authority certificates installed on |
| the remote server. Zebra requires that the Zebra Root Certificate |
| Authority and the Zebra Subordinate Certificate Authority be |
| installed on the remote server. This error typically indicates that |
| neither of the Zebra Certificate Authority certificates are |
| installed on the remote server. |
|
|
"SSL certificate problem: | This error indicates that the remote server’s certificate has |
certificate has expired" | expired. This is typically an indication that the printer’s date |
| and/or time are incorrect as the Zebra certificates are typically |
| issued for long durations. Check that rtc.date and rtc.time |
| are set correctly. |
| Note • For printers that do not have a battery to store the |
| Real Time Clock (RTC) value, the date will be restored |
| to the default value upon a power cycle. The default |
| value depends upon how the rtc.date SGD is managed. |
| If it has never been set then it will default to the |
| firmware build date (the value in appl.date). |
| Otherwise, the value in rtc.date will default to the |
| value that it was last set to. This does not mean the value |
| of the rtc.date when it was power cycled. It means that |
| when a user sets rtc.date that becomes the new default |
| value. |
| If the printer has a battery, then the rtc.date is never |
| default and continues to track the date as expected. |
|
|
39
1/20/15 |
