4 posts • Page 1 of 1
Hi, do you mean to Unimus itself? There are multiple options:
- completely disable access to the web GUI on a firewall "in front of" your Unimus server
- deploy iptables (or other firewall) on the server itself and only allow access from "known good" sources
- deploy NGINX as a reverse-proxy "in front of" Unimus and use "allow/deny" statements
- use Radius and allow login only from specific client IPs
In general, this restriction should be either on the connection level (firewalls, reverse proxy) or on the auth level (using external auth such as Radius or NPS).
Happy to provide more info - but the best place for this kind of access control would indeed be on the firewall responsible for that server, or to deploy iptables and protect the server directly.