A browser console permits you to access a remote server using a web browser. Browser consoles enter the following functionality:
- Playback console recording
- Clipboard access
- Shared Drive
To add or launch a browser console, enable Browser Consoles for the client. A user can configure browser console settings using the user preference setting option.
User permissions define the following user capabilities:
- A user with Consoles Manage permission can add, edit, or remove a console.
- A user with Consoles View permission can view consoles created by other users.
- An HTML-enabled browser is required to launch a browser console.
- Browser consoles and their related features should be activated for the client.
- Verify that you have whitelisted the needed IPs as listed in Public IP addresses.
- Whitelisted IPs must have both inbound and outbound communication to access remote consoles.
- Device Manager and Console Manage permissions are enabled.
- The protocol is enabled on the target device, such as SSH, RDP, or Telnet.
- Port numbers are checked for launching the remote console.
- The agent and gateway are active on the target device or on the managed device.
- Login information is available for the target device.
- The target device status is active.
When launching a console on a gateway, enter the localhost IP address:
|Gateway Version||Agent Version||Features available|
|7.00||7.00||All features except SSH-based shared drive|
|8.00 and above||8.00 and above||All features|
The protocols supported by the browser console are:
Add Browser consoles for SSH/Telnet/RDP
Add the details of the remote device on which you want to launch a console. You can also edit or delete the configured remote console.
Go to Infrastructure.
Click the category to which the target resource belongs.
Click the required resource name.
From the resource Overview page, click the settings icon and select Add Console.
Click +Add to add a new set of console details. You can also edit the existing sample details to add a remote console. The existing sample details are configured for the agent.
Configure the following information on the consoles window:
- Connector: Element (Agent or Gateway) managing the target device.
- Protocols: Protocol that you want to use to communicate with the target device.
- Port: Port that transmits and receives data. The port numbers vary with Services.
- Username: Login username of the target device. Username is optional.
- Password: Login password of the target device.
- IP Address: IP Address of the target device.
- Name: Name of the console. You can add Name in the RDP IP address format of the target device and port number. For example,
The console is added to the console list.
Click Add Consoles again from the settings icon to add more consoles or to remove existing consoles.
Launching browser consoles for RDP
Add the remote device information to launch a browser console. Remote device information must be provided to launch browser consoles.
It is recommended that you select the Network Level Authentication (NLA) option on the remote Windows device for secure communication. RDP operates on NLA which is a secured channel of communication. Connecting users must be aware of NLA settings on the target device.
If NLA is enabled on the target device, connecting users can access the target device only with particular credentials. The following are considerations for adding consoles:
- With domain: (Mandatory) Provide username, password, and domain values for credential sets.
- Without domain: (Mandatory) Provide username and password for manual login.
If NLA is disabled on the target device, connecting users can access the target device without authenticating. Username and password fields can be left empty in manual login.
NLA is required for Windows 2016 and above versions.
Launching Secure Shell consoles
To launch Secure Shell (SSH) consoles:
Go to Infrastructure and select the resource name for which you want to add the console.
Click Launch Remote Console.
Click SSH or SSH with certificate.
From the Launch Browser Console dialog box, provide Ticket ID/Alert ID to associate the console activity to a ticket and add Activity Log Notes.
Select the applicable checkbox:
- Use Credentials: If credentials are available in credentials sets, select the option from the Credentials drop-down option.
- I have Credentials: If you have credentials, select the option. For SSH, enter username and password. For SSH with certificate, select Choose File to upload Certificate and enter a Pass Phrase. Private keys are required for SSH keypair-based authentication.
Enter your credentials in the browser console.
The target remote device is now connected, enabling activities to be performed on the device.
Launching Telnet consoles
- Go to Infrastructure and click the resource name for which you want to add the console.
- Click Launch Remote Console.
- Click Telnet.
- From the Launch Browser Console dialog box, enter the Ticket ID/Alert ID to associate the console activity to a ticket and add an Activity Log Note.
- Click OK.
Disconnecting browser consoles
Disconnect from the session when you are done.
<Ctrl><Alt><Shift>to display the Clipboard window.
- From the username drop-down menu, click Disconnect.
The session is disconnected.
Launching consoles from different pages in OpsRamp
In addition to launching a console from the Infrastructure page, you can also launch consoles from the alert details and gateway details pages.
Launch console from the alert details page
- Go to Alerts.
- Click the required alert ID. The Alert Details page displays.
- Click the consoles icon.
- Click the browser console icon to launch the console you want.
Launch console from the Gateway Details page
- Go to Setup > Resources > Management Profiles.
- Click the required management profile name.
- In the Management Gateway Details section, click the Gateway UUID, which displays the GATEWAY DETAILS page.
- Click the Consoles icon.
- Click the browser-based console icon to launch the console.