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

Need a way to lock the browser down for Kiosks

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by Mkll

more options

Hello,

We have been using Firefox for several kiosk devices utilizing the mKiosk extension but now it seems our computers are starting to auto-migrate to the new Firefox Quantum. The main purpose of the mKiosk extension was to lock the browser completely down so the user could not access other pages, settings, bookmarks, etc.

With this new migration mKiosk, as well as most other extensions are no longer compatible which has completely compromised our network.

I am hoping someone knows how to completely lockdown this new Firefox using settings (advanced) or another extension. Also, is there anyway to completely halt the migration to the rest of our network so we do not have this problem at all?

This has put us in a very critical position so I would appreciate any quick assistance

Thank you!

Hello, We have been using Firefox for several kiosk devices utilizing the mKiosk extension but now it seems our computers are starting to auto-migrate to the new Firefox Quantum. The main purpose of the mKiosk extension was to lock the browser completely down so the user could not access other pages, settings, bookmarks, etc. With this new migration mKiosk, as well as most other extensions are no longer compatible which has completely compromised our network. I am hoping someone knows how to completely lockdown this new Firefox using settings (advanced) or another extension. Also, is there anyway to completely halt the migration to the rest of our network so we do not have this problem at all? This has put us in a very critical position so I would appreciate any quick assistance Thank you!

All Replies (1)

more options

Hello, try running Firefox in headless mode: https://developer.mozilla.org/en-US/Firefox/Headless_mode