After upgrade from v12, Shadowsocks port changes and is not editable; old port stays locked as "used by Shadowsocks"

Open
#5,688 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

The payload names no files, so start by finding where the Shadowsocks port is stored and migrated during the v12 upgrade, and where the Domains port-conflict check reads it. Reproduce with a v12 config holding port A, then confirm the migrated value and the error. Done means the migrated Shadowsocks port is editable, and port A can be assigned in Domains once Shadowsocks uses B.

Written by the indexing model from the issue text.

Description

bug

Summary

After upgrading the panel from v12 to the new version, the Shadowsocks port setting is broken:

  1. In panel v12 the Shadowsocks port was set to value A. After the update, the Shadowsocks port shows a different value B, and the field cannot be edited.
  2. Port A is still treated as reserved: when trying to use port A in the Domains section, the panel shows an error saying the port is already used by Shadowsocks, even though Shadowsocks no longer uses it (it now uses B). The old port stays locked from the previous version.

Steps to reproduce

  1. On panel v12, set the Shadowsocks port to some value A.
  2. Upgrade to the latest panel version.
  3. Open the Shadowsocks port setting: it shows a different value B and is read-only.
  4. In Domains, try to assign port A to a domain/entry.

Expected

  • The Shadowsocks port from v12 (A) is migrated as-is, or the port remains editable after the upgrade.
  • The port-conflict check uses the port Shadowsocks actually uses now, so port A becomes free once Shadowsocks moves to B.

Actual

  • Shadowsocks port changed to B during migration and is not editable.
  • Port A is rejected in Domains with a "used by Shadowsocks" error, although nothing uses it (stale value from the old version).
Dominant language
Python
Stars
9.5k
Forks
1.1k
Avg merge
1d 2h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hiddify/Hiddify-Manager

All issues in hiddify/Hiddify-Manager

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.