12.25.1 now available

Aliysa_Enhance

Enhanced

cPanel imports are now able to complete where PostgreSQL is enabled on cPanel but not on Enhance, by skipping any PostgreSQL databases during the import process.
The search login on 'Customers' has been moved from UI code to API to improve performance on larger clusters.
Improved phpMyAdmin error reporting.
"Overrides" back heading now contains the primary domain of the website being edited.
getGlobalInstallableApps and getInstallableApps endpoints now return OpenClaw as a supported application. getInstallableApps returns applications subject to package restrictions.

Fixed

phpMyAdmin domain selection for resellers now ignores soft-deleted domains.
API will no longer accept syntactically invalid ".." in email local part.

JohnBee

Very nice!

Exporter3973

this update broke my cluster. the panel can telnet into app cluster at port 50000 but the file manager is broken.

in journalctl, the error is

Jul 29 08:56:47 prod-enhance-1 orchd[2062922]: 2026-07-29T08:56:47.229757Z ERROR ThreadId(05) orchd::error: Returning internal server error to the API: Error { kind: Internal, detail: None, msg: Some("Grpc Transport failed: \"transport error\"") }

so this is clearly in the app layer, not network issue. why the broken changes?

other finding: when i tried to access File Manager tab, i noticed one POST is getting http 500 return

https://panel-url/api/orgs/***/websites/***/access-tokens

something related to access token?

in master server (where panel also reside), ecp access-token list returned no error. however, inside the cluster member it has error.

root@enhance-panel-cluster-1:~# RUST_BACKTRACE=full ecp access-token list
thread 'main' panicked at ecp-cli/src/orchd.rs:209:56:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:     0x59e67c39b9ca - <unknown>
   1:     0x59e67be0cdcb - <unknown>
   2:     0x59e67c397b63 - <unknown>
   3:     0x59e67c39cbab - <unknown>
   4:     0x59e67c39c81b - <unknown>
   5:     0x59e67c39d342 - <unknown>
   6:     0x59e67c39d0b3 - <unknown>
   7:     0x59e67c39be79 - <unknown>
   8:     0x59e67c39cd94 - <unknown>
   9:     0x59e67bd80f53 - <unknown>
  10:     0x59e67bd80fdc - <unknown>
  11:     0x59e67bd80eb9 - <unknown>
  12:     0x59e67be6e3dd - <unknown>
  13:     0x59e67bf006b0 - <unknown>
  14:     0x59e67bed9865 - <unknown>
  15:     0x59e67c06df1c - <unknown>
  16:     0x59e67c0cd26f - <unknown>
  17:     0x59e67c0145bd - <unknown>
  18:     0x59e67c0a2a23 - <unknown>
  19:     0x59e67c0dec49 - <unknown>
  20:     0x59e67c38fe05 - <unknown>
  21:     0x59e67c014695 - <unknown>
  22:     0x7c0d2c62a1ca - <unknown>
  23:     0x7c0d2c62a28b - __libc_start_main
  24:     0x59e67bd9a0e5 - <unknown>
  25:                0x0 - <unknown>

Adam

Check the filerd service is running, run systemctl restart filerd on the web server. If it still doesn't work please send me a support ticket.

ecp access-token list is only intended to run on the control panel server, it's normal that it would error if you run it on another server. That command manages access tokens for the panel which are different to the ephemeral tokens used by the file manager service.