ThreatExploit Documentation logoThreatExploit Documentation logo ThreatExploit Documentation
Infrastructure Management Connecting and Managing Servers

Managing your infrastructure should be straightforward. Whether you are connecting to an existing machine or provisioning a new one, the Studio provides a centralized dashboard to add servers, monitor their health, and control their lifecycle.

Image

This guide walks you through connecting a new server and managing its state (like starting, stopping, and restarting).

Adding a New Server

To connect a new server to your environment, you'll need its IP address and the appropriate port numbers.

Image
  1. 1

    Open the Add Server modal

    Navigate to the Studio page and click the button to add a new server. This will open the ADD NEW SERVER window.

  2. 2

    Enter server details

    Fill in the connection details for your machine. You can use the default ports unless your server is configured differently.

  3. 3

    Save the connection

    Click ADD SERVER to save your configuration. The server will now appear in your server list and become your active selection.

Connection Settings

When adding a server, you will be prompted for the following information:

FieldDescriptionDefault
Display NameA friendly name to help you identify the server (e.g., Production Server).None
Server Host/IPThe internal or external IP address of your server (e.g., 10.0.0.5).None
API PortThe port used for standard HTTP requests.9741
gRPC PortThe port used for high-performance gRPC communication.9742

If your server is hosted within the same private network as your application, use its internal IP address for faster, more secure communication.

Managing Server State

Once your servers are connected, they will appear in the Servers Table. This table gives you a quick overview of each server's Name, Status, External IP, and Region.

Server Lifecycle

A server moves through different states depending on the actions you take.

stateDiagram-v2
    direction LR
    Stopped --> Transitioning : Start
    Transitioning --> Running : Ready
    Running --> Transitioning : Stop / Restart
    Transitioning --> Stopped : Terminated

Available Actions

You can control a server directly from the Actions column in the table. The primary buttons (Start/Stop) change dynamically based on the server's current status.

For additional commands, click the More actions (⋮) dropdown menu next to the primary button.

ActionWhere to find itDescription
StartPrimary ButtonBoots up a stopped or suspended server.
StopPrimary ButtonSafely halts a running server.
Restart⋮ DropdownReboots a running server.
Reset⋮ DropdownForce-resets the server. Note: Disabled while the server is transitioning.
Delete⋮ DropdownRemoves the server connection from your dashboard.

Deleting a server removes it from your Studio dashboard entirely. If you just want to pause billing or temporarily take it offline, use the Stop action instead.

Frequently Asked Questions

Why is the Reset button disabled?

The Reset button is temporarily disabled when a server is in a transitioning state (such as PROVISIONING, STAGING, or STOPPING). Wait for the server to reach a stable RUNNING status before attempting to reset it.

What is the difference between API and gRPC ports?

The API Port handles standard web traffic (HTTP/REST), which is great for general requests. The gRPC Port is used for high-speed, low-latency communication between services. Both are required for the Studio to fully communicate with your server.