Accessing API button


(Dave) #1

Hello!

Trying to accomplish what this guy did here but failed :frowning:

This is how i have it configured.

rest_listen_uri = http://127.0.0.1:9000/graylog/api/
#rest_transport_uri = http://192.168.1.1:9000/api/
web_listen_uri = http://127.0.0.1:9000/graylog
#web_endpoint_uri =
#http_proxy_uri =

Using nginx to access through web browser (https://<routable-fqdn>/graylog) works

   location /graylog {
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Graylog-Server-URL https://$server_name/graylog/api;
    proxy_pass       http://127.0.0.1:9000/graylog;
    }

With the above setup the API button goes to the loopback address, http://127.0.0.1:9000/graylog/api/api-browser, which makes sense since i dont have rest_transport_uri set. Manually typing https://<routable-fqdn>/graylog/api/api-browser works

Im sure it’s something very simple
Any input is appreciated!

Thank you!
dave


Graylog behind nginx sub directory how-to configure
(Dave) #2

When i make the following changes, my graylog-server dies:

rest_listen_uri = http://0.0.0.0:9000/graylog/api/
rest_transport_uri = http://<fqdn>:9000/graylog/api/

Not sure why

Note: graylog and elasticsearch all live in the same box


(Jan Doberstein) #3

@davama

that is a known issue: https://github.com/Graylog2/graylog2-server/issues/1576


(Dave) #4

@jan

Thank you for replying!
That ticket is quite old.
I’ll reply on that ticket, hopefully get some traction.


(system) #5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.