Single nic deployed, the solution of Justin worked.
Thank you,
Paulo
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253833,253873#msg-253873
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Single nic deployed, the solution of Justin worked.
Thank you,
Paulo
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253833,253872#msg-253872
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Correct Justin.. beginners mistake . disabled the firewalld but
forgot selinux ...
I install it in CentOS 7.0.
Do you know how to troubleshoot it when sometimes the proxy doesn't go
through and other times works ??
Paulo
Posted at Nginx Forum:
http://forum.nginx.org/read.php?
ip.forwarding on?
On 2014-10-08, 2:21 PM, pharasyte wrote:
Hello,
Which distro are you using?
The first thing that comes to mind with this type of issue is that Selinux
is enabled and blocking nginx from making connections to the upstream. You
can test if this is the case by turning Selinux of
Hello,
Which distro are you using?
The first thing that comes to mind with this type of issue is that Selinux
is enabled and blocking nginx from making connections to the upstream. You
can test if this is the case by turning Selinux off and seeing if that
resolves the issue.
This of course only
Hi all,
I very new to NGINX, but thought that it might be the best tool to achieve a
reverse proxy ( in the DMZ ) for an internal HTTPS server.
Unfortunately it isn't working and I get 502 Bad Gateway message if I check
in the error Log I see :
2014/10/07 17:38:27 [crit] 2606#0: *1 connect() to
