User Conflict

In Alpacon, a user conflict refers to a UID (User ID) conflict between an existing system user and an Alpacon user. This page explains the causes and solutions for such conflicts.

Cause of Conflict

Conflicts typically arise due to UID duplication. The following steps may lead to a conflict:

An existing user is already present on the server before using Alpacon
The Alpacon agent is installed and connected
A system user already exists with the same UID as the specified IAM user, but with a different username
The IAM user attempts to use websh, webftp, or deploy shell features

If the UID is already assigned to another system user, the IAM user will be unable to use the above features. When a conflict occurs, an error message will be displayed. You can also identify the conflicting user on the Server detail page under the Access tab.

Resolution

Alpacon is intentionally designed not to resolve user conflicts automatically, ensuring that users retain full control and avoid unintended changes.

After logging into the server, use the following commands with sudo privileges:

🔍 Check UID

cat /etc/passwd

✅ Option 1: Delete the existing user

# Delete user only
sudo userdel <USER_NAME>
 
# Delete user and home directory
sudo userdel -r <USER_NAME>

✅ Option 2: Change the existing user's UID

sudo usermod -u <NEW_UID> <USER_NAME>

⚠️ Warning

These operations may impact system behavior. Please proceed with caution and only after confirming there are no side effects. AlpacaX is not responsible for any issues caused by executing these commands.

Agent Synchronization

After resolving conflicts, you must synchronize the agent to ensure Alpacon reflects the changed user information. Click the Synchronize button at the top of the server details page to update to the latest status. The respective IAM user will then be able to use websh, webftp, and deploy shell functionalities normally.

User Delete Overview