After updating to version 2026.02.2 and higher, the platform does not work

Problem

After updating the platform to version 2026.02.2 or higher, the following symptoms occur:

the platform web interface does not open;
the vm_box container constantly restarts.

Cause

Starting with version 2026.02.2, the platform architecture includes a new container, vm_back. As a result, configuration templates for some services have been moved from the vm_box container to the new vm_back container. For example, the ip-fabric configuration template. The issue occurs due to custom patches (YAML files) that reference files in the vm_box container. This causes the vm_box container to fail to start correctly and constantly restart. For more information about patches, see Container modification via patches.

Diagnosis

To confirm the cause of the issue:

Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
Check the status of the vm_box container:
```
docker ps --format "table {{.Names}}\t{{.Status}}" | grep vm_box
```
Example output
```
vm_box   Restarting (2) 7 seconds ago
```
Indicator of the issue: the vm_box container status shows it is constantly restarting (Restarting).
Check the logs of the vm_box container:
```
docker logs -n 10 vm_box
```
Example output
```
sed: can't read /opt/ispsystem/vm/scripts/kvm/etc/frr_routereflector_bgpd.tmpl: No such file or directory
```
Indicator of the issue: the container logs contain errors about missing files or directories that have been moved to the vm_back container.
Check for custom patches:
1. Open the platform configuration file:
```
cat /opt/ispsystem/vm/config.json
```
2. Examine the Patches section. This section lists all patches, including custom ones:
  Example output
```
"Patches":{"channelp":{"base64_compose":"c2VydmljZXM6CiAgdm1fYm94OgogICAgZVfVElNRU9VVDogMC4zCg=="}
```
  Examples of system patch names:
  for the “Integration with DNSmanager 6” module — vmdnsmgr;
  for the “Integration with IPmanager 6” module — vmipmgr.
  Indicator of the issue: the configuration contains patches with names not included in the list of system patches (e.g., channelp, ip-fabric).

Decode the contents of the custom patch:

echo <base64_code> | base64 -d

Example command

echo c2VydmljZXM6CiAgdm1fYm94OgogICAgZVfVElNRU9VVDogMC4zCg== | base64 -d

Example output

services:
  vm_box:
    command:
      - bash
      - -c
      - sed -i -E "s/(neighbor fabric capability extended-nexthop)/\1\n neighbor fabric ebgp-multihop 255/;s/(neighbor fabric route-map IPV4_EXPORT out)/\1\n neighbor fabric route-map IPV4_IMPORT in/;s/(neighbor fabric route-map IPV6_EXPORT out)/\1\n neighbor fabric route-map IPV6_IMPORT in/;s/(route-map IPV4_EXPORT permit 5)/route-map IPV4_IMPORT permit 5\n\!\n\1/;s/(route-map IPV6_EXPORT permit 5)/route-map IPV6_IMPORT permit 5\n\!\n\1/" /opt/ispsystem/vm/scripts/kvm/etc/frr_routereflector_bgpd.tmpl && /supervisor.sh

Indicator of the issue: the services section references the vm_box container.

Verify the patch functionality. For example, the issue is confirmed if you observe the following:
- the patch edits a file in the vm_box container, but this file no longer exists in the container;
- the patch copies a file to the vm_box container, but the file is no longer being copied.

Solution

To resolve the issue, replace the vm_box container with vm_back in the custom patch:

Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
Disable the target patch:
```
vm remove-patch -p=<patch_name>
```
Comment:
- <patch_name> — the unique name of the patch.

Edit the patch file:

Open the patch file.It is located in the /opt/ispsystem/vm/ directory and has a name like patch_*****.yaml.

In the services section, replace the vm_box container with vm_back.

Patch example after modifications

version: "3.5"
services:
  vm_back:
    command:
      - bash
      - sed -i -E "s/(neighbor fabric capability extended-nexthop)/\1\n neighbor fabric ebgp-multihop 255/;s/(neighbor fabric route-map IPV4_EXPORT out)/\1\n neighbor fabric route-map IPV4_IMPORT in/;s/(neighbor fabric route-map IPV6_EXPORT out)/\1\n neighbor fabric route-map IPV6_IMPORT in/;s/(route-map IPV4_EXPORT permit 5)/route-map IPV4_IMPORT permit 5\n\!\n\1/;s/(route-map IPV6_EXPORT permit 5)/route-map IPV6_IMPORT permit 5\n\!\n\1/" /opt/ispsystem/vm/scripts/kvm/etc/frr_routereflector_bgpd.tmpl && /supervisor.sh

Apply the new patch:
```
vm add-patch -p=<patch_name> -f=</path/to/patch.yaml>
```
Comment:
- <patch_name> — the unique name of the patch;
- </path/to/patch.yaml> — the path to the file containing the patch contents.
If multiple custom patches exist, repeat these steps for each patch.
Verify that the platform is functioning correctly.

Useful tips