[Termix] Termix build fails on ujpdate from 2.5.0 to 2.6.0

[frontend-report]

Script: Termix

Reported by: @j-inc

Guidelines

• Read and understood guidelines: yes
• Verbose mode used: yes

Issue occurs during: Script Update

Environment

• Linux distribution: Debian
• Proxmox version: 9.1
• Default settings: Yes
• Advanced settings: No
• Exact command: update

Description

Made no major configuration changes to the container, all prior updates have been successful, this is the first to fail.

I update via typing "update" in the bash terminal in the proxmox GUI and output claims the frontend and backend build successfully but termix fails to start. Rebooting the container also doesn't trigger a successful start.

Steps to reproduce

Be on Termix 2.5.0, type update, build fails.

Error output

✔️ Built Frontend
⏳ Building Backendnpm warn using --force Recommended protections disabled.
npm warn rebuild 4 packages have install scripts not yet covered by allowScripts. Run npm approve-scripts --allow-scripts-pending to review.
rebuilt dependencies successfully

termix@2.6.0 build:backend
tsc -p tsconfig.node.json && node -e "require('fs').copyFileSync('src/backend/package.json','dist/backend/package.json')"

✔️ Built Backend
⏳ Setting up Production Dependenciesnpm warn config only Use --omit=dev to omit dev dependencies from the install.
npm warn using --force Recommended protections disabled.
npm warn deprecated @ldapjs/protocol@1.2.1: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/change@1.0.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/attribute@1.0.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/asn1@1.2.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/asn1@2.0.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/controls@2.1.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/dn@1.1.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/filter@2.1.1: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated @ldapjs/messages@1.3.0: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md
npm warn deprecated ldapjs@3.0.7: This package has been decomissioned. See https://github.com/ldapjs/node-ldapjs/blob/8ffd0bc9c149088a10ec4c1ec6a18450f76ad05d/README.md

added 289 packages, and audited 290 packages in 2s

57 packages are looking for funding
run npm fund for details

2 high severity vulnerabilities

To address all issues, run:
npm audit fix

Run npm audit for details.
npm warn using --force Recommended protections disabled.
npm warn rebuild 4 packages have install scripts not yet covered by allowScripts. Run npm approve-scripts --allow-scripts-pending to review.
rebuilt dependencies successfully
npm warn using --force Recommended protections disabled.
✔️ Set up Production Dependencies
✔️ Updated Frontend Files
💡 The Nginx configuration may need to be updated for new features to work.

  Update Nginx configuration? [Y/n]: y

⏳ Updating Nginx Configurationnginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
✔️ Updated Nginx Configuration
⏳ Starting TermixJob for termix.service failed because of unavailable resources or another system error.
See "systemctl status termix.service" and "journalctl -xeu termix.service" for details.
✖️ in line 240: exit code 1 (General error / Operation not permitted): while executing command systemctl start termix

--- Last 20 lines of log ---
[2026-08-03 14:21:47] [OK] Deployed: termix (release-2.6.0-tag)
[2026-08-03 14:21:47] [INFO] Restoring data
[2026-08-03 14:21:47] [OK] Restored data
[2026-08-03 14:21:47] [INFO] Recreating Directories
[2026-08-03 14:21:47] [OK] Recreated Directories
[2026-08-03 14:21:47] [INFO] Migrating Database to new layout
[2026-08-03 14:21:47] [OK] Migrated Database to new layout
[2026-08-03 14:21:47] [INFO] Building Frontend
[2026-08-03 14:22:06] [OK] Built Frontend
[2026-08-03 14:22:06] [INFO] Building Backend
[2026-08-03 14:23:13] [OK] Built Backend
[2026-08-03 14:23:13] [INFO] Setting up Production Dependencies
[2026-08-03 14:24:16] [OK] Set up Production Dependencies
[2026-08-03 14:24:16] [INFO] Updating Frontend Files
[2026-08-03 14:24:16] [OK] Updated Frontend Files
[2026-08-03 14:24:16] [WARN] The Nginx configuration may need to be updated for new features to work.
[2026-08-03 14:25:02] [INFO] Updating Nginx Configuration
[2026-08-03 14:25:02] [OK] Updated Nginx Configuration
[2026-08-03 14:25:02] [INFO] Starting Termix
[2026-08-03 14:25:02] [ERROR] in line 240: exit code 1 (General error / Operation not permitted): while executing command systemctl start termix

