Skip to main content

Using HTTPS troubleshooting in SuperOps

Updated this week

HTTP troubleshooting allows you to securely access the web-based interfaces (HTTP/HTTPS services) of your monitored network devices directly through SuperOps. This feature uses a secure reverse proxy tunnel, meaning you don't need direct network access, VPNs, or open ports on the device's firewall to establish a connection.

Prerequisites

Before you begin, please ensure the following requirements are met.

For Your Workstation:

  • Operating System: Windows 10 (or higher) or macOS 11 Big Sur (or higher).

  • Software: The SuperOps Remoting Software application must be installed.

SuperOps Remoting Software Installation:

  • How to get it: The software is available directly from the network device page. Select your installer file based on your Operating System and ensure that you download and install the Remoting application before starting your first HTTP remote session.
    ​


    ​

  • Installation Directory:

    • Windows: C:\ProgramData\SuperOpsRemote\

    • macOS: /Users/Shared/SuperOpsRemote/
      ​

  • Log Files: Diagnostic logs are written to:

    • Windows: C:\ProgramData\SuperOpsRemote\logs\superopsremoting.log

    • macOS: /Users/Shared/SuperOpsRemote/logs/superopsremoting.log

  • First-time setup: The first time you run the software, it will automatically download necessary dependencies, including a dedicated Chromium browser. This one-time installation may take a few moments, depending on your network speed. If the connection fails on the first try due to this installation time, simply try connecting again.

πŸ“ Note:

Ensure the following domains are whitelisted based on your region:

For US Domain:

  • Probe side: us-wsproxy.superops.ai

  • Technician side: us-superopsproxy.superops.ai, us-wsproxy.superops.ai

For EU Domain:

  • Probe side: eu-wsproxy.superops.ai

  • Technician side: eu-superopsproxy.superops.ai, eu-wsproxy.superops.ai

How to Use HTTP Troubleshooting

  1. Navigate to the specific network device's page you want to access.

  2. Click the Remote button at the top-right corner of the page and select either HTTP or HTTPS from the protocol options listed.
    ​

  3. By default, HTTPS uses port 443 and HTTP uses port 8080. You can enter a custom port if the service on the target device uses a different one. If you want to access a specific path, you can include the path name in the path field.

  4. Click Connect to initiate the session. The system will establish a secure tunnel through the SuperOps Probe.

  5. Once the tunnel is established, the SuperOps Remoting Software will launch a dedicated Chromium browser window, loading the device's web interface.
    ​

  6. Your active session will be listed in the "Active Connections" panel within the SuperOps UI.
    ​


    ​

Managing and Terminating a Session

You can end an HTTP Remoting session in two ways:

  • Close the browser window: Simply closing the dedicated Chromium browser window will automatically terminate the secure tunnel. You can use keyboard shortcuts to exit:

    • Windows: Alt + F4

    • macOS: Command + Q

  • Abort from the UI: Click the Abort button next to the relevant session in the "Active Connections" panel. This will terminate the tunnel, but you will still need to close the browser window manually.

Browser Controls:

The remote session opens in a clean, focused browser window without the standard address bar or controls.

  • Back Button: To navigate back, move your cursor to the top-left corner of the window, and a "Back" button will appear.

  • Reload Page: Use keyboard shortcuts to refresh the page:

    • Windows: F5

    • macOS: Command + R

Auditing and Logs

Every HTTP Remoting session start and end event is recorded for security and auditing purposes. You can view the complete history of connections for any device by navigating to its page and clicking the Asset Activity tab.

Limitations

Please be aware of the following limitations:

  • Session Duration: A single session is valid for a maximum of 1 hour for security purposes. If you need more time, you can start a new session.

  • Probe Concurrency: A single SuperOps Probe can support a maximum of 10 active HTTP Remoting connections at one time.

  • User Concurrency: A single user can only have one active connection to a specific device on a specific port. However, you can connect to the same device on different ports, and multiple users can connect to the same device and port simultaneously.

Frequently Asked Questions (FAQ)

Installation & Setup

Q1: Where do I get the SuperOps Remoting Software?

The software is available directly within the SuperOps platform. Navigate to a device page, click the "Remote" button, select HTTP/HTTPS, and you will see a "Download & Install" button to get the installer for your operating system.

Q2: What are the system requirements?

The software requires Windows 10 (or higher) or macOS 11 (Big Sur) (or higher). You must have administrative rights to install it.

Q3: Why does the first launch take a few minutes?

During the first execution, the software downloads and installs necessary dependencies. This is a one-time setup. If this process takes too long (e.g., over 5 minutes), the initial connection token may expire, causing the connection to fail. If this happens, simply initiate a new connection. The software will resume the installation and use a fresh token.

Connection & Usage

Q4: I get an error or a "Page Not Found" message. What should I check?

Connection errors can have several causes. Please verify the following:

  • Probe Status: The SuperOps Probe managing the device must be online.

  • Target Device Status: The target device must be online and reachable by the Probe.

  • Service Status: Ensure the HTTP/HTTPS service is running on the device at the specified port and protocol.

  • Pop-up Blockers: Your web browser may block the pop-up that launches the remoting software. Check your address bar for a pop-up blocker icon and choose to always allow pop-ups from SuperOps.

  • Firewalls: The target device's firewall may be blocking connections. Ensure the required domains are whitelisted.

  • Connection Limits: A Probe can only handle 10 concurrent sessions. You may need to wait for an existing session to end.

  • Existing Session: You can only have one active connection to a specific device and port. Check your "Active Connections" list.

Q5: Why does the browser display "Chrome is being controlled by automated test software"?

This is expected. SuperOps uses browser automation technology to establish and manage the secure tunnel in a controlled environment. This message is a standard notification and does not affect the security or functionality of your session.

Q6: I clicked "Abort" in the UI, but the browser is still open. Is this normal?

Yes. The "Abort" button only terminates the secure tunnel connection. It does not close the browser application on your machine. You must close the window manually using the keyboard shortcuts (Alt+F4 on Windows, Command+Q on macOS).

Security & Limitations

Q7: Is the connection to my device secure?

Yes. The connection is authenticated using a short-lived, unique token, and all traffic is relayed through a secure tunnel via the SuperOps Probe.

Q8: Why does my connection disconnect after 1 hour?

For security, each session has a maximum duration of one hour. This helps prevent unauthorized access if a workstation is left unattended. You can start a new connection immediately if you need more time.

Did this answer your question?