6 Commits

Include renames

Author	SHA1	Message	Date
Rogue	29de9761c8	V2.0.1: listen override fix, sing-box core fetch, probe settings page + fast report, spx removal, core mem env ... - 0: sing-box gen overrides fragment listen/port from the inbound row (empty listen -> "::"), Update/Add recompute the stored fragment; non-loopback E2E against the real core binary. - 1: agent fetches the sing-box core from the Gitea release when missing, self-checks it, and only then latches the switch. - 2: node list shows the sing-box core version (heartbeat field, persisted on the node row), xray version as fallback. - 3: public-page fallback returns 404 to anonymous visitors when the page is disabled. - 4: settings restart hint bar removed, dead i18n keys cleaned. - 5: two PUT calls missing JSON headers fixed (audit: only those two), batch probe-task creation endpoint + UI. - 6: cf-probe retirement card and coverage pipeline removed. - 7: generated vless links no longer carry spx (panel export + sub); parser still accepts spx; golden fixtures updated. - probe batch: dedicated probe settings tab (public-page settings, tasks, per-node meta), retention_days editable, per-node traffic calibration + stat-interface pinning, runtime metrics split into a lightweight fast report (default 3s, 1-60s adjustable). - 8: sing-box core processes start with GOMEMLIMIT=32MiB, GOGC=50. - 9: dead /getTwoFactorEnable docs entries removed (frontend call and contract entry already gone at base; verified by grep).	2026-10-23 07:53:11 +00:00
Muse	1bd63e6625	settings trim: remove dead settings, upstream remnants, JSON/Clash subscriptions ... Per SETTINGS-AUDIT (all three tiers approved 2026-10-23): Dead settings: - panelOutbound, ipLimitAllowlist (+ orphan parser job), outboundDownThreshold - tg fake events outbound.down/outbound.up/xray.crash (no publisher in lite) - phantom routing sub-tabs (Happ/Clash/Incy) and subJsonRules direct-rules tab (no backend keys); subHideSettings moved to the subscription info tab first Upstream remnants: - ldap* / smtp* model+schema keys, EmailNotifications orphan component - twoFactorEnable/twoFactorToken + login-page probe (no backend handler) - externalTrafficInform* Newly approved removals: - JSON subscription family (producer, routes, UA auto-detect, mux/finalmask/ observatory) and Clash subscription family (producer, routes, UA detect) - SubBalancer (table, service, controller, settings tab) - subThemeDir (subscription page falls back to the built-in template) - datepicker jalalian option (gregorian only; Persian picker removed) JSON/Clash endpoints now 404; link-format output pinned by regression tests. Guarded keys untouched: webListen/webPort/webBasePath/certs, tg* chain, expireDiff/trafficDiff/tgBotProxy, subHideSettings, pageSize/tgLang.	2026-10-22 19:21:07 +00:00
Muse	8e89960474	merge wiring: route agent address lookups through ResolveAgentAddresses (V1.0.1)	2026-10-23 00:34:33 +08:00
Muse	7d9a38490d	fix(sub): agent-hosted inbounds export the agent's telemetry address, not the 'agent' placeholder ... Agent nodes store the create form's placeholder in nodes.address ('agent', port 2053; NodeFormModal.buildPayload). The export fallback chain treated it as a real node address, so every host-less inbound on an agent node produced links like vless://...@agent:31324. SubService now loads agent_nodes bindings alongside nodes (latest last_seen per node, same rule as the node list) and resolves an agent-managed node's export address through the single convergence point agentNodeAddress(nodeID): telemetry IPv4, then IPv6, then "" so the chain continues to listen/public/request host and can never emit the placeholder. Host-bound inbounds and traditional nodes are untouched. GetInboundOptions applies the same substitution via agentAdvertisedAddresses so the frontend share/QR/WireGuard feed never sees the placeholder either.	2026-10-22 15:35:21 +00:00
Muse	8ca1a4647a	feat(sub): emit socks:// links for clients on socks/mixed inbounds ... GetLink had no socks-family case, so an attached client's subscription contained no link for the inbound at all, and getInboundsBySubId's protocol list omitted socks/mixed entirely, so such a subscription 404'd when the SK5 inbound was the client's only one. genSocksLink emits socks://user:pass@host:port with the same credential pair the core config carries — user is the client email, pass is the client password, both percent-encoded. The inbound's own fixed account is an operator credential and is never emitted.	2026-10-21 22:25:18 +00:00
Sanaei	f727d04f65	v3.7.0	2026-08-24 15:07:15 +02:00