# New Graylog 5 Open Deployment Inaccessible from web interface

**URL:** <https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367>\
**Category:** Graylog Central (peer support)\
**Tags:** curl\
**Created:** [January 19, 2023, 6:59pm UTC](https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367 "2023-01-19T18:59:42Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![lawdfarquhar](https://avatars.discourse-cdn.com/v4/letter/l/fbc32d/32.png) [@lawdfarquhar](https://community.graylog.org/u/lawdfarquhar)\
**Post date:** [January 31, 2023, 1:11pm UTC](https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367/22 "2023-01-31T13:11:04Z")

</div>

Correct. The only ports it cares about as far as A records are concerned are 80/443, meaning that I can’t make an A record for my FQDN that points to xxx.xx.80.9:9000. My guess is I’m going to have to setup a proxy in order to serve the page to my FQDN instead of xxx.xx.80.9:9000. Either that or change the default port to 443 but I think I would have to give Graylog root privs to do that and I don’t wanna do that.

---

<div class="post-metadata">

**Author:** ![gsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gsmith/32/1222_2.png) [@gsmith](https://community.graylog.org/u/gsmith)\
**Post date:** [January 31, 2023, 10:42pm UTC](https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367/23 "2023-01-31T22:42:45Z")

</div>

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](http://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…

```auto
[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](https://community.graylog.org/t/nginx-config-examples/20738):
>
> 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…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [February 14, 2023, 10:43pm UTC](https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367/24 "2023-02-14T22:43:19Z")

</div>

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

[Previous page](https://community.graylog.org/t/new-graylog-5-open-deployment-inaccessible-from-web-interface/27367.md?page=1)