mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #288] Netdata multiple backends #257
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#257
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 @modem7 on GitHub (Feb 5, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/288
With this particular image, any ideas on how best to transfer my current setup for netdata?
I'm a bit stumped on setting upstreams!
Example from https://docs.netdata.cloud/docs/running-behind-nginx/
@modem7 commented on GitHub (Feb 5, 2020):
Ah pants, looks like this is pending https://github.com/jc21/nginx-proxy-manager/issues/156
@jc21 commented on GitHub (Feb 7, 2020):
Yeah you'll need upstreams support. You can add those upstreams in an undocumented custom nginx config file, but even then the wildcarded proxy_pass would be an issue..
@modem7 commented on GitHub (Feb 19, 2020):
Closing pending #156 - no point having duplicate incidents