Connection issues

Troubleshooting guide for server connection issues.

When server status shows Disconnected

Server status may show Disconnected for different reasons. Check the following scenarios to resolve it yourself.

1. Server is powered off or shut down

If the server is stopped, Alpacon cannot maintain a connection.

What to do:

  1. Server power and boot status check
  2. After server is running, wait briefly for Alpamon agent to reconnect automatically
  3. If status remains Disconnected, check agent status

2. When network connection to Alpacon is broken

The Alpamon agent connects to Alpacon over outbound HTTPS/WSS. If the server’s network blocks this or the network is down, status will show Disconnected.

What to do:

  1. Server outbound internet access check (e.g. curl -I https://alpacon.io or workspace endpoint)
  2. Firewall or proxy outbound HTTPS (443) and WSS allowance check (see Network requirements)
  3. If using a proxy, set HTTP_PROXY and HTTPS_PROXY on the server
  4. After fixing network or firewall, wait for agent to reconnect; if not, restart the agent or CLI agent restart

3. Agent not installed or not running

If the agent is not installed, was removed, or the agent process is not running, the server will show Disconnected.

What to do:

  1. On the server, verify Alpamon agent is installed and running (e.g. systemctl status alpamon on Linux)
  2. If not installed, install using installation script or instructions from Server connect
  3. If installed but not running, start or restart the agent (e.g. systemctl start alpamon or systemctl restart alpamon on Linux). See Server register for more commands
  4. For agent-specific problems, see Agent issues

When unable to connect to Websh

Console button is not available

Websh access is only available when the server is Connected to Alpacon. The Console button for Websh access is displayed only for connected servers.

What to do:

Terminal closes during a Websh session

The terminal may close unexpectedly while you are using Websh. Alpacon provides workspace admins with a remote session termination feature. A Staff or higher admin can terminate a user’s active Websh session at their discretion when they deem it necessary for security—in that case, the user’s terminal is closed.

What to do:

  • Check if workspace admin remotely terminated the session
  • If server is still Connected, start a new Websh session from server list or Websh page