[GH-ISSUE #1051] Custom Scheme #877

New issue

Closed

opened 2026-02-26 06:34:47 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:34:47 +03:00

Owner

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

Hi All,
I am having trouble finding a reliable example/config for what I am trying to do. So I understand that someone might say to use a Stream, but I cannot do that as I require a certificate to work.

So I have a service (Desktop Central) that works with multiple ports i.e 8383, 8027, 8443 and 8031. ALL these ports use HTTPS and they only allow you to specify a single FQDN for communication between the agent and the server, so I am forced to use "example.domain.com:8383", "example.domain.com:8027", "example.domain.com:8443" and "example.domain.com:8031" for the agents to communicate back to desktop central. Does anyone have a link or can provide some sort of information as to how to do this via the Advanced Configuration on NPM.

Originally created by @barendbotes on GitHub (Apr 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1051 Hi All, I am having trouble finding a reliable example/config for what I am trying to do. So I understand that someone might say to use a Stream, but I cannot do that as I require a certificate to work. So I have a service (Desktop Central) that works with multiple ports i.e 8383, 8027, 8443 and 8031. ALL these ports use HTTPS and they only allow you to specify a single FQDN for communication between the agent and the server, so I am forced to use "example.domain.com:8383", "example.domain.com:8027", "example.domain.com:8443" and "example.domain.com:8031" for the agents to communicate back to desktop central. Does anyone have a link or can provide some sort of information as to how to do this via the Advanced Configuration on NPM. ![image](https://user-images.githubusercontent.com/80952223/116554965-186db500-a8fc-11eb-9065-2f046982468d.png) ![image](https://user-images.githubusercontent.com/80952223/116555007-291e2b00-a8fc-11eb-9a9d-5dc1a720adc7.png)

kerem

2026-02-26 06:34:47 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 06:34:47 +03:00

Author

Owner

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

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

@github-actions[bot] commented on GitHub (Mar 12, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:34:47 +03:00

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 24, 2025): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns