# Security setup for server

**URL:** <https://community.datagerry.com/t/security-setup-for-server/636>\
**Category:** Community Support\
**Created:** [July 24, 2024, 4:27pm UTC](https://community.datagerry.com/t/security-setup-for-server/636 "2024-07-24T16:27:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shadowtech](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@Shadowtech](https://community.datagerry.com/u/Shadowtech)\
**Post date:** [July 24, 2024, 4:27pm UTC](https://community.datagerry.com/t/security-setup-for-server/636/1 "2024-07-24T16:27:45Z")

</div>

Is it possible to lock down the default port 4000 to only listen on the loop back interface after the NGINIX reverse proxy is setup.

Alternate idea is to allow it to only respond to a specific ip if a separate NGINIX box is setup as a proxy and is the only device that can talk to the server?

I’m setup on an Ubuntu server at the moment.

---

<div class="post-metadata">

**Author:** ![Shadowtech](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@Shadowtech](https://community.datagerry.com/u/Shadowtech)\
**Post date:** [July 24, 2024, 4:35pm UTC](https://community.datagerry.com/t/security-setup-for-server/636/2 "2024-07-24T16:35:15Z")

</div>

Would the simplest method be to just enable UFW and setup a rule to allow inbound connections on port 80 and 443. Also add in 22 for SSH from a restricted ip set if wanted.