The proxy binds to 0.0.0.0 (all interfaces) on port 11300 by default, so it
is reachable from your LAN. Restrict access to your LAN.
# Allow established connections
nft add rule inet filter input ct state established,related accept
# Allow loopback
nft add rule inet filter input iif lo accept
# Allow LAN access to port 11300
nft add rule inet filter input tcp dport 11300 ip saddr 192.168.0.0/16 accept
nft add rule inet filter input tcp dport 11300 ip saddr 10.0.0.0/8 accept
nft add rule inet filter input tcp dport 11300 ip saddr 172.16.0.0/12 accept
# Drop all other traffic to port 11300
nft add rule inet filter input tcp dport 11300 dropTo persist, save rules:
sudo nft list ruleset > /etc/nftables.conf
sudo systemctl enable nftables# Allow LAN access to port 11300
sudo iptables -A INPUT -p tcp --dport 11300 -s 192.168.0.0/16 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 11300 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 11300 -s 172.16.0.0/12 -j ACCEPT
# Drop all other traffic to port 11300
sudo iptables -A INPUT -p tcp --dport 11300 -j DROP
# Save rules
sudo apt install iptables-persistent
sudo netfilter-persistent save# Allow from LAN only
sudo ufw allow from 192.168.0.0/16 to any port 11300
sudo ufw allow from 10.0.0.0/8 to any port 11300
sudo ufw allow from 172.16.0.0/12 to any port 11300
# Enable firewall
sudo ufw enableIf the proxy should only be accessible from the same machine, bind to localhost:
[server]
host = "127.0.0.1"No firewall rules are needed in this case.
EggPool does not open a connection to Eggsearch and does not expose an MCP or hosted-tool route. Clients that execute tools do that in their own process. See Tool execution.
Legacy inference clients use the shared server key only while the database is
legacy_unmigrated. After local identity initialization, EggPool retires that
key and requires personal API tokens for inference and browser sessions for
dashboard administration. Remote browser password login must reach EggPool
through operator-managed HTTPS termination. Add the proxy's exact peer IP to
[security].trusted_proxies; only that peer's single
X-Forwarded-Proto: https header is trusted. Browser sign-in and failed
personal-token throttling use one literal X-Forwarded-For client IP only
from that trusted peer; the proxy must replace the incoming header with the
client's IP. Missing, duplicated, or chained values fall back to the proxy peer. The proxy should
preserve the public Host header, and the firewall should allow port 11300
only from that proxy. Do not expose the backend port directly to clients when
trusting a proxy.
Loopback HTTP sign-in is supported for local administration. The optional
[security].allow_insecure_web_auth = true setting permits remote HTTP only
for isolated development and logs a warning because passwords and session
cookies then travel without TLS.
# Check listening ports
ss -tlnp | grep 11300
# Test access from another machine
curl http://<proxy-ip>:11300/v1/healthz