Nginx: Hangs for almost 25 minutes at deploying in npm

24 hours after I migrated to Electric Eel and did a fresh install of the nginx-proxy-manager, and there is an update to the nginx application to App Version: 2.12.1 / Version: 1.0.24 . However, it is hanging at deploying for almost 25 minutes at the npm level.

2024-11-01 04:38:47.997614+00:00 e[1;34m❯ e[1;36mConfiguring npm user ...e[0m
2024-11-01 04:38:49.726797+00:00 useradd warning: npm's uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2024-11-01 04:38:50.578503+00:00 e[1;34m❯ e[1;36mConfiguring npm group ...e[0m
2024-11-01 04:38:50.762413+00:00 e[1;34m❯ e[1;36mChecking paths ...e[0m
2024-11-01 04:38:50.951546+00:00 e[1;34m❯ e[1;36mSetting ownership ...e[0m
2024-11-01 05:03:20.445051+00:00 e[1;34m❯ e[1;36mDynamic resolvers ...e[0m
2024-11-01 05:03:20.470183+00:00 e[1;34m❯ e[1;36mIPv6 ...e[0m
2024-11-01 05:03:20.478323+00:00 Disabling IPV6 in hosts in: /etc/nginx/conf.d
2024-11-01 05:03:20.478399+00:00 - /etc/nginx/conf.d/default.conf
2024-11-01 05:03:20.507247+00:00 - /etc/nginx/conf.d/production.conf
2024-11-01 05:03:20.555523+00:00 - /etc/nginx/conf.d/include/log.conf
2024-11-01 05:03:20.571779+00:00 - /etc/nginx/conf.d/include/proxy.conf
2024-11-01 05:03:20.590328+00:00 - /etc/nginx/conf.d/include/force-ssl.conf
2024-11-01 05:03:20.638891+00:00 - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2024-11-01 05:03:20.655985+00:00 - /etc/nginx/conf.d/include/assets.conf
2024-11-01 05:03:20.668226+00:00 - /etc/nginx/conf.d/include/ip_ranges.conf
2024-11-01 05:03:20.670191+00:00 - /etc/nginx/conf.d/include/block-exploits.conf
2024-11-01 05:03:20.694240+00:00 - /etc/nginx/conf.d/include/ssl-ciphers.conf
2024-11-01 05:03:20.696512+00:00 - /etc/nginx/conf.d/include/resolvers.conf
2024-11-01 05:03:20.702897+00:00 Disabling IPV6 in hosts in: /data/nginx

Here is a screenshot of my configuration:

25 minutes is extremely unusual especially since all of my other apps start up a minute after deploying.

Hello,
add this line right below time zone in “Additional Environment Variables”

S6_STAGE2_HOOK=sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh

1 Like

image

2024-11-01 10:29:54.129017+00:00 e[1;34m❯ e[1;36mConfiguring npm user ...e[0m
2024-11-01 10:29:54.967626+00:00 useradd warning: npm's uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2024-11-01 10:29:55.863200+00:00 e[1;34m❯ e[1;36mConfiguring npm group ...e[0m
2024-11-01 10:29:56.046107+00:00 e[1;34m❯ e[1;36mChecking paths ...e[0m
2024-11-01 10:29:56.213585+00:00 e[1;34m❯ e[1;36mSetting ownership ...e[0m
2024-11-01 10:29:58.480053+00:00 e[1;34m❯ e[1;36mDynamic resolvers ...e[0m
2024-11-01 10:29:58.486379+00:00 e[1;34m❯ e[1;36mIPv6 ...e[0m
2024-11-01 10:29:58.492680+00:00 Disabling IPV6 in hosts in: /etc/nginx/conf.d
2024-11-01 10:29:58.492733+00:00 - /etc/nginx/conf.d/default.conf
2024-11-01 10:29:58.505680+00:00 - /etc/nginx/conf.d/production.conf

YAY! Deployment is now as expected. Thank you!

1 Like

Mine takes 1hr to complete the ‘setting ownership’ even after adding the environmental variable

Sounds like you guys are using Hard Drives and it’s slow to CHOWN the files

I change the userid and groupid to be within the 1000-60000 range, and the useradd error did not show up in the logs. But it still takes forever to deploy.

The problem seems to be related to user/group mapping between the host and the container. Is your suggestion a workaround that can cause problems down the road, or is it just skipping an unimportant step?

I changed the userid and groupid to 0 (root) and after it was deploying fast (i also applied the variable mentioned above which did not help).
Not sure if that is a good way to solve it though.

1 Like

I’ve having the same issue with the 25 minute delay. Has there been any new solutions to this problem outside of using the environment variable? Chat-gpt explained to me that this variable essentially truncates a file which makes it skip the check for this. This doesn’t seem so bad as no other containers would be accessing this dataset. Just wanted to check in before attempting this.

Started in seconds. App is on a SSD.