mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #1354] Problem setting up stream #1073
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#1073
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 @DejonckheereWard on GitHub (Aug 27, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1354
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
While setting up a stream, an error shows up saying "data.forwarding_host should match exactly one schema in oneOf"
Nginx Proxy Manager Version
Verstion 2.9.8
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Creating a new stream
Screenshots
Operating System
Photon Os 3.0, build 11dd065
Additional context
This issue didn't happen before in a previous install, we upgraded and re-setup nginx proxymanager today because of issues upgrading.
I don't seem to find any logs about this issue on the server either.
Docker version used: 19.03.15, build 99e3ed8
@victorelec14 commented on GitHub (Aug 27, 2021):
+1 , you can add a Hostname (with this IP) but direct IP give me the same error.
Nginx Proxy Manager v2.9.8
Docker version 20.10.7, build 20.10.7-0ubuntu1~20.04.1
@victorelec14 commented on GitHub (Aug 27, 2021):
@BjoernAkAManf is a problem with you commit for v2.9.8 ?
@tbringuier commented on GitHub (Aug 31, 2021):
is a fix planned ?
@BjoernAkAManf commented on GitHub (Aug 31, 2021):
Might want to try the fix in the aforementioned PR.