starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1128] Segmentation fault on ARM64 #927

New issue
Closed
opened 2026-02-26 06:34:59 +03:00 by kerem · 12 comments
kerem commented 2026-02-26 06:34:59 +03:00
Owner
Copy link

Originally created by @tribal2 on GitHub (May 26, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1128

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? Yes
  • Are you sure you're not using someone else's docker image? Yes
  • Have you searched for similar issues (both open and closed)? Yes

Describe the bug
I got a segmentation fault when I try to run the container using the docker-compose.yml from here: https://nginxproxymanager.com/setup/#running-on-raspberry-pi-arm-devices .

Same error with NPM tags 2.9.3, 2.8.0, github-develop

Here is the log:

app_1  | [5/26/2021] [6:06:36 PM] [Global   ] › ℹ  info      Generating MySQL db configuration from environment variables
app_1  | [5/26/2021] [6:06:36 PM] [Global   ] › ℹ  info      Wrote db configuration to config file: ./config/production.json
app_1  | [5/26/2021] [6:06:38 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   229 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:40 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   271 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:41 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   294 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:43 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   307 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:45 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   320 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

Operating System

  • Oracle Linux 8: Image: Oracle-Linux-Cloud-Developer-8.3-aarch64-2021.05.12-1
  • Podman / Docker -> same error

$ lscpu

Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):           1
NUMA node(s):        1
Vendor ID:           ARM
Model:               1
Stepping:            r3p1
BogoMIPS:            50.00
NUMA node0 CPU(s):   0,1
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
Originally created by @tribal2 on GitHub (May 26, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1128 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? **Yes** - Are you sure you're not using someone else's docker image? **Yes** - Have you searched for similar issues (both open and closed)? **Yes** **Describe the bug** I got a segmentation fault when I try to run the container using the docker-compose.yml from here: https://nginxproxymanager.com/setup/#running-on-raspberry-pi-arm-devices . Same error with NPM tags 2.9.3, 2.8.0, github-develop Here is the log: ``` app_1 | [5/26/2021] [6:06:36 PM] [Global ] › ℹ info Generating MySQL db configuration from environment variables app_1 | [5/26/2021] [6:06:36 PM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json app_1 | [5/26/2021] [6:06:38 PM] [Migrate ] › ℹ info Current database version: none app_1 | ./run: line 18: 229 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js app_1 | [5/26/2021] [6:06:40 PM] [Migrate ] › ℹ info Current database version: none app_1 | ./run: line 18: 271 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js app_1 | [5/26/2021] [6:06:41 PM] [Migrate ] › ℹ info Current database version: none app_1 | ./run: line 18: 294 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js app_1 | [5/26/2021] [6:06:43 PM] [Migrate ] › ℹ info Current database version: none app_1 | ./run: line 18: 307 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js app_1 | [5/26/2021] [6:06:45 PM] [Migrate ] › ℹ info Current database version: none app_1 | ./run: line 18: 320 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ``` **Operating System** - Oracle Linux 8: Image: Oracle-Linux-Cloud-Developer-8.3-aarch64-2021.05.12-1 - Podman / Docker -> same error `$ lscpu` ``` Architecture: aarch64 Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: ARM Model: 1 Stepping: r3p1 BogoMIPS: 50.00 NUMA node0 CPU(s): 0,1 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs ```
kerem 2026-02-26 06:34:59 +03:00
  • closed this issue
  • added the
    stale
    bug
         labels
kerem commented 2026-02-26 06:34:59 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (May 26, 2021):

Sounds like this docker-node issue, could you check whether the code in that issue also results in a segmentation fault?

<!-- gh-comment-id:849078279 --> @chaptergy commented on GitHub (May 26, 2021): Sounds like [this docker-node issue](https://github.com/nodejs/docker-node/issues/588), could you check whether the code in that issue also results in a segmentation fault?
kerem commented 2026-02-26 06:34:59 +03:00
Author
Owner
Copy link

@tribal2 commented on GitHub (May 26, 2021):

@chaptergy no... it's running ok:

$ docker run --rm --entrypoint sh -it node:alpine
/ # node
Welcome to Node.js v16.1.0.
Type ".help" for more information.
>
<!-- gh-comment-id:849086005 --> @tribal2 commented on GitHub (May 26, 2021): @chaptergy no... it's running ok: ``` $ docker run --rm --entrypoint sh -it node:alpine / # node Welcome to Node.js v16.1.0. Type ".help" for more information. > ```
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (May 26, 2021):

Hm, then I'm not sure I can help with that, sorry. Maybe someone from the community has an idea what could cause this. It would also be useful to know if this happens on any ARM64 machine, but if I remember correctly, there were people which were able to set it up on a Rasperry Pi with 64 bit.

<!-- gh-comment-id:849118798 --> @chaptergy commented on GitHub (May 26, 2021): Hm, then I'm not sure I can help with that, sorry. Maybe someone from the community has an idea what could cause this. It would also be useful to know if this happens on any ARM64 machine, but if I remember correctly, there were people which were able to set it up on a Rasperry Pi with 64 bit.
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@GrimIcarus commented on GitHub (Aug 1, 2021):

I've run this on a VPS's VM using both mariadb and sqlite, the CPU is an ampere altra which is a server grade ARM processor and i have the same issue
./run: line 18: 1750 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js, the VM has 4 cores, 16GB of ram

<!-- gh-comment-id:890581270 --> @GrimIcarus commented on GitHub (Aug 1, 2021): I've run this on a VPS's VM using both mariadb and sqlite, the CPU is an ampere altra which is a server grade ARM processor and i have the same issue ` ./run: line 18: 1750 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js `, the VM has 4 cores, 16GB of ram
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Aug 11, 2021):

Maybe someone could install the segfault-handler on their instance and register it in /app/index.js? Maybe that could provide some information of what causes this.

<!-- gh-comment-id:896742211 --> @chaptergy commented on GitHub (Aug 11, 2021): Maybe someone could install the [segfault-handler](https://www.npmjs.com/package/segfault-handler) on their instance and register it in `/app/index.js`? Maybe that could provide some information of what causes this.
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Aug 11, 2021):

I would have to assume this is one of 2 reasons:

  • node installed on there is faulty or
  • a compiled node_module is faulty
<!-- gh-comment-id:897191353 --> @jc21 commented on GitHub (Aug 11, 2021): I would have to assume this is one of 2 reasons: - node installed on there is faulty or - a compiled node_module is faulty
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@jquinn96 commented on GitHub (Aug 13, 2021):

Hi, I have a stack trace from a segfault

Environment is ARM Ampere (Oracle Cloud)

PID 17999 received SIGSEGV for address: 0x28
/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x2dd0)[0xfffe34202dd0]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xfffe367005c8]
node(_ZN2v88internal18CodeObjectRegistry32RegisterNewlyAllocatedCodeObjectEm+0x20)[0xdc89c8]
node(_ZN2v88internal4Heap11AllocateRawEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x26c)[0xe0d044]
node(_ZN2v88internal4Heap34AllocateRawWithRetryOrFailSlowPathEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x30)[0xe14158]
node(_ZN2v88internal7Factory11CodeBuilder13BuildInternalEb+0x104)[0xde9204]
node(_ZN2v88internal7Factory11CodeBuilder5BuildEv+0x10)[0xde9a10]
node(_ZN2v88internal25RegExpMacroAssemblerARM647GetCodeENS0_6HandleINS0_6StringEEE+0xd00)[0x13897c8]
node(_ZN2v88internal14RegExpCompiler8AssembleEPNS0_7IsolateEPNS0_20RegExpMacroAssemblerEPNS0_10RegExpNodeEiNS0_6HandleINS0_6StringEEE+0x154)[0x10bdd3c]
node(_ZN2v88internal10RegExpImpl7CompileEPNS0_7IsolateEPNS0_4ZoneEPNS0_17RegExpCompileDataENS_4base5FlagsINS0_8JSRegExp4FlagEiEENS0_6HandleINS0_6StringEEESF_bj+0x3c8)[0x10d96b0]
node(_ZN2v88internal10RegExpImpl15CompileIrregexpEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEb+0x164)[0x10d9c1c]
node(_ZN2v88internal6RegExp15IrregexpPrepareEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEE+0x158)[0x10da728]
node(_ZN2v88internal10RegExpImpl12IrregexpExecEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEiNS4_INS0_15RegExpMatchInfoEEE+0x84)[0x10da7fc]
node(_ZN2v88internal18Runtime_RegExpExecEiPmPNS0_7IsolateE+0x1a4)[0x112c964]
node[0x14638cc]
Segmentation fault (core dumped)

