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 #1134] Unable to run on aarch64 #933

New issue
Closed
opened 2026-02-26 06:35:02 +03:00 by kerem · 1 comment
kerem commented 2026-02-26 06:35:02 +03:00
Owner
Copy link

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

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

"Bad Gateway" - on attempt to login.

Nginx Proxy Manager Version:

  • v2.9.3

To Reproduce
Steps to reproduce the behavior:

  1. created a docker-compose.yml with following content from quick setup guide:
version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "npm"
      DB_MYSQL_NAME: "npm"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - ./data/mysql:/var/lib/mysql
  1. docker-compose up ( I'm using linuxserver/docker-compose )

Operating System:

  • Oracle Linux Server release 7.9

Platform:

  • Oracle Cloud

CPU Info:

[opc@instance-20210529-1419 nginx-proxy-manager]$ sudo lscpu
Architecture:          aarch64
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Model:                 1
BogoMIPS:              50.00
NUMA node0 CPU(s):     0-3
Flags:                 fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

Logs on DB container:

[i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
[i] mysqld not found, creating....
[i] MySQL directory already present, skipping creation
2021-05-29  9:51:05 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
2021-05-29  9:51:05 0 [Note] Plugin 'InnoDB' is disabled.
2021-05-29  9:51:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-05-29  9:51:05 0 [Note] Server socket created on IP: '::'.
2021-05-29  9:51:05 0 [Warning] 'user' entry '@fb5deba43988' ignored in --skip-name-resolve mode.
2021-05-29  9:51:05 0 [Warning] 'proxies_priv' entry '@% root@fb5deba43988' ignored in --skip-name-resolve mode.
2021-05-29  9:51:05 0 [Note] Reading of all Master_info entries succeeded
2021-05-29  9:51:05 0 [Note] Added new Master_info '' to hash table
2021-05-29  9:51:05 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.4.15-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server
2021-05-29  9:51:09 3 [Warning] Aborted connection 3 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:12 4 [Warning] Aborted connection 4 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:15 5 [Warning] Aborted connection 5 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:18 6 [Warning] Aborted connection 6 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:21 7 [Warning] Aborted connection 7 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:24 8 [Warning] Aborted connection 8 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:30 9 [Warning] Aborted connection 9 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:33 10 [Warning] Aborted connection 10 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:36 11 [Warning] Aborted connection 11 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)
2021-05-29  9:51:39 12 [Warning] Aborted connection 12 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets)

Logs on App container:

[5/29/2021] [9:51:06 AM] [Global   ] › ℹ  info      Generating MySQL db configuration from environment variables
[5/29/2021] [9:51:06 AM] [Global   ] › ℹ  info      Wrote db configuration to config file: ./config/production.json
./run: line 18:   223 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   272 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   295 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
[5/29/2021] [9:51:16 AM] [Migrate  ] › ℹ  info      Current database version: none
./run: line 18:   317 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   330 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   352 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
[5/29/2021] [9:51:26 AM] [Migrate  ] › ℹ  info      Current database version: none
./run: line 18:   365 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   387 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   409 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
./run: line 18:   422 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
[5/29/2021] [9:51:40 AM] [Migrate  ] › ℹ  info      Current database version: none
./run: line 18:   445 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
[5/29/2021] [9:51:43 AM] [Migrate  ] › ℹ  info      Current database version: none
./run: line 18:   458 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

While in the logs it says: "Wrote db configuration to config file: ./config/production.json", I don't see a ./config directory being created.

