This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

How to allow permanent access to webcam for HTTP website?

  • 3 uphendule
  • 1 inale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu stbear11

more options

I'm a developer of intranet enterprise app. The app works through HTTP and requires webcam access to make photos of clients. Right now, employees use outdated FF 50, and I need to convince the management to upgrade the version to current. HTTPS is required for webcam access starting with FF 68. We've got over 300 app installations, and HTTPS is not viable in our situation. I've found two preferences in about:config, media.devices.insecure.enabled, media.getusermedia.insecure.enabled, and photo can be taken by clicking Allow every time. When I click "Remember this decision" checkbox, Allow button becomes disabled, and FF displays message "Your connection to this site is not secure. To protect you, Firefox will only allow access for this session".

App is hosted on one fixed internal IP address and users probably don't have access to Internet. Can I do something to fight this behavior? Users should be able to allow permanent access to webcam.

PS. Upgrade was delayed by https://github.com/mozilla/pdf.js/issues/2851 - we've used Adobe plugin instead. Last week I fixed the bug in our own copy of PDF.js. We will be upgrading to either FF 67 or the current version.

Update: found a workaround to remember the website. Click on Connection not secure icon, then More Information, then Permissions. You can set allow camera there, but FF ignores the setting and still shows popup in question.

I'm a developer of intranet enterprise app. The app works through HTTP and requires webcam access to make photos of clients. Right now, employees use outdated FF 50, and I need to convince the management to upgrade the version to current. HTTPS is required for webcam access starting with FF 68. We've got over 300 app installations, and HTTPS is not viable in our situation. I've found two preferences in about:config, media.devices.insecure.enabled, media.getusermedia.insecure.enabled, and photo can be taken by clicking Allow every time. When I click "Remember this decision" checkbox, Allow button becomes disabled, and FF displays message "Your connection to this site is not secure. To protect you, Firefox will only allow access for this session". App is hosted on one fixed internal IP address and users probably don't have access to Internet. Can I do something to fight this behavior? Users should be able to allow permanent access to webcam. PS. Upgrade was delayed by https://github.com/mozilla/pdf.js/issues/2851 - we've used Adobe plugin instead. Last week I fixed the bug in our own copy of PDF.js. We will be upgrading to either FF 67 or the current version. Update: found a workaround to remember the website. Click on Connection not secure icon, then More Information, then Permissions. You can set allow camera there, but FF ignores the setting and still shows popup in question.
Ama-screenshot ananyekiwe

Okulungisiwe ngu stbear11

All Replies (3)

more options

Hi there!

Click the cog icon next to the Permission heading.

Option on the Firefox menu

Click setting to make any changes.

https://www.wired.com/story/how-to-lock-down-websites-permissions-access-webcam/

more options
more options

See my update. Manual addition via workaround or through group policies doesn't work - Firefox ignores website being in allow list and shows up popup every time. I guess my option is to upgrade to FF 67 for now and switch to Chrome-based browser in future, which works fine with --unsafely-treat-insecure-origin-as-secure="10.32.200.127" switch.