starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #436] NPM is down: "finish: applet not found" #366

New issue

Closed

opened 2026-02-26 06:32:33 +03:00 by kerem · 10 comments

kerem commented

2026-02-26 06:32:33 +03:00

Owner

Originally created by @SAOPP on GitHub (May 30, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/436

Hi!

Guys, after the latest docker container upgrade have an next issue:

Also, admin webface is not available. So, my npm is down, redeploy also is the same resault. What's happened who know?

Originally created by @SAOPP on GitHub (May 30, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/436 Hi! Guys, after the latest docker container upgrade have an next issue: ![image](https://user-images.githubusercontent.com/5647009/83321216-b2ddf800-a256-11ea-9b71-0522d344a978.png) Also, admin webface is not available. So, my npm is down, redeploy also is the same resault. What's happened who know?

kerem

2026-02-26 06:32:33 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@jc21 commented on GitHub (May 30, 2020):

I've encountered this problem just recently, with 2 different Centos 7 hosts running latest version of docker. This only seems to happen when building the container in CI on those hosts, but when running an image built with a different host, it works fine.

The error you're seeing suggests that the Nginx binary inside the container is not built for the architecture you're running it on, however I'm 100% sure it's a red herring and the problem is a result of something else.

Could you please check that the docker tag 2.2.4 works differently?

For reference, here's my docker version:

Client: Docker Engine - Community
 Version:           19.03.10
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        9424aeaee9
 Built:             Thu May 28 22:18:06 2020
 OS/Arch:           linux/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.10
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       9424aeaee9
  Built:            Thu May 28 22:16:43 2020
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

and kernel: 3.10.0-1127.8.2.el7.x86_64

@jc21 commented on GitHub (May 30, 2020): I've encountered this problem just recently, with 2 different Centos 7 hosts running latest version of docker. This only seems to happen when building the container in CI on those hosts, but when running an image built with a different host, it works fine. The error you're seeing suggests that the Nginx binary inside the container is not built for the architecture you're running it on, however I'm 100% sure it's a red herring and the problem is a result of something else. Could you please check that the docker tag `2.2.4` works differently? For reference, here's my docker version: ``` Client: Docker Engine - Community Version: 19.03.10 API version: 1.40 Go version: go1.13.10 Git commit: 9424aeaee9 Built: Thu May 28 22:18:06 2020 OS/Arch: linux/amd64 Experimental: true Server: Docker Engine - Community Engine: Version: 19.03.10 API version: 1.40 (minimum version 1.12) Go version: go1.13.10 Git commit: 9424aeaee9 Built: Thu May 28 22:16:43 2020 OS/Arch: linux/amd64 Experimental: true containerd: Version: 1.2.13 GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429 runc: Version: 1.0.0-rc10 GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd docker-init: Version: 0.18.0 GitCommit: fec3683 ``` and kernel: `3.10.0-1127.8.2.el7.x86_64`

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@SAOPP commented on GitHub (May 30, 2020):

Hi. one second I will check... before I'm had trying to use tag 2 and 3... instead latest, but faced with the same issue.

@SAOPP commented on GitHub (May 30, 2020): Hi. one second I will check... before I'm had trying to use tag 2 and 3... instead latest, but faced with the same issue.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@SAOPP commented on GitHub (May 30, 2020):

Yes this build is working thanks.

@SAOPP commented on GitHub (May 30, 2020): Yes this build is working thanks.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@SAOPP commented on GitHub (May 30, 2020):

Solution: https://github.com/jc21/nginx-proxy-manager/issues/436#issuecomment-636289064

@SAOPP commented on GitHub (May 30, 2020): Solution: https://github.com/jc21/nginx-proxy-manager/issues/436#issuecomment-636289064

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@jc21 commented on GitHub (May 31, 2020):

My comment was not a solution, it was a downgrade for those with this current problem.

@jc21 commented on GitHub (May 31, 2020): My comment was not a solution, it was a downgrade for those with this current problem.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@jc21 commented on GitHub (May 31, 2020):

Right so I think I've got to the bottom of it. 2.3.0 uses OpenResty now instead of Nginx vanilla.

OpenResty by default only supports cpu's with SSE 4.2+ by default. Looking in to a fix.

@jc21 commented on GitHub (May 31, 2020): Right so I think I've got to the bottom of it. 2.3.0 uses OpenResty now instead of Nginx vanilla. OpenResty by default only supports cpu's with SSE 4.2+ by default. Looking in to a fix.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@jc21 commented on GitHub (May 31, 2020):

The latest, 2 and 2.3.0 tags have been rebuilt to support those older CPUs. Please try again and reopen if you have more troubles.

@jc21 commented on GitHub (May 31, 2020): The `latest`, `2` and `2.3.0` tags have been rebuilt to support those older CPUs. Please try again and reopen if you have more troubles.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@SAOPP commented on GitHub (Jun 2, 2020):

Pulled now latest image and redeploy it, all seems fine now. Thanks. And actually yes, my copy running at very old small pc, I'm using it for some small docker server, and on board something like pentium d500 like that.

@SAOPP commented on GitHub (Jun 2, 2020): Pulled now latest image and redeploy it, all seems fine now. Thanks. And actually yes, my copy running at very old small pc, I'm using it for some small docker server, and on board something like pentium d500 like that.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@jc21 commented on GitHub (Jun 3, 2020):

Awesome. I'm likely to drop support for those older CPU's in version 3 but that's a while off.

@jc21 commented on GitHub (Jun 3, 2020): Awesome. I'm likely to drop support for those older CPU's in version 3 but that's a while off.

kerem commented

2026-02-26 06:32:34 +03:00

Author

Owner

@SAOPP commented on GitHub (Jun 3, 2020):

Essentially, if, then this is the right decision, since the problems of old processors are not rational in a brand new software.

@SAOPP commented on GitHub (Jun 3, 2020): Essentially, if, then this is the right decision, since the problems of old processors are not rational in a brand new software.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#366

No description provided.

Rows
Columns