Critical bug: deleting a user crashes Hiddify Manager and makes the server unresponsive #5578
Description
Activity
Hello
I have exactly the same problem. In my case, restarting services shows:Hiddify: Command restart ========================================== ---------------------------------------------------------------- Name Old Status New Status Error: Key not found: warp_mode hiddify-core active ---> active hiddify-mysql active ---> active hiddify-rpxy-l4 active ---> activeSome main service has wierd errors logs like:
journalctl -e -u hiddify-panel-background-tasks.service Sep 29 11:32:27 xxx systemd[1]: hiddify-panel-background-tasks.service: Failed to op> Sep 29 11:32:27 xxx systemd[1]: hiddify-panel-background-tasks.service: Failed to op>journalctl -e -u hiddify-dnstm-router.service Sep 29 11:32:27 eu-server systemd[1]: hiddify-dnstm-router.service: Failed to open /etc/sy> Sep 29 11:32:27 eu-server systemd[1]: hiddify-dnstm-router.service: Failed to open /etc/sy>Any solution?
Reacted by Hesam Rad and Fatmann666Same issue here. Whenever I update a user everything crashes and I see
Error: Key not found: warp_modeerror.I have to update the entire server using cli to fix the issue.
Reacted by Fatmann666 and Anton SmirnovHaving the same issue, any solution?
I tracked this down on a v13.0.3 server. It's caused by
scripts/migrate_layout.sh, and it's already fixed ondev(7ce3eab) but not yet inmain/beta.Cause
scripts/install.shrunsmigrate_layout.shon every call, including "Apply configs" andinstall.sh apply_users(what the panel runs when you change a user). Itsdisable_all_servicessearches/opt/hiddify-manager/for*.servicefiles. It skipsservices/but notold/, where the upgrade moved the previous layout. The files inold/have the same names as the current units (hiddify-haproxy,hiddify-nginx,hiddify-panel,hiddify-redis,hiddify-xray,mtproxy, ...). So it runssystemctl disable --nowon the live services. That stops them and removes their symlinks from/etc/systemd/system.- A full install (CLI update, or the
@rebootreinstall) recreates the units in each service'sinstall.sh, so everything comes back. That's why updating from the CLI "fixes" it. - Apply configs / apply users run with
DO_NOT_INSTALL=true, so nothing recreates haproxy, nginx, panel and redis. They stay gone, andhiddify restartonly lists core/mysql/rpxy-l4. TheFailed to open /etc/systemd/system/...messages in the journal are the deleted symlinks.
To check whether you're affected:
find /opt/hiddify-manager/ -type d -name services -prune -o -type f -name '*.service' -printIf this prints anything under
old/, you're hit by this.Fix
Make the same change as
devin/opt/hiddify-manager/scripts/migrate_layout.sh(also skipold/):sudo sed -i 's#-type d -name "services" -prune -o -type f#-type d -name "services" -prune -o -type d -name "old" -prune -o -type f#' /opt/hiddify-manager/scripts/migrate_layout.shThen run a full install once to restore the deleted units:
sudo bash /opt/hiddify-manager/scripts/install.sh --no-gui
After the change, I ran
apply_configs.shandinstall.sh apply_users, and all units (haproxy, nginx, panel, redis, xray, core, mysql, rpxy-l4, mtproxy) stayed loaded and running. Before the change,apply_configs.shremoved haproxy, nginx, panel and redis every time.Note: the next update unpacks a new release over the patched file and will overwrite it until the fix is in a stable release. If you don't need anything in
/opt/hiddify-manager/old/, deleting it also prevents the problem.Error: Key not found: warp_modeis unrelated and harmless. It's just a missing config key thatrestart.shreads.- A full install (CLI update, or the
Hello Hiddify development team,
I have found a critical issue in the latest Hiddify Manager update.
When I delete a user from the Hiddify Manager web panel, the system becomes completely unresponsive.
After clicking Delete user:
This happens specifically when deleting a user through the Hiddify Manager panel.
Environment
The problem appeared after updating Hiddify Manager.
Impact
This is a critical issue because deleting a single user can effectively take down the entire VPS. A complete server reboot is required to recover.
Could you please investigate this issue?
In particular, it would be useful to check whether the user deletion process can cause:
I can provide logs, configuration information, or reproduction steps if needed.
Please let me know which logs you would like me to collect immediately after reproducing the problem.
Thank you.
Best regards,
Hiddify user