Hi Andrew,
when you add a second proxy to the chain, it looks like Graylog would be
reachable from another IP. Your web browser tries to connect back to the
Graylog REST api based on the value of web_endpoint_uri _or_ the
X-Graylog-Server-URL header. Set one of those to the IP that is reachable
from the perspective of your browser.

Cheers,
Marius


On 8 October 2016 at 18:34, Andrew Morgan <andrew.morgan@icuc.social> wrote:

> hello everyone,
> I have an issue at work with graylog I'd like help with please...I
> installed graylog from scratch within my AWS environment using the websites
> AMI, and everything was setup for me.I have a AWS VPC and all traffic goes
> through a load balancer or proxy on port 80. I ave opened port 9000 as
> well. My issue is when I open port 80 and 9000 for where the server is
> located everything works(but this is against my companies policy, so
> traffic should be routed through the proxy), but I am unable to proxy port
> 80 traffic to the public ip address and the private ip address doesnt work.
>
> my proxy config is below:
>
> <VirtualHost *:80>
>     ServerName logserver.net
>     ServerAlias logserver
>     ProxyRequests off
>     ProxyPreserveHost On
> <Location />
>     ProxyPass http://10.1.80.23:9000/
>     ProxyPassReverse http://10.1.80.23:9000/
>         Order allow,deny
>           Allow from all
> </Location>
>
> </VirtualHost>
>
> I also proxy passed port 80 traffic because on the server it uses nginx as
> a proxy as well.
>
>
> My nginx config:
>  server {
>
>
>
>       listen 80;
>
>       location / {
>
>         proxy_pass http://localhost:9000/;
>
>         proxy_http_version 1.1;
>
>         proxy_set_header Host $host;
>
>         proxy_set_header X-Real-IP $remote_addr;
>
>         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>
>         proxy_set_header X-Graylog-Server-URL http://10.1.80.7:9000/api/;
>
>         proxy_pass_request_headers on;
>
>         proxy_connect_timeout 150;
>
>         proxy_send_timeout 100;
>
>         proxy_read_timeout 100;
>
>         proxy_buffers 4 32k;
>
>         client_max_body_size 8m;
>
>         client_body_buffer_size 128k;
>
>       }
>
>       error_page 502 /502.html;
>
>       location  /502.html {
>
>         internal;
>
>       }
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Graylog Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to graylog2+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/graylog2/a29c4498-23e6-470d-a0c9-fb5978be597e%40googlegroups.com
> <https://groups.google.com/d/msgid/graylog2/a29c4498-23e6-470d-a0c9-fb5978be597e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Developer

Tel.: +49 (0)40 609 452 077
Fax.: +49 (0)40 609 452 078

TORCH GmbH - A Graylog Company
Poolstraße 21
20335 Hamburg
Germany

https://www.graylog.com <https://www.torch.sh/>

Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
Geschäftsführer: Lennart Koopmann (CEO)

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/CAMqbBbJHTtgp7OfB6jGUxrysCKwMM_DAXPEN3ZshipxJhgA9Cw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to