# Embed webcam http/https, not working in Perspective **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [January 16, 2023, 2:30pm UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627 "2023-01-16T14:30:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [January 16, 2023, 2:30pm UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627/1 "2023-01-16T14:30:24Z")
Hi All, I'm trying to get a still photo from a web cam each time the session loads. Running into some issues with Chrome and Edge. Firefox and Safari seem to work OK with http URL. I can get it working in Chrome using https, but at the camera does not have any certificates so I need to open the picture in another tab and accept the possible danger. I can then load the image. Using http in Chrome. I can't see the picture in the Perspective session, but I can right click and select open in a new tab and see the photo. Buying a SSL certificate is not an option. Any suggestions? Also tried iFrame with no luck. source: [http://ip/cgi-bin/api.cgi?cmd=Snap&user=usr&password=passwd&width=840&height=680](http://ip/cgi-bin/api.cgi?cmd=Snap&user=usr&password=passwd&width=840&height=680) source: [https://ip/cgi-bin/api.cgi?cmd=Snap&user=usr&password=passwd&width=840&height=680](https://ip/cgi-bin/api.cgi?cmd=Snap&user=usr&password=passwd&width=840&height=680) ---
**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\ **Post date:** [January 16, 2023, 3:21pm UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627/2 "2023-01-16T15:21:34Z")
the fileupload component should ba able to use the camera, any other way is meh. Also Im not pressing those links, but i already see a mayor issue with them. user & password should never be inside the link! ---
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [January 16, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627/3 "2023-01-16T16:13:18Z")
The file upload, as in the drag and drop component? Its not the phone camera, but a designated camera. The URL is pointing nowhere, so it will not work. I will - if possible make user and password parameters outside the url when an if there is a solution of the security issue. ---
**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\ **Post date:** [January 17, 2023, 7:20am UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627/4 "2023-01-17T07:20:36Z")
If its a designated camera, i suppose it connected to the gateway network? you could try to control it from the gateway then instead of the client. Let the client send a message to the gateway to take a pic and there execute some local (bash) script that remotely controls the camera. [system.util.execute - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/system.util.execute) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 17, 2023, 6:30pm UTC](https://forum.inductiveautomation.com/t/embed-webcam-http-https-not-working-in-perspective/68627/5 "2023-01-17T18:30:04Z")
You could set up a reverse-proxy to route incoming requests to the camera, transparently. You could even have it issue the request parameters, so that external users don't see the request. You could then add a self-signed cert to the reverse proxy, or set up Let's Encrypt (free, if you own a domain name). You could also probably do that with Ignition using Webdev, but something like nginx or Traefik could do it a bit easier and without buying an additional module.