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 have tried this several times since I have been using sniproxy and just tried it again but cannot get it tro work.
I need to be able to run a NGINX server hosting web pages as well as sniproxy on the same server.
I understand the way to do this is to use fallback, so I have configured nginx to listen on 8080 and need sniproxy to fallback to 8080 so that requests coming in for a local web page are displayed, right now that is not happening.
OK, I think I just figured it out, not sure if this is the correct way but it appears to work, in my table, before the wildcard redirect I add entries for local domain names to be served.
I use a UNIX socket for connection to the fallback nginx server. It looked like in your first post, you had Nginx listening on a specific IP which was not the loopback address so that could have been an issue.
sniproxy.conf:
listen 80 {
proto http
table vhosts
fallback unix:/var/run/nginx-http.socket
}
listen 443 {
proto tls
table vhosts
fallback unix:/var/run/nginx-https.socket
}
I have tried this several times since I have been using sniproxy and just tried it again but cannot get it tro work.
I need to be able to run a NGINX server hosting web pages as well as sniproxy on the same server.
I understand the way to do this is to use fallback, so I have configured nginx to listen on 8080 and need sniproxy to fallback to 8080 so that requests coming in for a local web page are displayed, right now that is not happening.
Here's the config setting for sniproxy:
and here's the config for NGINX:
I can connect to the webserver directly on 8080 but of course that's no good as it needs to be accessed via 80
The connection just hangs and eventually times out with 'Backend not Available'
what am I doing wrong and / or can this be done ??
The text was updated successfully, but these errors were encountered: