mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #2212] listener port #1583
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1583
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sunO2 on GitHub (Aug 20, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2212
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
@the1ts commented on GitHub (Aug 20, 2022):
This issue has zero content what are you trying to say by listener port?
@the1ts commented on GitHub (Aug 27, 2022):
close off?
@mxwmnn commented on GitHub (Nov 25, 2022):
I think he wants to define optional another listener ports instead the defaul 80,443. I need it to for the Matrix federation port forwarding cause matrix expects a SSL Certificate on port 8448
@the1ts commented on GitHub (Nov 25, 2022):
Can't you just use the fact that certs from NPM are saved in your data volume which you can share with as many containers as you wish? So NPM can get the cert that other containers use. You just have to restart the other container after NPM gets a new cert which can be done on a schedule since after 60 days of a 90 day cert NPM will renew. So a simple reboot every Sunday would perhaps work.
@github-actions[bot] commented on GitHub (Feb 11, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 28, 2025):
Issue was closed due to inactivity.