Troubleshooting

Edit online

Information about how to troubleshoot a problem with IP filtering.

Admin locked out

The error message 401 Unauthorized is displayed when you try to verify or access the system.

Possible cause: Your current IP address is blocked by the rules that you just created.

To troubleshoot this issue, try the following steps:

  1. Wait for up to 5 minutes. The system has a safety mechanism that automatically disables unverified configurations after approximately 5 minutes (timing may vary by environment).
  2. After five minutes, you can access the system again from your original IP address.
  3. Review your IP filtering rules carefully before reapplying.
  4. Make sure that your current IP address is explicitly allowed in the rules.

To prevent this issue, consider the following steps:

  • Always double-check your rules before applying.
  • Test with `denyAll: false` first to ensure your IP is correctly identified.
  • Keep a backup access method (different network/VPN) available during initial setup.

Configuration not applied

IP filtering rules are not working.

Possible cause: Configuration was not verified within the time window.

To troubleshoot this issue, try the following steps:

  1. Check whether the configuration exists: 
    GET /api/settings/ip-filtering

    If it returns 404, the configuration was auto-disabled.

  2. Recreate the configuration and verify it immediately. 
    PATCH /api/settings/ip-filtering/verify

Unable to determine the current IP address

Unable to determine which IP address must be used to allow the rules.

To troubleshoot this issue, try the following steps:

  1. Contact your network administrator to determine your gateway's outgoing IP address.
  2. Use a service such as https://api.ipify.org to check your public IP address.
Note: Pour outgoing gateway or proxy IP address is used but not your local machine IP adress

Rules are not working as expected

Access is allowed or denied contrary to the expectations.

Possible cause: Conflict on rule precedence or CIDR notation.

To troubleshoot this issue, try the following steps:

  1. Check whether the CIDR notation is correct, use online CIDR calculators.
  2. Check the rule order. The first rule has highest priority. You must place more specific rules before broader rules.
  3. Test with denyAll: false to determine which IP addresses are matched.
  4. Check whether enabled: true is set in the IP configuration.

500 Internal Server Error

API calls return 500 errors.

Possible cause: Invalid configuration format or system error

To troubleshoot this issue, try the following steps:

  1. Validate the JSON syntax.
  2. Make sure that all required fields are present (enabled, denyAll, rules).
  3. Check whether CIDR notation is valid, for example, 1xx.168.1.0/24, not 1xx.168.1.0/33.
  4. Check whether API token has correct permissions.
  5. Review server logs for detailed error messages.