[MickLesk]

@P3RF3CTION ? Again broken Script? Like every Version? ^^

[j-inc]

A snippet of what I see in logs:

root@termix:~# journalctl -xeu termix.service
░░ Subject: A start job for unit termix.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit termix.service has finished with a failure.
░░ 
░░ The job identifier is 3096 and the job result is failed.
Aug 03 14:28:04 termix systemd[1]: termix.service: Scheduled restart job, restart counter is at 35.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit termix.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 14:28:04 termix systemd[1]: termix.service: Failed to load environment files: No such file or directory
Aug 03 14:28:04 termix systemd[1]: termix.service: Failed to spawn 'start' task: No such file or directory
Aug 03 14:28:04 termix systemd[1]: termix.service: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit termix.service has entered the 'failed' state with result 'resources'.
Aug 03 14:28:04 termix systemd[1]: Failed to start termix.service - Termix Backend.
░░ Subject: A start job for unit termix.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit termix.service has finished with a failure.
░░ 
░░ The job identifier is 3170 and the job result is failed.
Aug 03 14:28:09 termix systemd[1]: termix.service: Scheduled restart job, restart counter is at 36.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit termix.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 03 14:28:09 termix systemd[1]: termix.service: Failed to load environment files: No such file or directory
Aug 03 14:28:09 termix systemd[1]: termix.service: Failed to spawn 'start' task: No such file or directory
Aug 03 14:28:09 termix systemd[1]: termix.service: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit termix.service has entered the 'failed' state with result 'resources'.
Aug 03 14:28:09 termix systemd[1]: Failed to start termix.service - Termix Backend.
░░ Subject: A start job for unit termix.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit termix.service has finished with a failure.
░░ 
░░ The job identifier is 3244 and the job result is failed.

I assure you, there's ample system resources.

[MickLesk]

Can you do following for more Output?

source /opt/termix/.env && /usr/bin/node /opt/termix/dist/backend/backend/starter.js

[j-inc]

It seems no .env file was created. /opt/termix/ is present, though.

root@termix:~# source /opt/termix/.env && /usr/bin/node /opt/termix/dist/backend/backend/starter.js
-bash: /opt/termix/.env: No such file or directory

For the second command:

root@termix:/opt/termix# /usr/bin/node /opt/termix/dist/backend/backend/starter.js
[2:43:02 PM] [INFO] [🚀] Termix backend initialization started [op:backend_init_start]
[2:43:02 PM] [INFO] [📦] Termix Backend starting - Version: 2.6.0 [op:startup]
[2:43:02 PM] [SUCCESS] [🗄️] JWT secret auto-generated and saved to .env [op:jwt_auto_generated]
[2:43:02 PM] [SUCCESS] [🗄️] Database key auto-generated and saved to .env [op:db_key_auto_generated]
[2:43:02 PM] [SUCCESS] [🗄️] Encryption key auto-generated and saved to .env [op:encryption_key_auto_generated]
[2:43:02 PM] [SUCCESS] [🗄️] Internal auth token auto-generated and saved to .env [op:internal_auth_auto_generated]
[2:43:02 PM] [INFO] [🗄️] Database layer pre-upgrade backup created [op:database_layer_preupgrade_backup_created]
[2:43:02 PM] [INFO] [🚀] SSL not enabled - skipping certificate generation [op:ssl_disabled_default]
[2:43:02 PM] [SUCCESS] [🚀] SSL setup completed [op:backend_init_ssl]
[2:43:02 PM] [ERROR] [🗄️] Database decryption authentication failed - possible causes: wrong DATABASE_KEY, corrupted files, or interrupted write [op:database_buffer_decryption_auth_failed]
Error: Unsupported state or unable to authenticate data
    at Decipheriv.final (node:internal/crypto/cipher:172:29)
    at DatabaseFileEncryption.decryptDatabaseToBuffer (file:///opt/termix/dist/backend/backend/utils/database-file-encryption.js:223:26)
    at async initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:48:41)
    at async initializeCompleteDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:125:5)
    at async Module.initializeDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:2351:5)
    at async file:///opt/termix/dist/backend/backend/starter.js:122:9
