Contact
Menu
Mihonator/DocumentationIn development

Using Mihonator

Find what is getting in the way

Review configuration audits and automatic fixes, inspect logs, and resolve profile or connection problems.
On this page

The profile will not import

HTTP 403 or 404: copy a fresh subscription URL from your provider. Confirm the subscription is active and that you copied the configuration endpoint rather than an account page.

YAML or missing-proxy errors: select the Mihomo / Clash Meta format at your provider. An HTML page, a single proxy share link, or a configuration for another client is not a complete Mihomo profile.

Device limit reached: remove an unused device in your provider’s account panel or contact the provider. Reinstalling the client is not a reliable way to resolve a device limit.

The tunnel will not start

  • macOS: approve the helper’s Touch ID or password prompt. Keep the app in Applications and run the GUI as your regular user.
  • Linux: check that the package installed successfully and that the system provides /dev/net/tun.
  • Android: approve the VPN permission dialog and disconnect any other VPN that is using the system VPN service.

Connected, but no traffic

  1. Check the profile’s quota and expiry with your provider.
  2. Open Proxies and try another available node in a selector group.
  3. Check whether the affected destination should use a proxy under this profile’s rules.
  4. Open the logs and look for DNS, connection, or configuration errors around the failed request.

A successful tunnel start and a successful proxy connection are separate checks. A timeout can also come from an unavailable test destination.

Configuration audit and automatic fixes

Mihonator audits a parsed profile before applying it to the connection engine. It detects known configuration issues and automatically applies supported fixes.

  • Routing-loop protection: prevents traffic to the tunnel’s own addresses from being routed back into the tunnel.
  • Desktop TUN and DNS checks: on macOS and Linux, the audit adjusts incompatible TUN settings, resolves fake-IP range conflicts with excluded routes, and corrects DNS settings that can cause resolution loops.

Open Settings → Logs → Problems to review the findings. Each entry explains the issue and includes Auto-fixed for an applied correction or Hint for a change that needs your attention.

Automatic fixes apply to the active configuration in memory. To keep a correction in your subscription, update the source profile or share the finding with your provider.

Collect useful logs

Open Settings, then Logs. Reproduce the problem, inspect the relevant log level, and use the save control to export the output. Select Problems to focus on audit findings and other diagnostics.

For a macOS tunnel-helper failure, the helper log is stored at:

macOS helper log
~/Library/Logs/Mihonator/mihonator-helper.log

When contacting support, include the app version, operating system, what you tried, and the relevant error. Remove subscription tokens, credentials, and private addresses from anything you share.