EasyDCIM Documentation
Back Home
Free Trial Request Get Started

Support Team Access

Installation & Configuration

# Support Team Access

In certain situations, the EasyDCIM support team may require access to the server with the EasyDCIM system installed. SSH access enables quicker and more effective troubleshooting by examining system services and custom logs.

WARNING

Support Team Access controls SSH access inside the EasyDCIM Docker containers, not SSH access to the host operating system. The App and Remote Agent containers have separate SSH services exposed on the following TCP ports:

  • 50223 - EasyDCIM App container
  • 50222 - Remote Agent container

The host's SSH service is separate and is not enabled or disabled by this setting. The App and Remote Agent access settings are managed separately. Make sure that ports 50223 and 50222 are allowed by the host firewall and any external security groups.

# Access management from the backend section

In order to allow the support team to access the container SSH services, you need to go to EasyDCIM's advanced settings. To do this, select 'Basic' → 'System Access' from the side menu.

In this section, you will find a button to enable or disable support access to the Docker containers:

  • Enable Support Team Access - this option will be accessible if establishing the access is doable. Enable it to allow our support team to connect to the relevant Docker container. The EasyDCIM App container uses port 50223, while the Remote Agent container uses port 50222.
  • Disable Support Team Access - this option will be accessible if the access has already been established. Disable it to remove support access from the relevant container. This does not change SSH access to the host.

# Access management from the command line

It is possible to manage access to the container SSH services from the command line if the backend section is not accessible. Such a situation may occur, for example, in case of problems with the web server or database.

Please input the following lines into the command line to enable or disable support access to the Docker containers:

  • Enable Support Team Access for the EasyDCIM App container (port 50223): 
    easydcim-control app shell -- sudo bash /opt/easydcim/scripts/support/access.sh enable
  • Disable Support Team Access for the EasyDCIM App container (port 50223): 
    easydcim-control app shell -- sudo bash /opt/easydcim/scripts/support/access.sh disable

For the Remote Agent container (port 50222), use the corresponding commands:

  • Enable Support Team Access: 
    easydcim-control agent shell -- sudo bash /opt/easydcim_remote/system/scripts/support/access.sh enable
  • Disable Support Team Access: 
    easydcim-control agent shell -- sudo bash /opt/easydcim_remote/system/scripts/support/access.sh disable

# Workflow

When enabling access to the container SSH services, the script performs the following actions:

  • Removes legacy or duplicate EasyDCIM support keys from the relevant container's /root/.ssh/authorized_keys file.
  • Adds the current EasyDCIM support public key to the relevant container.
  • Restricts use of the key to connections originating from the EasyDCIM company VPN address 91.192.166.30.
  • Preserves unrelated SSH keys already configured by the server administrator.
  • Creates a backup at /root/.ssh/authorized_keys.easydcim-support.bak inside the relevant container.

When disabling access, the script removes current and legacy EasyDCIM support keys from the relevant container while preserving unrelated entries. Restarting the host SSH server is not required for changes to authorized_keys.

# Rotating active support access

After EasyDCIM announces a support-key rotation, servers with active support access should have access disabled and then enabled again. This removes the previous EasyDCIM support key and installs the current restricted key.

If the SSH server observes a different source address because of NAT or an SSH gateway, the restricted key will be refused. Contact EasyDCIM Support before changing the allowed source address.

# Current public key

Fingerprint:

SHA256:O5q8ROLLpN9A4jPX+bDx06sKl87GLMIohcPbIseUmUY

Restricted authorized_keys entry:

from="91.192.166.30",no-agent-forwarding,no-X11-forwarding ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILAop58p3ZHIp+GRGZdC0nk76AZWMzFmDW0KGVr3VJUB EasyDCIM-Support-Team-2026-07