You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to proxy tcp traffic to different servers depending on which domain has been used. Basically a simple tcp reverse proxy.
When not specifying a domain, this works great - but only for a single server:
proxy :25565 192.168.14.10:25565 {
host test1.domain.com
tls off
}
This also, despite having "host" configured as a single domain, proxy's all traffic hitting the WAN-IP with port 25565.
Now, when trying to proxy different domains to different servers like this:
proxy test1.domain.com:25565 192.168.14.10:25565 {
host test1.domain.com
tls off
}
I'm getting the following error: Listen: listen tcp [WAN-IP-HERE]:25565: bind: cannot assign requested address
Since the host-directive doesn't seem to do anything, stuff like
proxy :25565 192.168.14.10:25565 {
host test1.domain.com
tls off
}
proxy :25565 192.168.14.11:25565 {
host test2.domain.com
tls off
}
also doesn't work: Listen: listen tcp :25565: bind: address already in use
Have I just done something wrong or is there an issue with the proxy?
The text was updated successfully, but these errors were encountered:
I'm trying to proxy tcp traffic to different servers depending on which domain has been used. Basically a simple tcp reverse proxy.
When not specifying a domain, this works great - but only for a single server:
This also, despite having "host" configured as a single domain, proxy's all traffic hitting the WAN-IP with port 25565.
Now, when trying to proxy different domains to different servers like this:
I'm getting the following error:
Listen: listen tcp [WAN-IP-HERE]:25565: bind: cannot assign requested address
Since the host-directive doesn't seem to do anything, stuff like
also doesn't work:
Listen: listen tcp :25565: bind: address already in use
Have I just done something wrong or is there an issue with the proxy?
The text was updated successfully, but these errors were encountered: