Hi Jan thanks for the answer
1- I changed http_publish_uri as you suggested -
a- Still getting Error 401
b - I cannot browse “API-BROWSER” page with this change from my personal computer since it changed the HTTP URI to internal(is this normal)
Yes I have a API token configured in Graylog and pasted that API token into sidecar.yml in Graylog sidecar.
I am suspecting of NGINX conf which is for /api/ directory as below:
was not to clear your problem but general advice. You can still reach the API browser - just eh button sends you wrong (add the /api/api-browser to your Graylog URI).
Hi Jan thanks for your perspective and prompt response-
1- one thing- I was thinking if API page is accessible through external world then sidecar can access since sidecar config which resides in /etc/graylog/sidecar/sidecar.yml
is like below:
where I concluded that API shall be accessible from outside- am I wrong?
because this URL utilizes API to authenticate to Graylog server.
2- working config doesn’t expose API somehow to outside- if you don’t have “/api/” location enabled separately- which I did because of my point in the 1 st answer.
Other directives is for cookie caching and resolving problems related with SSL sessions together with DNS issues of Nginx.
For the URL you sent- it is mostly the same- maybe very small variation but I will try again with standard guidanceand let you know about it too.
I believe problem is exposing API thorugh SSL but not being able to authenticate due to somehow authentication token is not passed properly with NGINX config.
You missed something entirely and screwed the configuration for some reason. With the scattered information so far it is nearly impossible to find the gap.
The server_url in your sidecar configuration looks ok - that you get the 401 error indicates that you do not have a token configured (or have that commented … )
Having a proxy serving Graylog is not unlikely and you do not need any special tricks to make that. run.
Hi,
I found it finally. solution was the basic config.
Problem was the disabled token authentication in authentication menu- I disabled it several weeks ago then needed ro re-enable it.
It would be good to have a warning while configuring tokens to show that token authentication is disabled- since now it seems totally independent.