Node HandbookNODE HANDBOOK中文
Hiddify · macOS

Hiddify on macOS: “duplicate column name: profile_override”

The message contains an ALTER TABLE statement, which places the failure in the application's local database migration. Nothing about your subscription, your nodes or your network has been evaluated at that point.

Node Handbook editorial team ·

Which layer the error belongs to

What you seeMost likely layerNext step
duplicate column name: profile_override with ALTER TABLE "profile_entries" RENAME COLUMNSQLite schema migration colliding with an existing columnPreserve the original, take an offline copy, then collect version and read-only schema facts
A duplicate-column error naming a different table or columnA different migration or a different version's problemKeep the full table name, column name, SQL and version; do not apply this page's conclusion
invalid yaml, Failed to import subscription content or an HTTP errorSubscription fetch or parseUse the subscription update path
Import succeeds, nodes appear, requests fail after connectingProxy connection or local networkRecord a real request on the same network

SQLite raises an error when RENAME COLUMN targets a name that already exists in the same table. That supports the reading “the migration statement met an existing target column”. It does not explain why the database reached that state, and it says nothing about whether the subscription content is valid.

The public reports

Hiddify issue #2078 was first filed on macOS Monterey with Hiddify 4.1.1, failing while importing a clipboard subscription. A later commenter on Hiddify 5.5.5 for macOS reported the same column conflict, this time affecting startup, and disclosed that the database showed user_version = 4 with both test_url and profile_override already present in profile_entries.

Two reports, two triggers, two database states. They share the error text; they are not one verified reproduction. As of 18 November 2026 the issue remained open, and the latest release tag checked was v5.5.5 — which is itself named in a later comment reporting the error. No maintainer-confirmed general fix appears in the public thread.

Collect evidence safely

  1. Record the context. Full Hiddify version, macOS version, the action that triggered the error, and whether you had just upgraded, migrated or restored from a backup. Record reproduction steps only — never the subscription link, token or the database file.
  2. Quit Hiddify completely. Find the database path the log actually mentions. Data paths differ between installations and versions; do not assume everyone uses the same location.
  3. Copy the database offline and keep the original. This site has not verified backup integrity or restore capability, and a non-zero file size does not prove a copy is usable. Never copy or edit the database while the app is running, and do not delete the data directory, uninstall and clean residue, or overwrite the old backup first.
  4. Read the copy read-only. If you are comfortable with SQLite, point the tool at the copy with a read-only URI:
    sqlite3 'file:/absolute/path/db.sqlite?mode=ro' 'PRAGMA user_version;'
    sqlite3 'file:/absolute/path/db.sqlite?mode=ro' 'PRAGMA table_info(profile_entries);'
  5. Report with masked details. If the output shows profile_override already present, keep the read-only output and the SQL line from the error, then add your versions and steps to issue #2078. PRAGMA table_info output is not a repair instruction, and schema dumps can contain identifiers — mask them before posting.

Why the user_version edit is not a fix

One comment in the thread describes a 5.5.5 case where, after backing up, changing PRAGMA user_version from 4 to 5 let the app open normally. That change tells the application a migration has been completed. It does not establish that every change in that migration was applied, or that the data is consistent.

It is one user's observation on one database. Editing schema, deleting db.sqlite, or re-importing your only subscription in the hope of clearing the error all trade a diagnosable state for an undocumented one.

What actually helps

  • Keep a launchable state. If the app opens sometimes, do not clear application data while it still works.
  • Separate the stages. Note whether the failure happens before the window appears, during import, or after a successful launch. The three produce different reports.
  • Treat versions as variables. If you upgrade, back up first, keep the previous version number and the error text, and verify launch, core start and one real request separately afterwards.
  • Do not publish the database. It can contain subscription metadata and identifiers that are not visible in the UI.

Scope and limits

This page applies only to the macOS error text containing profile_entries and profile_override. Issue #2078 is a user report, not a maintainer-confirmed defect or root-cause analysis. This site has no user database, no reproduction and no restore drill. If your error names a different table, column, OS or client, re-triage from your own log and the current official release notes.