# IP Camera Viewer, URLProxy, and Force Secure Redirect

**URL:** <https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [September 22, 2022, 2:09pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370 "2022-09-22T14:09:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnBomb](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johnbomb/32/38431_2.png) [@JohnBomb](https://forum.inductiveautomation.com/u/JohnBomb)\
**Post date:** [September 22, 2022, 2:09pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/1 "2022-09-22T14:09:50Z")

</div>

Hey all! I’m working on trying to better secure my Ignition Gateway, so I’d like to switch everything over to SSL communication. I’ve mostly got it figured out but I have one issue still remaining with some Vision windows that use the IP Camera Viewer.

My gateway has two network interfaces, one to the “controls” network (which includes the IP cameras) and the office network. The IP Camera Viewer block uses the Gateway’s URLProxy ([http://ignitiongateway-officenetwork:8088/main/system/urlproxy?url=http://webcamIPonControlsNetwork](http://ignitiongateway-officenetwork:8088/main/system/urlproxy?url=http://webcamIPonControlsNetwork)…) to access the camera feed so clients on the office network can see the cameras too. But these IP Camera Viewers break when I turn on Force Secure Redirect.

I’ve changed the URLs to ([https://ignitiongateway-officenetwork:8043/main/system/urlproxy?url=http://webcamIPonControlsNetwork](https://ignitiongateway-officenetwork:8043/main/system/urlproxy?url=http://webcamIPonControlsNetwork)…) but I still get an SSL exception error. If I pull the URL up in my web browser (https/8043) on the office network I can see the camera feed just fine, but for some reason the IP Camera Viewer in a Vision Window still can’t if Force Secure Redirect is on.

This is the error I get in IP Camera Viewer:  
 ![2022-09-22_07-43-48](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/d/7ddd79bf32dad7ac8f5b129ec35ca7d8225bd3a7.jpeg)

Any ideas how I can get this working? I tried toggling “Use Proxy Forwarded Headers” and that didn’t help.

---

<div class="post-metadata">

**Author:** ![plo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plo/32/33875_2.png) [@plo](https://forum.inductiveautomation.com/u/plo)\
**Post date:** [October 3, 2022, 10:32pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/2 "2022-10-03T22:32:10Z")

</div>

Hello JohnBomb,

Do you see the error in the Designer? I wonder if this is similar to this forum post - [Valid Certificate Path Problem](https://forum.inductiveautomation.com/t/valid-certificate-path-problem/26888)  
Where they were able to add the certificate to the Vision Clients in the `.ignition/clientlauncher-data/certificates` directory to authenticate there.

I suggest opening a Support to help troubleshoot this issue if it is possible or not. Please contact us here! We would like to review your Certificate and see what else we find in the logs  
[https://inductiveautomation.com/support/home/](https://inductiveautomation.com/support/home/)

---

<div class="post-metadata">

**Author:** ![JohnBomb](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johnbomb/32/38431_2.png) [@JohnBomb](https://forum.inductiveautomation.com/u/JohnBomb)\
**Post date:** [October 13, 2022, 2:51pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/3 "2022-10-13T14:51:46Z")

</div>

I see the error in Designer and in Vision.

The certificate is in `.ignition/clientlauncher-data/certificates` and Designer and Vision are both accessing the Gateway via https using the certificate. The camera views work fine when I connect via SSL and Force Secure Redirect is off. Its only once I force everything to SSL only that it breaks.

I thought it might be because the cameras are not SSL maybe it doesn't like the SSL urlproxy accessing a non-SSL site on the other side? But if I pull up the URL doing that (SSL from client to gateway, non-SSL from gateway to camera) in my web browser I can see the camera feed fine, the IP Camera Viewer just doesn't want to.

I'll open a ticket soon, I need some downtime in production to test and generate some more logs since I don't have a test environment. The last time I tried it has rolled off the log already.

Thanks!

---

<div class="post-metadata">

**Author:** ![TANVEER\_AHMAD](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@TANVEER\_AHMAD](https://forum.inductiveautomation.com/u/TANVEER_AHMAD)\
**Post date:** [December 27, 2022, 4:56am UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/4 "2022-12-27T04:56:31Z")

</div>

Hello John Bomp  
I am facing similar issue , have you resolved ?  
also try to find this **ignoreCertValidation=True** path

please reply

---

<div class="post-metadata">

**Author:** ![JohnBomb](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johnbomb/32/38431_2.png) [@JohnBomb](https://forum.inductiveautomation.com/u/JohnBomb)\
**Post date:** [December 28, 2022, 2:24pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/5 "2022-12-28T14:24:06Z")

</div>

Inductive confirmed this is a bug in the IP Camera Viewer module and that I'd have to wait for them to release a fix in a future Ignition update. They recommended using the web browser component module in the meantime as a workaround, but my company didn't pay for that in my license so you could use that if you have it.

---

<div class="post-metadata">

**Author:** ![TANVEER\_AHMAD](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@TANVEER\_AHMAD](https://forum.inductiveautomation.com/u/TANVEER_AHMAD)\
**Post date:** [December 29, 2022, 6:23am UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/6 "2022-12-29T06:23:47Z")

</div>

JahnBomb Thanks for update ❤ 🤔

---

<div class="post-metadata">

**Author:** ![JohnBomb](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johnbomb/32/38431_2.png) [@JohnBomb](https://forum.inductiveautomation.com/u/JohnBomb)\
**Post date:** [March 23, 2023, 1:18pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/7 "2023-03-23T13:18:37Z")

</div>

I was told this would be fixed in release 8.1.26

---

<div class="post-metadata">

**Author:** ![marwane.gannoun](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marwane.gannoun/32/15701_2.png) [@marwane.gannoun](https://forum.inductiveautomation.com/u/marwane.gannoun)\
**Post date:** [April 17, 2023, 7:55pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/8 "2023-04-17T19:55:07Z")

</div>

I have the same problem. Can I contact you in order to share with you the whole steps to solve this?  
Thanks.

---

<div class="post-metadata">

**Author:** ![Chris\_W](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chris\_W](https://forum.inductiveautomation.com/u/Chris_W)\
**Post date:** [October 28, 2024, 7:53pm UTC](https://forum.inductiveautomation.com/t/ip-camera-viewer-urlproxy-and-force-secure-redirect/64370/9 "2024-10-28T19:53:45Z")

</div>

Did you figure this out?