<!-- gh-comment-id:898182945 --> @jquinn96 commented on GitHub (Aug 13, 2021): Hi, I have a stack trace from a segfault Environment is ARM Ampere (Oracle Cloud) PID 17999 received SIGSEGV for address: 0x28 /app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x2dd0)[0xfffe34202dd0] linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xfffe367005c8] node(_ZN2v88internal18CodeObjectRegistry32RegisterNewlyAllocatedCodeObjectEm+0x20)[0xdc89c8] node(_ZN2v88internal4Heap11AllocateRawEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x26c)[0xe0d044] node(_ZN2v88internal4Heap34AllocateRawWithRetryOrFailSlowPathEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x30)[0xe14158] node(_ZN2v88internal7Factory11CodeBuilder13BuildInternalEb+0x104)[0xde9204] node(_ZN2v88internal7Factory11CodeBuilder5BuildEv+0x10)[0xde9a10] node(_ZN2v88internal25RegExpMacroAssemblerARM647GetCodeENS0_6HandleINS0_6StringEEE+0xd00)[0x13897c8] node(_ZN2v88internal14RegExpCompiler8AssembleEPNS0_7IsolateEPNS0_20RegExpMacroAssemblerEPNS0_10RegExpNodeEiNS0_6HandleINS0_6StringEEE+0x154)[0x10bdd3c] node(_ZN2v88internal10RegExpImpl7CompileEPNS0_7IsolateEPNS0_4ZoneEPNS0_17RegExpCompileDataENS_4base5FlagsINS0_8JSRegExp4FlagEiEENS0_6HandleINS0_6StringEEESF_bj+0x3c8)[0x10d96b0] node(_ZN2v88internal10RegExpImpl15CompileIrregexpEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEb+0x164)[0x10d9c1c] node(_ZN2v88internal6RegExp15IrregexpPrepareEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEE+0x158)[0x10da728] node(_ZN2v88internal10RegExpImpl12IrregexpExecEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEiNS4_INS0_15RegExpMatchInfoEEE+0x84)[0x10da7fc] node(_ZN2v88internal18Runtime_RegExpExecEiPmPNS0_7IsolateE+0x1a4)[0x112c964] node[0x14638cc] Segmentation fault (core dumped)
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@jquinn96 commented on GitHub (Aug 13, 2021):

