Repository navigation
Troubleshooting
Open Changes: the errors are listed in red under the change list, each naming what is wrong, for example
policy 14 "wifi-rule-14": unknown src_addr reference "Kids_Devices". Fix that item and commit again. The
API shows the same list: POST /api/v1/config/validate.
- Policies: the ⋮ button at the right end of the row, or right-click the row → Delete.
- Objects, profiles, feeds: the trash icon at the end of the row. If it refuses, the message says what still uses the object.
Password logins over SSH are always off. Add a key under System → Admins → SSH keys and commit (see Remote Access: SSH, API and CLI).
- Log & Report: filter by the device's IP. A denied connection shows which policy denied it (or none: no policy matched, so it was denied by default).
- Give the deny policy
log: denyif it is not logged yet. - Remember: policies match top to bottom, first match wins.
- Traffic to the box itself (web UI, SSH) depends on the interface's allowed access, not policies.
- Log & Report shows DNS filter, web filter and app control blocks with the list or category.
- Add the domain to the profile's allow domains (DNS filter or web filter), commit.
- The threat feed lookup box tells you which feed lists an address or domain.
-
download: HTTP 404/403or a timeout: the list is gone or blocks automated downloads. Remove it. -
rejected: the update has no valid entries: wrong type or format, or an empty list. -
this is a domain list: change the feed type todomainand use it in a DNS filter profile. -
rejected: ... more than 90% fewer: the download looked broken; the last good copy is still in use.
Look for denies of your isolation policy in Log & Report (filter by its ID) and add an exception policy above it for what the device needs (for example Wi-Fi → Home Assistant).
On networks with a DNS filter, the box asks Private Relay to turn off so the filter can't be bypassed. Remove the DNS filter profile from that network's policy if you want Private Relay there.
If you committed with a confirmation window, wait: it rolls back on its own. Otherwise, from the console:
menu option 4 (shell), then goblin -c "rollback <revision>" with the last good revision (System →
Revisions lists them; goblin -c "history" on the shell).
System → Diagnostics runs checks from the box itself (admins only):
- Ping: reachability and latency to a host, optionally out of a specific interface or VLAN. Useful when one network works but another does not — ping the same host from each source interface.
-
Traceroute: which hop stops answering on the way to a host. A
*row is a hop that did not answer (often a router that blocks probes); look for where real hops end. - DNS lookup: what the resolver returns for a name or IP (PTR). Ask "this firewall" to test Unbound, or an upstream IP to compare — different answers point at the box's DNS configuration.
At most two diagnostics run at once; if one is already busy you get "Another diagnostic is running; try again in a moment." Traceroute can take up to a minute — the button stays disabled with a spinner until it finishes.
Open an issue with: the Goblin Gate version (System → About), what you did, what you expected, and the
relevant Log & Report lines or journalctl -u goblind output. Never post backups, tokens or config files
without removing secrets.
Getting started
Network
- Interfaces and VLANs
- Objects
- Firewall Policies
- NAT, Port Forwards and UPnP
- DHCP and DNS
- Multi-WAN and Routing
- VPN
Security
System