starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 18:05:54 +03:00

[GH-ISSUE #2778] Is it possible to change the nginx port if running macvlan? #1911

New issue

Closed

opened 2026-02-26 07:33:12 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:33:12 +03:00

Owner

Originally created by @cwesterfield on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2778

I'm running my instance on my lan and somehow I have it running on 4443. I'd like to change that to 443 so I can try using NPM on my LAN. Is this possible?

  nginx-proxy-manager:
    image: jlesage/nginx-proxy-manager:latest
    container_name: nginx-proxy-manager
    networks:
      LAN:
        ipv4_address: 10.0.1.201
    volumes:
      - /srv/NGINX-PROXY:/config
      - /srv/NGINX-PROXY/data/log:/data/log
    restart: unless-stopped

bash-5.1# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:25000           0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.11:38307        0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:4443            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:8181            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      -
tcp        0      0 :::25000                :::*                    LISTEN      -
tcp        0      0 :::3000                 :::*                    LISTEN      -
tcp        0      0 :::4443                 :::*                    LISTEN      -
tcp        0      0 :::8181                 :::*                    LISTEN      -
tcp        0      0 :::8080                 :::*                    LISTEN      -
bash-5.1# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
73: eth0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP 
    link/ether 02:42:0a:00:01:c9 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.201/24 brd 10.0.1.255 scope global eth0
       valid_lft forever preferred_lft forever
bash-5.1#

Originally created by @cwesterfield on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2778 I'm running my instance on my lan and somehow I have it running on 4443. I'd like to change that to 443 so I can try using NPM on my LAN. Is this possible? ``` nginx-proxy-manager: image: jlesage/nginx-proxy-manager:latest container_name: nginx-proxy-manager networks: LAN: ipv4_address: 10.0.1.201 volumes: - /srv/NGINX-PROXY:/config - /srv/NGINX-PROXY/data/log:/data/log restart: unless-stopped ``` ``` bash-5.1# netstat -ntlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:25000 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.11:38307 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:4443 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:8181 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN - tcp 0 0 :::25000 :::* LISTEN - tcp 0 0 :::3000 :::* LISTEN - tcp 0 0 :::4443 :::* LISTEN - tcp 0 0 :::8181 :::* LISTEN - tcp 0 0 :::8080 :::* LISTEN - bash-5.1# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 73: eth0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:0a:00:01:c9 brd ff:ff:ff:ff:ff:ff inet 10.0.1.201/24 brd 10.0.1.255 scope global eth0 valid_lft forever preferred_lft forever bash-5.1# ```

kerem

2026-02-26 07:33:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:33:13 +03:00

Author

Owner

@cwesterfield commented on GitHub (Mar 30, 2023):

I see in each proxy config the use of 4443. I can use sed to replace them all if that would work.

Where does that template come from? I fear if I don't fix the template, the next proxy host I create will be pointed back at 4443.

@cwesterfield commented on GitHub (Mar 30, 2023): I see in each proxy config the use of 4443. I can use sed to replace them all if that would work. Where does that template come from? I fear if I don't fix the template, the next proxy host I create will be pointed back at 4443.

kerem commented

2026-02-26 07:33:13 +03:00

Author

Owner

@cwesterfield commented on GitHub (Apr 4, 2023):

Found the templates in /opt/nginx-proxy-manager/templates/_listen.conf

We shall see if my changes are overwritten on next update.

@cwesterfield commented on GitHub (Apr 4, 2023): Found the templates in /opt/nginx-proxy-manager/templates/_listen.conf We shall see if my changes are overwritten on next update.

kerem referenced this issue

2026-02-26 08:32:18 +03:00

[PR #4425] Adds feature to Edit Custom certificates. #3880

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

No description provided.

Rows
Columns