9 Feb 2012 20:59
nginx reverse proxy in front of netdot
Hello Community,
I have installed netdot, v0.9.10, following the online manual. Everything is working. I have a few other services running on that box
and I have configured nginx to proxy to Apache2 which listens on localhost only, on 8080 port.
All other services work ok but netdot throws out a 403 HTTP Error - Access to the webpage was denied. Do you know does this
happen? I have switched Apache2 to listen on the external interface (eth0) on port 8080 and it works as it should.
Follows the nginx configuration pertaining netdot:
location /netdot/ {
proxy_pass http://localhost:8080/netdot/;
proxy_redirect off;
proxy_set_header Host localhost;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
include /etc/nginx/conf.d/proxy.options;
}
Has anybody encountered this kind of issue. Do you know how can I solve it?
Thank you and a wonderful day to everybody,
Valentin Bud
<div>
<p>Hello Community,</p>
<div><br></div>
<div>I have installed netdot, v0.9.10, following the online manual. Everything is working. I have a few other services running on that box</div>
<div>and I have configured nginx to proxy to Apache2 which listens on localhost only, on 8080 port.</div>
<div><br></div>
<div>All other services work ok but netdot throws out a 403 HTTP Error - Access to the webpage was denied. Do you know does this</div>
<div>happen? I have switched Apache2 to listen on the external interface (eth0) on port 8080 and it works as it should.</div>
<div><br></div>
<div>Follows the nginx configuration pertaining netdot:</div>
<div>
<div>location /netdot/ {</div>
<div> proxy_pass <a href="http://localhost:8080/netdot/">http://localhost:8080/netdot/</a>;</div>
<div> proxy_redirect off;</div>
<div><br></div>
<div> proxy_set_header Host localhost;</div>
<div> proxy_set_header X-Real-IP $remote_addr;</div>
<div> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;</div>
<div><br></div>
<div> include /etc/nginx/conf.d/proxy.options;</div>
<div> }</div>
</div>
<div><br></div>
<div>Has anybody encountered this kind of issue. Do you know how can I solve it?</div>
<div><br></div>
<div>
Thank you and a wonderful day to everybody,</div>
<div>Valentin Bud</div>
<div>-- <br>w: <a href="http://databus.ro/blog" target="_blank">http://databus.ro/blog</a><div>in: <a href="http://www.linkedin.com/pub/valentin-bud/9/881/830" target="_blank">http://www.linkedin.com/pub/valentin-bud/9/881/830</a>
</div>
<div>t: <a href="https://twitter.com/valentinbud" target="_blank">https://twitter.com/valentinbud</a>
</div>
<br>
</div>
</div>
Carlos suggested I clear the ADD_UNKNOWN_DP_DEVS flag which had been
configured to "one" in my etc/Site.conf file.
After making this configuration change, the same "discovery" process
took a bit more than four (4!) minutes. 
Here is my quandry: I clearly don't want the discovery process to get
carried away searching the entire network here at Michigan. 
RSS Feed