New Graylog 5 Open Deployment Inaccessible from web interface

[gsmith]

Hey @lawdfarquhar

I really dont think you need to go that route, DNS uses port 53 but does listing to all ports unless specified.

For example if i create a graylog server and called it lawdfarquhar.com IP 192.168.1.100. I then create a A record and you good for that domain and depending on the DNS server setting on how far can reach. meaning is it a lab or production. Also if you have graylog on Linux node, what I do is set the /etc/hosts file like so…

[root@graylog mongodb]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.100 lawdfarquhar.com

[root@graylog mongodb]#

With the /etc/hostname file, I ensure its the same as the /etc/hosts file and the certitificates I create.

EDIT: @lawdfarquhar

If you do go with a reverse proxy might want to check out this post.

Nginx Config Examples

For those of you who use Nginx as a reverse proxy or load balancer, you may find these configuration files useful: Here’s the example main nginx config I use for load balancing tcp/udp connections:

nginx.conf

user nginx; worker_processes 4; error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include /etc/nginx/mime.types; default_type application/octet-stream; log_format main '$remote_addr - $r…