Originally created by @rahulmkhj on GitHub (May 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1134 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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** <!-- A clear and concise description of what the bug is. --> "Bad Gateway" - on attempt to login. **Nginx Proxy Manager Version:** <!-- What version of Nginx Proxy Manager is reported on the login page? --> - v2.9.3 **To Reproduce** Steps to reproduce the behavior: 1. created a docker-compose.yml with following content from [quick setup guide](https://nginxproxymanager.com/guide/#quick-setup): ```yaml version: '3' services: app: image: 'jc21/nginx-proxy-manager:latest' ports: - '80:80' - '81:81' - '443:443' environment: DB_MYSQL_HOST: "db" DB_MYSQL_PORT: 3306 DB_MYSQL_USER: "npm" DB_MYSQL_PASSWORD: "npm" DB_MYSQL_NAME: "npm" volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt db: image: 'jc21/mariadb-aria:latest' environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes: - ./data/mysql:/var/lib/mysql ``` 2. docker-compose up ( I'm using [linuxserver/docker-compose](https://hub.docker.com/r/linuxserver/docker-compose) ) **Operating System:** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> - Oracle Linux Server release 7.9 **Platform:** - Oracle Cloud **CPU Info:** ``` [opc@instance-20210529-1419 nginx-proxy-manager]$ sudo lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Model: 1 BogoMIPS: 50.00 NUMA node0 CPU(s): 0-3 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs ``` Logs on DB container: ``` [i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh [i] mysqld not found, creating.... [i] MySQL directory already present, skipping creation 2021-05-29 9:51:05 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ... 2021-05-29 9:51:05 0 [Note] Plugin 'InnoDB' is disabled. 2021-05-29 9:51:05 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-05-29 9:51:05 0 [Note] Server socket created on IP: '::'. 2021-05-29 9:51:05 0 [Warning] 'user' entry '@fb5deba43988' ignored in --skip-name-resolve mode. 2021-05-29 9:51:05 0 [Warning] 'proxies_priv' entry '@% root@fb5deba43988' ignored in --skip-name-resolve mode. 2021-05-29 9:51:05 0 [Note] Reading of all Master_info entries succeeded 2021-05-29 9:51:05 0 [Note] Added new Master_info '' to hash table 2021-05-29 9:51:05 0 [Note] /usr/bin/mysqld: ready for connections. Version: '10.4.15-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server 2021-05-29 9:51:09 3 [Warning] Aborted connection 3 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:12 4 [Warning] Aborted connection 4 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:15 5 [Warning] Aborted connection 5 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:18 6 [Warning] Aborted connection 6 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:21 7 [Warning] Aborted connection 7 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:24 8 [Warning] Aborted connection 8 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:30 9 [Warning] Aborted connection 9 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:33 10 [Warning] Aborted connection 10 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:36 11 [Warning] Aborted connection 11 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) 2021-05-29 9:51:39 12 [Warning] Aborted connection 12 to db: 'npm' user: 'npm' host: '172.20.0.3' (Got an error reading communication packets) ``` Logs on App container: ``` [5/29/2021] [9:51:06 AM] [Global ] › ℹ info Generating MySQL db configuration from environment variables [5/29/2021] [9:51:06 AM] [Global ] › ℹ info Wrote db configuration to config file: ./config/production.json ./run: line 18: 223 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 272 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 295 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js [5/29/2021] [9:51:16 AM] [Migrate ] › ℹ info Current database version: none ./run: line 18: 317 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 330 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 352 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js [5/29/2021] [9:51:26 AM] [Migrate ] › ℹ info Current database version: none ./run: line 18: 365 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 387 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 409 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ./run: line 18: 422 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js [5/29/2021] [9:51:40 AM] [Migrate ] › ℹ info Current database version: none ./run: line 18: 445 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js [5/29/2021] [9:51:43 AM] [Migrate ] › ℹ info Current database version: none ./run: line 18: 458 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ``` **While in the logs it says: "Wrote db configuration to config file: ./config/production.json", I don't see a ./config directory being created.**
kerem 2026-02-26 06:35:02 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 06:35:03 +03:00
Author
Owner
Copy link

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

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/1128, please contribute any additional findings you have over there

<!-- gh-comment-id:850866151 --> @chaptergy commented on GitHub (May 29, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/1128, please contribute any additional findings you have over there
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#933
No description provided.