Skip to main content
Skip table of contents

HIAB Remote Support


Purpose

This document describes the remote support service.

Introduction

The remote support function allows the Outpost24 support to remotely access a customers HIAB through SSH.

Requirement

To connect to Outpost24 remote support servers, the HIAB must be able to communicate outward to osrss.outpost24.com on TCP port 22, as well as have deep packet inspection disabled in the  firewall.

Note

Any proxy need to be disable for the connection as this could interfere.

Activate Remote Support

By activating Remote Support, you allow the support team at Outpost24 to access the back-end of your HIAB. This is mainly used for troubleshooting if any issues occur during the operational use of your HIAB.

There are two ways of doing this, via the HIAB Console or through the HIAB GUI.

HIAB Console

HIAB Console Main Menu

  1. To Activate the Remote Support in the HAIB Console, press c while in the Main menu.
    To Deactivate, press c again.
  2. Retrieve a SSH-key by navigating to https://<HIABIP>/sbc_id_rsa.pub, where the HIABIP is the IP of the actual HIAB. By entering this URL you download a file which contains the key.
  3. Copy + Paste the the given public key into a support ticket.
HIAB GUI
  1. Log in to the HIAB GUI.
  2. Go to Main Menu > Support.
  3. Right click Enabling Remote Support allows support to connect to the machine.



  4. When the remote support has been enabled, please provide us with the public key located under Main Menu -> Support.



  5. Copy + Paste the the given public key into your support ticket.





Copyright

© 2024 Outpost24® All rights reserved. This document may only be redistributed unedited and unaltered. This document may be cited and referenced only if clearly crediting Outpost24® and this document as the source. Any other reproduction and redistribution in print or electronically is strictly prohibited without explicit permission.

Trademark

Outpost24® and OUTSCAN™ are trademarks of Outpost24® and its affiliated companies. All other brand names, product names or trademarks belong to their respective owners.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.