After upgrade from v12, Shadowsocks port changes and is not editable; old port stays locked as "used by Shadowsocks"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
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
Summary
After upgrading the panel from v12 to the new version, the Shadowsocks port setting is broken:
- 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.
- 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
- On panel v12, set the Shadowsocks port to some value A.
- Upgrade to the latest panel version.
- Open the Shadowsocks port setting: it shows a different value B and is read-only.
- 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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hiddify/Hiddify-Manager
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hiddify/Hiddify-Manager#5689 ·
Maintainers usually reply within 1 day
-
enhancement from-telegram
Difficulty 4/5 3-5 days Newbie friendliness 40/100
hiddify/Hiddify-Manager#5691 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hiddify/Hiddify-Manager#5690 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 45/100
hiddify/Hiddify-Manager#5687 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
hiddify/Hiddify-Manager#5685 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in hiddify/Hiddify-Manager
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Install the skills as a Claude Code pluginPossibly taken @ruban-24 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FAIRmat-NFDI/pynxtools#874 ·
-
Eval: PublicationOpendata
Difficulty 2/5 1-3 hours Newbie friendliness 66/100