Outbound Proxy for outbound connections. #1729

New issue

Closed

opened 2026-02-26 07:32:15 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:32:15 +03:00

Owner

Originally created by @tuxpowered on GitHub (Dec 13, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2479

In some cases, a user may want to proxy all outbound connections, thru a specific IP/Hostname. At first it looked like the streams would be able to do so potentially, however, you must specify a resolvable host, and are unable to use Nginx built-in variables.

An example of where a forwarding/outbound proxy is useful:
Multiple phone systems that do not have a dedicated IP address. But the web application, such as a web softphone (ws/wss) needs to make an outbound connection and 'know' the public IP.

This allows a regular reverse proxy to allow inbound connections and a separate outbound/forwarding proxy to push data out with the shared IP.

Describe the solution you'd like
There appear to be 2 common ways to implement HTTP/S forwarding proxy, and streams appear to be one method, but there is no method to use built-in variables to specify custom configurations, and you are only able to specify real destinations. Allowing the use of $variables or adding a custom option like the forwarding proxy can resolve this issue.

Describe alternatives you've considered
Open to other ideas and suggestions.

Originally created by @tuxpowered on GitHub (Dec 13, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2479 In some cases, a user may want to proxy all outbound connections, thru a specific IP/Hostname. At first it looked like the streams would be able to do so potentially, however, you must specify a resolvable host, and are unable to use Nginx built-in variables. An example of where a forwarding/outbound proxy is useful: Multiple phone systems that do not have a dedicated IP address. But the web application, such as a web softphone (ws/wss) needs to make an outbound connection and 'know' the public IP. This allows a regular reverse proxy to allow inbound connections and a separate outbound/forwarding proxy to push data out with the shared IP. **Describe the solution you'd like** There appear to be 2 common ways to implement HTTP/S forwarding proxy, and streams appear to be one method, but there is no method to use built-in variables to specify custom configurations, and you are only able to specify real destinations. Allowing the use of $variables or adding a custom option like the forwarding proxy can resolve this issue. **Describe alternatives you've considered** Open to other ideas and suggestions.

kerem

2026-02-26 07:32:15 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:32:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 2, 2024):

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

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

kerem commented

2026-02-26 07:32:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 19, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 19, 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#1729

No description provided.

Rows
Columns