starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #581] Getting Error when Arm64/Odroid C4 - OMV5 - Debian Stretch 64 #488

New issue

Closed

opened 2026-02-26 06:33:04 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @ghost on GitHub (Aug 26, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/581

OMV5 Debian Stretch64 for arm64 Odroid C4 board

Creating config.json and docker-compose.yaml per installation instructions. When docker-compose up -d is run I get the following error:

ERROR: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-bd9843adfdb5 -j DOCKER: iptables v1.8.2 (nf_tables):  RULE_INSERT failed (Invalid argument): rule in chain FORWARD
 (exit status 4)

Config:

{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "DBNAME",
    "user": "DBUSERNAME",
    "password": "DBPASSWORD",
    "port": 3306
  }

docker-compose:

version: '2'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      - '80:80'
      - '443:443'
      - '81:81'
    volumes:
      - './config.json:/app/config/production.json'
      - './data:/data'
      - './letsencrypt:/etc/letsencrypt'
    depends_on:
      - db
  db:
    image: 'yobasystems/alpine-mariadb:latest'
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: npman
      MYSQL_DATABASE: npman
      MYSQL_USER: npman
      MYSQL_PASSWORD: pasmuqks
    volumes:
      - './data/mysql:/var/lib/mysql'

Originally created by @ghost on GitHub (Aug 26, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/581 OMV5 Debian Stretch64 for arm64 Odroid C4 board Creating config.json and docker-compose.yaml per installation instructions. When docker-compose up -d is run I get the following error: ``` ERROR: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-bd9843adfdb5 -j DOCKER: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain FORWARD (exit status 4) ``` Config: ``` { "database": { "engine": "mysql", "host": "db", "name": "DBNAME", "user": "DBUSERNAME", "password": "DBPASSWORD", "port": 3306 } ``` docker-compose: ``` version: '2' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: always ports: - '80:80' - '443:443' - '81:81' volumes: - './config.json:/app/config/production.json' - './data:/data' - './letsencrypt:/etc/letsencrypt' depends_on: - db db: image: 'yobasystems/alpine-mariadb:latest' restart: always environment: MYSQL_ROOT_PASSWORD: npman MYSQL_DATABASE: npman MYSQL_USER: npman MYSQL_PASSWORD: pasmuqks volumes: - './data/mysql:/var/lib/mysql' ```

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@ghost commented on GitHub (Aug 29, 2020):

Tried an update to the system and rebooted docker - problem still exists

@ghost commented on GitHub (Aug 29, 2020): Tried an update to the system and rebooted docker - problem still exists

kerem commented

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

Author

Owner

@ghost commented on GitHub (Sep 2, 2020):

This may have to do with iptables-legacy on debian buster. Not sure how to proceed.

@ghost commented on GitHub (Sep 2, 2020): This may have to do with iptables-legacy on debian buster. Not sure how to proceed.

kerem commented

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

Author

Owner

@ghost commented on GitHub (Sep 2, 2020):

OK if anyone has this error is it because debian is now using nftables rather than iptables. Here is how if fixed it:

# sudo apt-get install -y iptables arptables ebtables

Then

# update-alternatives --set iptables /usr/sbin/iptables-legacy
# update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
# update-alternatives --set arptables /usr/sbin/arptables-legacy
# update-alternatives --set ebtables /usr/sbin/ebtables-legacy

Then restart docker. Should be good.

@ghost commented on GitHub (Sep 2, 2020): OK if anyone has this error is it because debian is now using nftables rather than iptables. Here is how if fixed it: `# sudo apt-get install -y iptables arptables ebtables` Then ``` # update-alternatives --set iptables /usr/sbin/iptables-legacy # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy # update-alternatives --set arptables /usr/sbin/arptables-legacy # update-alternatives --set ebtables /usr/sbin/ebtables-legacy ``` Then restart docker. Should be good.

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#488

No description provided.

Rows
Columns