# Raspberry pi ssl configuration problems **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective, vision\ **Created:** [April 24, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828 "2023-04-24T16:18:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Skylar\_Sabo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/skylar_sabo/32/42622_2.png) [@Skylar\_Sabo](https://forum.inductiveautomation.com/u/Skylar_Sabo)\ **Post date:** [April 24, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/1 "2023-04-24T16:18:07Z")
Hello everyone, we are currently experiencing some issues with our Raspberry Pi's and Ignition connections/SSL configurations. We have a SSL enabled gateway and are trying to access perspective pages from a Raspberry Pi. We run the legacy.sh script to run vision clients of some dashboards on the Pi's as well. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/d/5d9ff0dd0cd6a5361680eda71468b0711c6a28b6.png) Our first problem is that when we enable the 'force secure redirect' on the gateway, our Pi's cannot connect because of the newly configured SSL. Our second problem is that perspective pages are unsecure on the Pi's but are secure on other connections (just not the pi's). When attempting to connect to the perspective page, we are met with the page being unsecure and asked to proceed manually while on the Pi's. However, when navigating to the address from a PC, we do not get the unsecure message, and the connection is fine. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/d/cd44589a923047f3746398eab8052f59e8db138c.png) We tried putting our root CA certificates into the Raspberry Pi's SSL folders and then restarting the Pi, but that did not help. Our goal is to have the same output as on a PC and for the perspective pages to be secure. We are not sure what direction to go from here Can anyone suggest a solution or a direction to troubleshoot this issue? Any help would be greatly appreciated. Thank you in advance. If anyone has any general knowledge or things to keep in mind with ssl and configuring devices please do not hesitate to mention any of that too. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 24, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/2 "2023-04-24T16:22:44Z")
Can you click on that "Not secure" in Chrome for more info about why it's not trusted? Does the certificate have the hostname you're using to access the gateway in it? Have you tried adding the root certificate to Chrome itself instead of the OS trust store? ---
**Author:** ![Skylar\_Sabo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/skylar_sabo/32/42622_2.png) [@Skylar\_Sabo](https://forum.inductiveautomation.com/u/Skylar_Sabo)\ **Post date:** [April 24, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/3 "2023-04-24T16:26:19Z")
This is the not secure message on the PI ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/6/a6d8278040b4695a53cf0fbbe7fc3813f335c169.png) And this is the same message while on the PC ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/1/01086552b48cf10d066d68d3727e27f34e488a1f.png) I have not tried adding the root certs to chrome itself, will try and let you know results ---
**Author:** ![Skylar\_Sabo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/skylar_sabo/32/42622_2.png) [@Skylar\_Sabo](https://forum.inductiveautomation.com/u/Skylar_Sabo)\ **Post date:** [April 24, 2023, 4:40pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/4 "2023-04-24T16:40:54Z")
Adding the root certificate chain to chrome fixed this issue with perspective but, while having the certificate chain in the os and chrome would I be able to have 'force secure redirect' enabled and have a connection while on a vision client running the legacy.sh script on a pi too? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 24, 2023, 4:45pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/5 "2023-04-24T16:45:22Z")
You may also need to add the certificate to Java's cacerts keystore. ---
**Author:** ![Skylar\_Sabo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/skylar_sabo/32/42622_2.png) [@Skylar\_Sabo](https://forum.inductiveautomation.com/u/Skylar_Sabo)\ **Post date:** [April 24, 2023, 4:54pm UTC](https://forum.inductiveautomation.com/t/raspberry-pi-ssl-configuration-problems/72828/6 "2023-04-24T16:54:59Z")
> [@Kevin.Herron](#): > > Java's cacerts keystore Thank you! So I now currently have the chain in my java's cacerts keystore, the os's and chromium's for all this to work