Register a server

Register your server with Alpacon to manage it from your browser.

What is a user server?

A user server refers to a server operated by an individual user or a group of users. Alpacon supports registration and management of both:

• Cloud-based servers (e.g., AWS, GCP, Azure)
• On-premise servers operated directly by the user

Even in hybrid environments where different types of servers coexist, Alpacon offers a consistent UI/UX to manage all servers seamlessly in one place.

Key benefits:

• Unified management interface for all server types
• Consistent experience regardless of server location
• No distinction needed between cloud and on-premise
• Centralized control and monitoring

Registration process

Server registration follows 3 steps:

1. Registration method—Choose a registration method
2. Server information—Enter server details (varies by method)
3. Installation guide—Run the generated installation script or command

Registration methods

Registration by script

Register a server by running a generated installation script directly on the target server.

Step 1: Select registration method

1. Click Servers in the left sidebar
2. Click Register Server button in the top right
3. Select Registration by script

Step 2: Enter server information

• Server name (required)—Lowercase letters, numbers, hyphens, and underscores only (max 20 characters)
• Platform (required)—Select the server OS (Debian-based or Red Hat-based)
• Access control—Define which groups can access this server:
  • All groups—All workspace members (Alpacon users group)
  • Admins only—Workspace administrators only
  • Specific groups—Select one or more groups

Step 3: Install agent

An installation script is automatically generated and displayed on screen.

1. Copy the generated installation script
2. Connect to your target server’s terminal
3. Paste and run the script
4. Wait for installation to complete (takes about 1-2 minutes)
5. Return to the server list and verify the status shows Connected

Script example:

curl -sSL https://install.alpacon.io/agent | sudo bash -s -- --token YOUR_TOKEN

Registration with token

Register a server using a pre-issued server registration token and a CLI command. This method is ideal for automating server registration across multiple servers.

Step 1: Select registration method

1. Click Servers in the left sidebar
2. Click Register Server button in the top right
3. Select Registration with token

Step 2: Enter server information

• Platform (required)—Select the server OS
• Server name—Lowercase letters, numbers, hyphens, and underscores only (max 20 characters). Used as a name prefix for the server being created. If not specified, the server’s hostname is used.
• Registration token—Select an existing token from the dropdown, or click Create new token to create one on the spot

Step 3: Install agent

A token-based CLI installation command is generated and displayed on screen.

1. Copy the generated command
2. Run it on the target server
3. Wait for installation to complete
4. Verify the status shows Connected in the server list

AWS Cloud-Init (coming soon)

Register servers automatically using AWS Cloud-Init user data during EC2 instance provisioning.

Terraform (coming soon)

Use the Terraform provider to provision and register servers simultaneously as part of your Infrastructure as Code workflow.

Ansible (coming soon)

Use an Ansible playbook to automate server registration across your fleet.

Supported platforms

Debian-based:

• Ubuntu
• Debian

Red Hat-based:

• RHEL (Red Hat Enterprise Linux)
• CentOS
• Amazon Linux
• Rocky Linux
• Fedora
• Oracle Linux

Requirements

Server requirements:

• Linux-based operating system
• Internet connection
• sudo privileges (for installation)

Network:

• Outbound HTTPS connections allowed (port 443)
• Access to Alpacon API servers

Troubleshooting

Connection status shows “Disconnected”:

1. Check agent status:

sudo systemctl status alpamon

2. Restart agent:

sudo systemctl restart alpamon

3. Check logs:

sudo journalctl -u alpamon -n 50

Installation fails:

• Verify sudo privileges
• Check internet connection
• Confirm platform is supported

Security considerations

Agent communication:

• All communication is TLS encrypted
• Only outbound connections from server to Alpacon required
• No inbound ports need to be opened

Authentication:

• Each server uses a unique token for authentication
• Token is only used during installation and stored securely

Next steps

After registering your server:

• Connect to servers
• Control server access
• Monitor server status