[2:43:02 PM] [ERROR] [🗄️] Failed to initialize memory database [op:db_memory_init_failed]
Error: Database decryption authentication failed. This usually means:
1. DATABASE_KEY has changed or is missing from ./db/data/.env
2. Encrypted file was corrupted during write (system crash/restart)
3. Metadata file does not match encrypted data

Debug info:
- DATA_DIR: ./db/data
- .env file exists: true
- .env file readable: true
- DATABASE_KEY in environment: true
Original error: Unsupported state or unable to authenticate data
    at DatabaseFileEncryption.decryptDatabaseToBuffer (file:///opt/termix/dist/backend/backend/utils/database-file-encryption.js:258:23)
    at async initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:48:41)
    ... 2 lines matching cause stack trace ...
    at async file:///opt/termix/dist/backend/backend/starter.js:122:9 {
  [cause]: Error: Unsupported state or unable to authenticate data
      at Decipheriv.final (node:internal/crypto/cipher:172:29)
      at DatabaseFileEncryption.decryptDatabaseToBuffer (file:///opt/termix/dist/backend/backend/utils/database-file-encryption.js:223:26)
      at async initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:48:41)
      at async initializeCompleteDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:125:5)
      at async Module.initializeDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:2351:5)
      at async file:///opt/termix/dist/backend/backend/starter.js:122:9
}
[2:43:02 PM] [INFO] [🗄️] Database encryption diagnostic info [op:diagnostic_info_generated]
[2:43:02 PM] [ERROR] [🗄️] Database encryption diagnostic completed - check logs above for details [op:db_encryption_diagnostic_completed]
[2:43:02 PM] [ERROR] [🚀] Failed to initialize backend services [op:startup_failed]
Error: Database decryption failed: Database decryption authentication failed. This usually means:
1. DATABASE_KEY has changed or is missing from ./db/data/.env
2. Encrypted file was corrupted during write (system crash/restart)
3. Metadata file does not match encrypted data

Debug info:
- DATA_DIR: ./db/data
- .env file exists: true
- .env file readable: true
- DATABASE_KEY in environment: true
Original error: Unsupported state or unable to authenticate data. This prevents data loss.
    at initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:116:19)
    at async initializeCompleteDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:125:5)
    at async Module.initializeDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:2351:5)
    at async file:///opt/termix/dist/backend/backend/starter.js:122:9 {
  [cause]: Error: Database decryption authentication failed. This usually means:
  1. DATABASE_KEY has changed or is missing from ./db/data/.env
  2. Encrypted file was corrupted during write (system crash/restart)
  3. Metadata file does not match encrypted data
  
  Debug info:
  - DATA_DIR: ./db/data
  - .env file exists: true
  - .env file readable: true
  - DATABASE_KEY in environment: true
  Original error: Unsupported state or unable to authenticate data
      at DatabaseFileEncryption.decryptDatabaseToBuffer (file:///opt/termix/dist/backend/backend/utils/database-file-encryption.js:258:23)
      at async initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:48:41)
      ... 2 lines matching cause stack trace ...
      at async file:///opt/termix/dist/backend/backend/starter.js:122:9 {
    [cause]: Error: Unsupported state or unable to authenticate data
        at Decipheriv.final (node:internal/crypto/cipher:172:29)
        at DatabaseFileEncryption.decryptDatabaseToBuffer (file:///opt/termix/dist/backend/backend/utils/database-file-encryption.js:223:26)
        at async initializeDatabaseAsync (file:///opt/termix/dist/backend/backend/database/db/index.js:48:41)
        at async initializeCompleteDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:125:5)
        at async Module.initializeDatabase (file:///opt/termix/dist/backend/backend/database/db/index.js:2351:5)
        at async file:///opt/termix/dist/backend/backend/starter.js:122:9
  }
}

FWIW, I've repeatedly restored the LXC from a backup from yesterday and reproduce the same errors. The .env file existed in the directory pre-update.

[MickLesk]

Why no env ? Restore your Backup and Take a Look again?

[j-inc]

Let me be more clear: the backup from last night has an .env file. After I attempt to update the functioning backup (and the same error occurs) the .env file is no longer in the directory. That file appears to be lost post-update.

[MickLesk]

Can you Update again with your Backup state?