Update on this, appears to be a bug on nodes end that they've resolved in node 16+. I did an update to node 16.6.2 and it resolved the segfault.

<!-- gh-comment-id:898195469 --> @jquinn96 commented on GitHub (Aug 13, 2021): Update on this, appears to be a bug on nodes end that they've resolved in node 16+. I did an update to node 16.6.2 and it resolved the segfault.
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Aug 13, 2021):

Alrighty, I'll update the base node version to 16 and see what breaks

<!-- gh-comment-id:898206206 --> @jc21 commented on GitHub (Aug 13, 2021): Alrighty, I'll update the base node version to 16 and see what breaks
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Aug 17, 2021):

There was a bit of a delay, upstream docker image changes caused builds to fail for a while.

You can now verify this is fixed with this image:

jc21/nginx-proxy-manager:github-develop

it's using node v16.6.2 currently.

If it's all working please close this issue :)

<!-- gh-comment-id:899954890 --> @jc21 commented on GitHub (Aug 17, 2021): There was a bit of a delay, upstream docker image changes caused builds to fail for a while. You can now verify this is fixed with this image: ``` jc21/nginx-proxy-manager:github-develop ``` it's using node v16.6.2 currently. If it's all working please close this issue :)
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 11, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1987487821 --> @github-actions[bot] commented on GitHub (Mar 11, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 06:35:00 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 23, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2822884892 --> @github-actions[bot] commented on GitHub (Apr 23, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#927
No description provided.