Installation stop at the 2%

[emilycodestar]

Hiddify Manager Installer
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐▒▒▒│ See "systemctl status hiddify-nginx.service" and "journalctl -xeu hiddify-nginx.service" for details. │ ▒▒│ }========================nginx=================================== │ ▒▒│ ---------------------Finished!------------------------ │ ▒▒│ ======================other/redis====================================={ │ ▒▒│ ===install.sh common │ ▒▒│ ===install.sh other/redis │ ▒▒│ ======================other/mysql====================================={ │ ▒▒│ ===install.sh other/mysql │ ▒▒│ ===run.sh other/redis │ ▒▒│ }========================other/mysql=================================== │ ▒▒│ }========================other/redis=================================== │ ▒▒│ Using Python 3.13.7 environment at: /opt/hiddify-manager/.venv313 │ ▒▒│ net.ipv6.conf.all.disable_ipv6 = 0 │ ▒▒│ net.ipv6.conf.default.disable_ipv6 = 0 │ ▒▒│ net.ipv6.conf.lo.disable_ipv6 = 0 │ ▒▒│ IPv6 Enabled for eth0 │ ▒▒│ * Reloading configuration files for periodic command scheduler cron │ ▒▒│ ...done. │ ▒▒│ ======================hiddify-panel====================================={ │ ▒▒│ ===install.sh hiddify-panel │ ▒▒│ ===run.sh hiddify-panel │ ▒▒└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒Installing... Common Tools and Requirements
2 %

[emilycodestar]

At the full clear system ubuntu 24 on the US server

[emilycodestar]

And also docker installation ain't working at all, it's creating directory with 2 docker files and then failing with error which mean that script can't find this directory with 2 docker files, idk

[emilycodestar]

[emilycodestar]

[ecteli]

I am experiencing the exact same issue on a fresh Ubuntu 22.04 64-bit VPS (location: US, New York).

During installation, the process stops at around 2% with the following error:

Job for hiddify-nginx.service failed because the control process exited with error code.
See "systemctl status hiddify-nginx.service" and "journalctl -xeu hiddify-nginx.service" for details.

From the logs:

nginx: [emerg] open() "/opt/hiddify-manager/nginx/nginx.conf" failed (2: No such file or directory)
systemd: hiddify-nginx.service: Failed with result 'exit-code'.

So the installation script expects `/opt/hiddify-manager/nginx/nginx.conf`, but this file and directory are never created. Because of that, the service cannot start and the installer hangs at 2%.

**Additional details:**
- OS: Ubuntu 22.04 LTS x86_64, clean installation
- VPS provider: RackNerd (US, NY)
- No other nginx/Apache installed
- Sometimes `unattended-upgrades` holds the dpkg lock (`/var/lib/dpkg/lock-frontend`) during installation, which may interrupt package configuration.

It looks like a general installer bug (not machine-specific), since the expected nginx config is missing.

Can you please confirm if this is a known bug and if there is a workaround (like correct symlink or adjusted unit file path)?

[emilycodestar]

So basic on your comment it's probably known bug, but i don't know any way to fix it.

[emilycodestar]

So, basic on documentation:

This code is only applicable on Ubuntu and has been tested only on version 22.04.

Issue is closed. I will attempt to install on Ubuntu 22.04, if it fails, unfortunately, i am gonna lookup for other solutions

[emilycodestar]

▒┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐▒▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒│ Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7114 (unattended-up>│ ▒▒└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒Installing... Almost Finished 98 %

Well.. now it's stuck here. For fuck sake...

[SARNPKIR]

same here i think its because of slip io temp domain down which is required to proceed installation i tried on Ubuntu 22.04, and Ubuntu 24.04, both stuck and failed at 2 percent

[vizvamitra]

Hi there. Just got into same problems, turned out the issue was with a lack of memory. I was running the script on a t3.nano aws instance which only has 512Mb of ram. Configuring a swapfile solved all the issues and allowed setup to finish.

For those who do not know how to set it up, here's a good guide: https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-20-04

A note for maintainers: Maybe it's worth mentioning memory requirements in the guide. And, btw, thanks for a great project!

[emilycodestar]

Hi there. Just got into same problems, turned out the issue was with a lack of memory. I was running the script on a t3.nano aws instance which only has 512Mb of ram. Configuring a swapfile solved all the issues and allowed setup to finish.

For those who do not know how to set it up, here's a good guide: https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-20-04

A note for maintainers: Maybe it's worth mentioning memory requirements in the guide. And, btw, thanks for a great project!

i have 2 gb of ram. should be enough... if not, it's actually quite expensive

[SARNPKIR]

Hi there. Just got into same problems, turned out the issue was with a lack of memory. I was running the script on a t3.nano aws instance which only has 512Mb of ram. Configuring a swapfile solved all the issues and allowed setup to finish.
For those who do not know how to set it up, here's a good guide: https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-20-04
A note for maintainers: Maybe it's worth mentioning memory requirements in the guide. And, btw, thanks for a great project!

i have 2 gb of ram. should be enough... if not, it's actually quite expensive

thanks it solved the issue of Installation stop at the 2% respect bro

[Creogenesis]

The version of Hiddify Manager after release 11.0.12 turned out to be very unstable. It’s hard to understand how this build made it past beta testing — it feels like proper QA might have been skipped.

After many installation attempts, the setup rarely finishes successfully. Services fail to start, reinstallation does not help, and initial configurations for haproxy, singbox, xray, etc. are not generated. At the end of the installation, no link is provided for the first login to the panel.

The logs are filled with errors (no need to list them here — you can easily reproduce and see for yourself).

Tested on Ubuntu 24.04 LTS (fresh and updated, using official fast repositories). VPS location: Finland. Also tested on Akamai Linode in Sweden with different providers and regions.

It’s not a resource issue either: instances with 2xCPU, 4GB RAM, NVMe 50GB were used across multiple VPS providers.

Please fix this — there’s still a lot of work ahead 😉 Maybe a few more beta versions wouldn’t hurt!