graylog 通过NGINX 反向代理配置

具体参考: https://github.com/Graylog2/graylog2-server/issues/5702
Graylog 3.0.1 released on April 1st, 2019 fixes this issue:
Fix running Graylog web interface under a path prefix. Graylog2/graylog2-server#5702 Graylog2/graylog2-server#5703
In addition, new version fixes these other [issues](http://docs.graylog.org/en/3.0/pages/changelog.html).
graylog版本日志以及修改的问题：http://docs.graylog.org/en/3.0/pages/changelog.html

How does the web interface connect to the Graylog server?
The web interface is fetching all information it is showing from the REST API of the Graylog server. Therefore it needs to connect to it using HTTP(S). There are several ways how you can define which way the web interface connects to the Graylog server. The URI used by the web interface is determined in this exact order:
If the HTTP(S) client going to the web interface port sends a X-Graylog-Server-URL header, which contains a valid URL, then this is overriding everything else.
If http_external_uri is defined in the Graylog configuration file, this is used if the aforementioned header is not set.
If http_publish_uri is defined in the Graylog configuration file, this is used if the aforementioned http_external_uri is not set.
If none of the above are defined, http://$http_bind_address is used.
The web interface assets (e.g. the index.html, CSS and JavaScript files) are accessible at the URI root (/ by default) and the REST API endpoints are accessible at the /api path.
Example:
Setting http_bind_address to 10.0.0.1:9000 configures the Graylog server with the following URLs.
Web interface: http://10.0.0.1:9000/
REST API: http://10.0.0.1:9000/api/