SSL Certificate errors when connecting to the Impinj R700 Reader

When the Impinj R700 are configured to use HTTPS as the default communication mechanism you may encounter SSL certificate errors when browsing to the reader's webpage or using the reader configuration REST API to make HTTP requests to the reader.  This occurs because the SSL certificate on the reader is self signed. Most browsers and HTTP libraries produce warnings when using encrypted HTTPS communication with a client that has a self signed certificate.  To continue you will to accept the certificate error to continue on to the webpage or for the HTTP request to complete.

Notice

In Impinj R700 Firmware version 7.4.0.240, the default mechanism for connecting to the reader was changed from HTTP to HTTPS. This change has been reverted in firmware version 7.4.1.240.

Below are some examples of web browser you may encounter, and how to proceed.

For additional details on how to configuring HTTP and HTTPS behavior, please refer to article "How to configure HTTP and HTTPS on the Impinj R700"

Firefox:

mceclip3.png

Chrome:

mceclip0.png

Another message you might encounter is:

mceclip0.png

Microsoft Edge:

mceclip1.png

 

This message is appearing because the Impinj R700 reader is using HTTPS encryption with self-signed certificates.   Please click the "Advanced" button in the browser to get another message about the certificate.

 

Firefox:

mceclip3.png

Chrome:

mceclip4.png

Microsoft Edge:

mceclip2.png

Click the appropriate link or button to continue and be asked for the root user credentials.

 

Firefox:

mceclip5.png

Chrome:

mceclip6.png

Microsoft Edge:

mceclip7.png

Once you enter the root user credentials and click the OK/Sign in button, you will be able to see the Impinj R700 web UI.

Firmware version 8.x

8.0webUI.png

Firmware version 7.x

mceclip8.png

 

Other Messages You May Run Into

One other message you may run into could prevent you from accessing the webpage altogether.  

Chrome:

Please clear your cookies, cache, and use the chrome://net-internals/#hstspage to query and delete entries for your host.domain to resolve this issue.

mceclip0.png

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.