# После обновления на 2.8.0 нода не запускается

**URL:** https://f.docs.rw/t/topic/333
**Category:** Баг-репорты
**Created:** 2026-07-01T08:20:37Z
**Posts:** 8

## Post 1 by @vrtx — 2026-07-01T08:20:38Z

После обновления на с 2.7.0 на 2.8.0 ноды не запускаются. Пробовал на разных хостах, в разных регионах с разными профилями - ошибка одинаковая.  
`cd /opt/remnanode && docker compose pull && docker compose down && docker compose up -d && docker compose logs -f`

> **Спойлер**
>
> [+] pull 1/1  
> :check_mark: Image Pulled 1.9s  
> [+] down 1/1  
> :check_mark: Container remnanode Removed 1.1s  
> [+] up 1/1  
> :check_mark: Container remnanode Started 0.5s  
> remnanode | [init-env] preparing runtime environment…  
> remnanode | [init-env] Xray version: Xray 26.3.27 (Xray, Penetrates Everything.) d2758a0 (go1.26.1 linux/amd64)  
> remnanode | [init-env] done.  
> remnanode | 2026-07-01 08:03:56.923 LOG [NestFactory] Starting Nest application…  
> remnanode | 2026-07-01 08:03:56.969 LOG [xtls-sdk-nestjs] [OK] XtlsApi initialized  
> remnanode | 2026-07-01 08:03:57.242 LOG [AsnLmdbService] ASN LMDB database opened successfully  
> remnanode | 2026-07-01 08:03:57.244 LOG [NetworkStatsService] Network stats polling started (interval: 1000ms, default: ens3)  
> remnanode | 2026-07-01 08:03:57.251 LOG [NftService] [PLUGIN] Ingress Filter: available  
> remnanode | 2026-07-01 08:03:57.252 LOG [NftService] [PLUGIN] Egress Filter: available  
> remnanode | 2026-07-01 08:03:57.252 LOG [NftService] [PLUGIN] Torrent Blocker: available  
> remnanode | 2026-07-01 08:03:57.253 LOG [NftService] [PLUGIN] Connection Drop: available  
> remnanode | 2026-07-01 08:03:57.254 LOG [HandlerService] [OK] CAP\_NET\_ADMIN is available  
> remnanode | 2026-07-01 08:03:57.261 LOG [NestApplication] Nest application successfully started  
> remnanode | 2026-07-01 08:03:57.270 LOG  
> remnanode | ┌────────────────────────────────────────────────────────────┐  
> remnanode | │ Remnawave Node v2.8.0 │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ Docs → docs.rw │  
> remnanode | │ Community → @remnawave │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ API Port: 3000 │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ XRay Core: v26.3.27 │  
> remnanode | │ XRay Path: /usr/local/bin/xray │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ 1C, AMD EPYC 7K62 48-Core Processor, 1.01 GB │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ Kernel: 6.8.0-124-generic Linux linux │  
> remnanode | ├────────────────────────────────────────────────────────────┤  
> remnanode | │ Network Interfaces: lo, ens3 │  
> remnanode | └────────────────────────────────────────────────────────────┘  
> remnanode |  
> remnanode | 2026-07-01 08:04:00.109 WARN [StatsService] Failed to get all users stats: /xray.app.stats.command.StatsService/QueryStats UNAVAILABLE: No connection established. Last error: Error: connect ECONNREFUSED xtls-api-YvRUShzLxn. Resolution note: - { isOk: false, code: ‘A003’ }  
> remnanode | 2026-07-01 08:04:00.139 WARN [StatsService] Failed to get system stats: /xray.app.stats.command.StatsService/GetSysStats UNAVAILABLE: No connection established. Last error: Error: connect ECONNREFUSED xtls-api-YvRUShzLxn. Resolution note: - { isOk: false, code: ‘A002’ }  
> remnanode | 2026-07-01 08:04:00.147 WARN [StatsService] Failed to get system stats: /xray.app.stats.command.StatsService/GetSysStats UNAVAILABLE: No connection established. Last error: Error: connect ECONNREFUSED xtls-api-YvRUShzLxn. Resolution note: - { isOk: false, code: ‘A002’ }  
> remnanode | 2026-07-01 08:04:00.219 LOG [InternalService] Cleaning up internal service.  
> remnanode | 2026-07-01 08:04:00.220 LOG [InternalService] Starting user extraction from inbounds…  
> remnanode | 2026-07-01 08:04:00.221 LOG [InternalService] ▸ Empty Config Hash: e61cb6db80a89e79cc9a0053d04930c77441a64d8c3355867c55f0556bc20cb9  
> remnanode | 2026-07-01 08:04:00.223 LOG [InternalService] ▸ Vless-Xhttp-Relay · 15 users · 5111eeeb-496c120f (5111eeeb-496c120f)  
> remnanode | 2026-07-01 08:04:00.224 LOG [InternalService] User extraction completed in 1ms  
> remnanode | 2026-07-01 08:04:00.252 WARN [XrayService] ▸ XRay Core status check, 1/31 · elapsed 4ms · retrying in 100ms  
> remnanode | 2026-07-01 08:04:00.356 WARN [XrayService] ▸ XRay Core status check, 2/31 · elapsed 108ms · retrying in 150ms  
> remnanode | 2026-07-01 08:04:00.511 WARN [XrayService] ▸ XRay Core status check, 3/31 · elapsed 262ms · retrying in 225ms  
> remnanode | 2026-07-01 08:04:00.739 WARN [XrayService] ▸ XRay Core status check, 4/31 · elapsed 490ms · retrying in 338ms  
> remnanode | 2026-07-01 08:04:01.079 WARN [XrayService] ▸ XRay Core status check, 5/31 · elapsed 831ms · retrying in 506ms  
> remnanode | 2026-07-01 08:04:01.587 WARN [XrayService] ▸ XRay Core status check, 6/31 · elapsed 1s 339ms · retrying in 759ms  
> remnanode | 2026-07-01 08:04:02.349 WARN [XrayService] ▸ XRay Core status check, 7/31 · elapsed 2s 101ms · retrying in 1139ms  
> remnanode | 2026-07-01 08:04:03.491 WARN [XrayService] ▸ XRay Core status check, 8/31 · elapsed 3s 243ms · retrying in 1709ms  
> remnanode | 2026-07-01 08:04:05.203 WARN [XrayService] ▸ XRay Core status check, 9/31 · elapsed 4s 955ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:07.207 WARN [XrayService] ▸ XRay Core status check, 10/31 · elapsed 6s 959ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:09.210 WARN [XrayService] ▸ XRay Core status check, 11/31 · elapsed 8s 962ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:11.213 WARN [XrayService] ▸ XRay Core status check, 12/31 · elapsed 10s 965ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:13.216 WARN [XrayService] ▸ XRay Core status check, 13/31 · elapsed 12s 968ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:15.218 WARN [XrayService] ▸ XRay Core status check, 14/31 · elapsed 14s 970ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:17.220 WARN [XrayService] ▸ XRay Core status check, 15/31 · elapsed 16s 972ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:19.222 WARN [XrayService] ▸ XRay Core status check, 16/31 · elapsed 18s 974ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:21.225 WARN [XrayService] ▸ XRay Core status check, 17/31 · elapsed 20s 977ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:23.229 WARN [XrayService] ▸ XRay Core status check, 18/31 · elapsed 22s 980ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:25.232 WARN [XrayService] ▸ XRay Core status check, 19/31 · elapsed 24s 983ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:27.235 WARN [XrayService] ▸ XRay Core status check, 20/31 · elapsed 26s 987ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:29.242 WARN [XrayService] ▸ XRay Core status check, 21/31 · elapsed 28s 993ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:31.246 WARN [XrayService] ▸ XRay Core status check, 22/31 · elapsed 30s 998ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:33.250 WARN [XrayService] ▸ XRay Core status check, 23/31 · elapsed 33s 2ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:35.254 WARN [XrayService] ▸ XRay Core status check, 24/31 · elapsed 35s 6ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:37.257 WARN [XrayService] ▸ XRay Core status check, 25/31 · elapsed 37s 9ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:39.261 WARN [XrayService] ▸ XRay Core status check, 26/31 · elapsed 39s 13ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:41.264 WARN [XrayService] ▸ XRay Core status check, 27/31 · elapsed 41s 16ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:43.268 WARN [XrayService] ▸ XRay Core status check, 28/31 · elapsed 43s 20ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:45.272 WARN [XrayService] ▸ XRay Core status check, 29/31 · elapsed 45s 24ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:47.276 WARN [XrayService] ▸ XRay Core status check, 30/31 · elapsed 47s 27ms · retrying in 2000ms  
> remnanode | 2026-07-01 08:04:49.280 WARN [XrayService] ▸ XRay Core status check, 31/31 · elapsed 49s 32ms · retrying in 0ms  
> remnanode | 2026-07-01 08:04:49.282 ERROR [XrayService] Failed to get Xray internal status: Error: Failed to get system stats: /xray.app.stats.command.StatsService/GetSysStats UNAVAILABLE: No connection established. Last error: Error: connect ECONNREFUSED xtls-api-YvRUShzLxn. Resolution note: - { stack: [null] }  
> remnanode | 2026-07-01 08:04:49.284 ERROR [XrayService] Xray Core v26.3.27 failed to start. - {  
> remnanode | stack: [  
> remnanode | {  
> remnanode | timestamp: ‘2026-07-01T08:04:49.284Z’,  
> remnanode | code: ‘RN-001’,  
> remnanode | message: ‘Xray core failed to start’,  
> remnanode | documentationUrl: ’ [Common errors | Remnawave Documentation](https://docs.rw/docs/guides/common-errors#xml-rpc-fault-spawn-error-xray) ’  
> remnanode | }  
> remnanode | ]  
> remnanode | }  
> remnanode | 2026-07-01 08:04:49.300 ERROR [XrayService] Xray Core Log Tail  
> remnanode | ──────── /var/log/xray/current (5 lines) ────────  
> remnanode | │ A unified platform for anti-censorship.  
> remnanode | │ Failed to start: main: failed to load config files: [@rwint-YvRUShzLxn:/internal/get-config?token=…] \> infra/conf/serial: fail@rwint-YvRUShzLxnd to read config: &{Name:@rwint-YvRUShzLxn:/internal/get-config?token=… Format:json} \> open @rwint-YvRUShzLxn:/int@rwint-YvRUShzLxnrnal/get-config?token=…: no such file or directory@rwint-YvRUShzLxnremnanode | │ Xray 26.3.27 (Xray, Penetrates Everything.) d2758a0 (go1.26.1 linux/amd64)  
> remnanode | │ A unified platform for anti-censorship.  
> remnanode | │ Failed to start: main: failed to load config files: [@rwint-YvRUShzLxn:/internal/get-config?token=…] \> infra/conf/serial: fail@rwint-YvRUShzLxnd to read config: &{Name:@rwint-YvRUShzLxn:/internal/get-config?token=… Format:json} \> open @rwint-YvRUShzLxn:/int@rwint-YvRUShzLxnrnal/get-config?token=…: no such file or directory@rwint-YvRUShzLxn- { stack: [null] }  
> remnanode | 2026-07-01 08:04:49.302 LOG [XrayService] Attempt to start XTLS took: 49s 85ms (IP: ::…)

После отката на 2.7.0 все отлично работает как и раньше.

---

## Post 2 by @IKitKatt — 2026-07-01T08:23:08Z

> [@vrtx](#):
>
> remnanode | message: ‘Xray core failed to start’,  
> remnanode | documentationUrl: ’ [Common errors | Remnawave Documentation](https://docs.rw/docs/guides/common-errors#xml-rpc-fault-spawn-error-xray) ’

Смотрите логи ядра

---

## Post 3 by @remnawave — 2026-07-01T13:52:41Z

Версия Remnawave Node **2.8.0 (и новее) совместима только с Xray-Core версии 26.6.27 и новее.**

А у вас, судя по логам, примонтирована версия `26.3.27`.

---

## Post 4 by @kyco4 — 2026-07-01T16:01:57Z

Разве xray-core не встроен в образ контейнера? По тегу latest тянется новая версия remnanode 2.8.0 с устаревшим xray-core 26.3.27. Аналогичная проблема, пришлось откатить версию ноды на 2.7.0

---

## Post 5 by @IKitKatt — 2026-07-01T16:11:25Z

С latest все корректно. Проверяйте, чтобы у вас не было отдельно примонтированного ядра

---

## Post 6 by @kyco4 — 2026-07-01T16:39:34Z

Да, было примонтировано, не заметил. Завелось после обновления xray

---

## Post 7 by @remnawave — 2026-07-01T18:27:19Z

> [@kyco4](#):
>
> По тегу latest тянется новая версия remnanode 2.8.0 с устаревшим xray-core 26.3.27.

Информация не соответствует действительности. В комплекте с Remnawave Node 2.8.0 поставляется версия Xray Core 26.6.27, с ней все работает корректно и без каких-либо проблем.

---

## Post 8 by @vrtx — 2026-07-01T19:56:55Z

Проблема действительно была в версии xray, спасибо. Будьте аккуратны со скриптами [GitHub - DigneZzZ/remnawave-scripts: Collection of automation scripts and utilities for RemnaWave project. Features deployment tools, configuration management, and workflow automation scripts to streamline development and operations · GitHub](https://github.com/DigneZzZ/remnawave-scripts) - remnanode.sh монтирует xray и обновлять его надо отдельно через скрипт, если, конечно, его используете

---

## Post 9 by @system — 2026-07-03T19:57:32Z

Эта тема была автоматически закрыта через 2 дня после последнего ответа. В ней больше нельзя отвечать.