Skip to main content
Help & Support

Supported Browsers

For the best experience, use Google Chrome — the recommended browser for octoja. Other Chromium-based browsers such as Microsoft Edge are fully supported too.

The octoja web interface is browser-based. For the best experience, we recommend Google Chrome — it is the browser octoja is developed and tested against most closely. Other Chromium-based browsers, such as Microsoft Edge, Brave, Opera, and Vivaldi, are fully supported too. Whichever you use, choose a current stable release paired with an operating system that the browser vendor still supports.

BrowserSupported baselineNotes
Google ChromeCurrent stable releaseRecommended — best overall experience
Microsoft EdgeCurrent stable releaseFully supported; a solid choice on Windows
Other Chromium-based browsers (for example Brave, Opera, or Vivaldi)Current stable releaseFully supported as part of the Chromium family. Privacy features these browsers add on top of Chromium can interfere with octoja — if a download does not start or a page misbehaves in Brave, disable its Shields for your octoja instance (or the equivalent protection feature in other browsers) and try again

Not fully supported

octoja may still work in other browsers, but they are not fully supported. When you sign in with one of them, the login page shows a blocking Unsupported browser warning that you have to acknowledge with I understand — continue anyway before continuing, and you may run into display glitches or features that don't work as expected. The acknowledgement is remembered in that browser for 24 hours; after that the warning appears again the next time you open the login page.

BrowserBehaviour
Mozilla FirefoxShows the unsupported-browser warning at sign-in
SafariShows the unsupported-browser warning at sign-in
Any other browser outside the Chromium familyShows the same warning at sign-in, naming your browser as Your current browser

Clipboard sync in Remote Desktop is the clearest place where the browser family shows. Chromium browsers offer a lasting clipboard permission, so text you copy on either side reaches the other on its own; while that permission is still open or has been blocked, a clipboard button appears in the session toolbar. Firefox and Safari do not offer it, so send your clipboard across with Paste in the toolbar — or with Type Clipboard on sign-in and UAC screens, where pasting is blocked.

Not supported

BrowserReason
Internet ExplorerRetired by Microsoft; the octoja interface needs a current browser engine
Microsoft Edge LegacyRetired by Microsoft; use the Chromium-based Microsoft Edge instead
Browser versions outside the vendor support windowSecurity and compatibility issues

Mobile browsers

The octoja dashboard works on modern mobile browsers, but is optimised for desktop screens. For the best experience on mobile, use a current Google Chrome release on a tablet or larger screen.

If you see “Something went wrong”

Browser extensions that modify web pages can interfere with the octoja web interface. This has been observed with 3CX Click2Call and website translation extensions, among others. The error can have other causes too.

  1. Disable these extensions for your octoja instance and reload the page.
  2. If the page works again, re-enable the extensions one at a time to identify the cause. Leave the offending extension disabled for octoja or exclude your octoja instance in its settings.
  3. If the error occurs with extensions disabled, contact support and describe which page is affected.

Required browser settings

  • JavaScript must be enabled
  • Cookies must be allowed for the octoja domain
  • Pop-up blockers should allow the octoja domain for features that open in a separate window, such as the device toolbox
  • Clipboard access should be allowed for the octoja domain so Remote Desktop can sync copied text with the remote machine
  • Site data should be kept between visits — octoja stores your table column layouts and the state of the sidebar in the browser, so a private window or a browser set to clear site data on exit starts from the defaults every time