mirror of
https://github.com/MHSanaei/3x-ui.git
synced 2026-05-31 18:24:10 +00:00
85e2ded0e1
* feat(clients): add shadow tables for first-class client promotion
Introduces three new GORM-backed tables (clients, client_inbounds,
inbound_fallback_children) and a populate-only seeder that backfills
them from each inbound's existing settings.clients JSON. Duplicate
emails across inbounds auto-merge under one client row, with each
field conflict logged. Existing services are unchanged and continue
reading from settings.clients — this commit is groundwork only.
* feat(clients): make clients+client_inbounds the runtime source of truth
Adds ClientService.SyncInbound that reconciles the new tables from
each inbound's clients list whenever existing service paths mutate
settings.clients. Wires it into AddInbound, UpdateInbound,
AddInboundClient, UpdateInboundClient, DelInboundClient,
DelInboundClientByEmail, DelDepletedClients, autoRenewClients, and
the timestamp-backfill path in adjustTraffics, plus DetachInbound
on DelInbound.
GetXrayConfig now builds settings.clients from the new tables before
writing config.json, and getInboundsBySubId joins through them
instead of JSON_EACH on settings JSON. Live Xray config and
subscription endpoints are now driven by the relational view;
settings.clients JSON stays in step as a side effect of every write.
* feat(clients): add top-level Clients tab and CRUD API
Adds /panel/api/clients endpoints (list, get, add, update, del,
attach, detach) backed by ClientService methods that orchestrate
the per-inbound Add/Update/Del flows so a single client row is
created once and attached to many inbounds in one operation.
The frontend gains a dedicated Clients page (frontend/clients.html
+ src/pages/clients/) with an AntD table, multi-inbound attach
modal, and full CRUD. Axios interceptor learns to honour
Content-Type: application/json so the JSON endpoints work
alongside the legacy form-encoded ones.
The legacy per-inbound client modal stays untouched in this PR —
both flows now write to the same source of truth.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(inbounds): add Port-with-Fallback inbound type
Adds a new "portfallback" protocol that emits as a VLESS-TLS inbound
under the hood but is paired with a sidecar table of child inbounds.
Panel auto-builds settings.fallbacks at Xray-config-gen time from the
sidecar — each child's listen+port becomes the fallback dest, with
SNI/ALPN/path/xver match criteria pulled from the row. No more typing
loopback ports by hand or keeping settings.fallbacks in sync.
Backend: new FallbackService (Get/SetChildren, BuildFallbacksJSON);
two new routes (GET/POST /panel/api/inbounds/:id/fallbackChildren);
xray.GetXrayConfig injects fallbacks for PortFallback inbounds; the
inbound model emits protocol="vless" so Xray accepts the config.
Frontend: PORTFALLBACK joins the protocol dropdown; selecting it
shows the standard VLESS controls plus a Fallback Children table
(inbound picker + per-row SNI/ALPN/path/xver). Children are loaded
on edit and replaced atomically on save.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): add Reset Traffic, QR Code, Info actions + Online/Remaining columns
The Clients page table gains:
- Online column — green/grey tag driven by /panel/api/inbounds/onlines,
polled every 10s.
- Remaining column — bytes-remaining tag, coloured green/orange/red
against quota, purple infinity when unlimited.
- Action icons per row: QR, Info, Reset traffic, Edit, Delete.
ClientInfoModal shows the full client detail (uuid/password/auth,
traffic ↑/↓ + remaining + all-time, expiry absolute + relative,
attached inbounds chip list, online + last-online).
ClientQrModal fetches links for the client's subId via
/panel/api/inbounds/getSubLinks/:subId and renders each one through
the existing QrPanel component.
Reset Traffic confirms then calls the existing per-inbound endpoint
on the client's first attached inbound (the traffic row is keyed on
email globally, so any attached inbound resets the shared counter).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): expose Attached inbounds in edit mode
The multi-select was gated on add-only, so editing a client had no way
to change which inbounds it belonged to. The picker now shows in both
modes, and on submit the modal diffs the picked set against the
original attachedIds — additions go through the /attach endpoint,
removals through /detach, both after the field update lands so the
new attachments get the latest values.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): unbreak template parsing + stale i18n keys
- InboundFormModal: split the multi-line help string in the
PortFallback section onto one line — Vue's template parser was
bailing on Unterminated string constant because a single-quoted
literal spanned two lines inside a {{ }} interpolation.
- ClientInfoModal: t('disable') was missing at the root level, so
vue-i18n returned the key path literally. Use t('disabled') which
exists.
- Linter cleanup elsewhere: pages.client.* references renamed to
pages.clients.* to match the merged i18n block; whitespace
normalisation in a few unrelated Vue templates.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* 1
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(traffic): drop all-time traffic tracking
Removes the AllTime field from Inbound and ClientTraffic and migrates
existing DBs by dropping the all_time columns on startup. The counter
duplicated up+down without adding signal, and the per-event accumulator
ran on every traffic write.
Frontend: drop the All-time column from the inbound list and the
client-row table, the All-time row from the client info modal, and the
All-Time Total Usage tile from the inbounds summary card. The
allTimeTraffic/allTimeTrafficUsage i18n keys are removed across every
locale.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): mobile cards, multi-select, bulk add
Adds the same row-card layout the inbounds page uses on mobile: the
table is suppressed under the mobile breakpoint and each client renders
as a compact card with a status dot, email, Info button, Enable switch,
and overflow menu. All the per-client detail (traffic, remaining,
expiry, attached inbounds, flow, created/updated, URL, subscription)
opens through the existing info modal.
Multi-select with bulk delete wires AntD row-selection on desktop and
a per-card checkbox on mobile; a Delete (N) button appears in the
toolbar when anything is selected.
Bulk add reuses the five email-generation modes from the inbound bulk
modal but takes a multi-inbound picker so one bulk run can attach to
several inbounds at once. Submits client-by-client through the
existing /panel/api/clients/add endpoint.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(inbounds): remove legacy per-inbound client UI
Now that clients live as first-class rows attached to one or many
inbounds, the per-inbound client UI on the inbounds page is dead
weight — every client action either has a global equivalent on the
Clients page or makes no sense in a many-to-many world.
Deletes ClientFormModal, ClientBulkModal, CopyClientsModal, and
ClientRowTable from inbounds/. Strips the matching emits, refs,
handlers, and dropdown menu items from InboundList and InboundsPage,
and removes the dead mobile expand-chevron state and the desktop
expanded-row plumbing that drove the inline client table.
The InboundFormModal Clients tab still works in add-mode (one inline
client at inbound creation) — that flow goes through ClientService.
SyncInbound on save and remains useful.
Fixes a stray "</a-dropdown>" left over by an earlier toolbar edit
in ClientsPage that broke the template parser.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): add Delete depleted action
Mirrors the legacy delDepletedClients action that lived under the
inbounds page, but as a first-class /panel/api/clients/delDepleted
endpoint backed by ClientService. The new path goes through
ClientService.Delete for each depleted email, so the new clients +
client_inbounds + xray_client_traffic tables stay consistent.
Adds a danger-styled toolbar button on the Clients page (next to
Reset all client traffic) with a confirm dialog and a toast
reporting the deleted count.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(api): move every client-shaped endpoint off /inbounds onto /clients
After the multi-inbound client migration, client state belongs to the
client API surface, not the inbound one. Twelve routes that were
crammed under /panel/api/inbounds/* now live where they belong, under
/panel/api/clients/*.
Moved (route, handler, doc):
POST /clientIps/:email
POST /clearClientIps/:email
POST /onlines
POST /lastOnline
POST /updateClientTraffic/:email
POST /resetAllClientTraffics/:id
POST /delDepletedClients/:id
POST /:id/resetClientTraffic/:email
GET /getClientTraffics/:email
GET /getClientTrafficsById/:id
GET /getSubLinks/:subId
GET /getClientLinks/:id/:email
Their /clients/* counterparts are:
POST /clients/clientIps/:email
POST /clients/clearClientIps/:email
POST /clients/onlines
POST /clients/lastOnline
POST /clients/updateTraffic/:email
POST /clients/resetTraffic/:email (email-only, fans out)
GET /clients/traffic/:email
GET /clients/traffic/byId/:id
GET /clients/subLinks/:subId
GET /clients/links/:id/:email
per-inbound resetAllClientTraffics and delDepletedClients are dropped
entirely — the Clients page already exposes global Reset All Traffic
and Delete depleted actions, and per-inbound resets are meaningless
once a client can be attached to many inbounds.
ClientService.ResetTrafficByEmail is the new email-only reset path:
it looks up every inbound the client is attached to and pushes the
counter reset + Xray re-add through inboundService.ResetClientTraffic
for each one, so depleted users come back online instantly.
Frontend callers (ClientsPage, useClients, ClientQrModal,
ClientInfoModal, InboundInfoModal, InboundsPage, useInbounds) all
switched to the new paths. The Inbounds page drops its per-inbound
"Reset client traffic" and "Delete depleted clients" dropdown items —
users do those at the client level now. api-docs is rebuilt to match.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(service): switch tgbot + ldap callers to ClientService
Adds two thin helpers to ClientService (CreateOne, DetachByEmail) and
rewrites tgbot.SubmitAddClient and ldap_sync_job to call ClientService
directly. Removes the JSON-blob payloads (BuildJSONForProtocol output for
add, clientsToJSON/clientToJSON helpers) that callers previously fed to
InboundService.AddInboundClient/DelInboundClient.
ldap_sync_job.batchSetEnable now loops InboundService.SetClientEnableByEmail
per email instead of trying to coerce AddInboundClient into doing the
update — the old path would have failed duplicate-email validation for
existing clients anyway.
The legacy InboundService.AddInboundClient/UpdateInboundClient/
DelInboundClient methods stay in place; they are now only used internally
by ClientService Create/Update/Delete/Attach. Inlining + deleting them
follows in a separate commit.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(service): move all client mutation methods to ClientService
Moves the client mutation surface out of InboundService and into
ClientService. These methods all operate on a single client (identity
fields, traffic limits, expiry, ip limit, enable state, telegram tg id)
and didn't belong on the inbound aggregate.
Moved (12 methods): AddInboundClient, UpdateInboundClient, DelInboundClient,
DelInboundClientByEmail, checkEmailsExistForClients, SetClientTelegramUserID,
checkIsEnabledByEmail, ToggleClientEnableByEmail, SetClientEnableByEmail,
ResetClientIpLimitByEmail, ResetClientExpiryTimeByEmail,
ResetClientTrafficLimitByEmail.
Each method now takes an explicit *InboundService for the helpers that
legitimately stay on InboundService (GetInbound, GetClients, runtimeFor,
AddClientStat / UpdateClientStat / DelClientStat, DelClientIPs /
UpdateClientIPs, emailUsedByOtherInbounds, getAllEmailSubIDs,
GetClientInboundByEmail / GetClientInboundByTrafficID,
GetClientTrafficByEmail).
Stays on InboundService: ResetClientTrafficByEmail and
ResetClientTraffic(id, email) — these mutate xray_client_traffic rows,
not client identity, so they're inbound-side bookkeeping.
Callers updated: tgbot (6 calls), ldap_sync_job (1 call),
InboundService internal (writeBackClientSubID, CopyInboundClients,
AddInbound's email-uniqueness check), ClientService Create/Update/
Delete/Attach/Detach.
Also removes a dead resetAllClientTraffics controller handler whose
route was already gone after the previous /clients API migration.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(clients): finish migrating to ClientService + tidy IP routes
Two related cleanups in the new /clients surface:
1. Move ResetAllClientTraffics (bulk-reset of xray_client_traffic +
last_traffic_reset_time, with node-runtime propagation) from
InboundService to ClientService. PeriodicTrafficResetJob now holds
a clientService and calls
j.clientService.ResetAllClientTraffics(&j.inboundService, id).
The last client-mutation method on InboundService is gone.
2. Shorten redundantly-named routes/handlers under /panel/api/clients:
- /clientIps/:email -> /ips/:email (handler getIps)
- /clearClientIps/:email -> /clearIps/:email (handler clearIps)
The "client" prefix was redundant inside the clients namespace.
Frontend (InboundInfoModal) and api-docs updated to match.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(inbounds,clients): clean up inbound modal + enrich client modal
Inbound modal rework (InboundFormModal.vue + inbound.js):
- Drop the embedded Client subform in the Protocol tab. Multi-inbound
clients are managed exclusively from the Clients page now; a fresh
inbound is created with zero clients (settings constructors default
to []) and the user attaches clients afterwards.
- Hide the Protocol tab entirely when it has nothing to render
(VMESS, Trojan without fallbacks, Hysteria). Auto-switches active
tab to Basic when the tab disappears while focused.
- Move the Security section (Security selector + TLS block with certs
and ECH + Reality block) out of the Stream tab into its own
Security tab, sharing the canEnableStream gate.
Client modal additions (ClientFormModal.vue + ClientBulkAddModal.vue):
- Flow select (xtls-rprx-vision / -udp443) appears only when the
panel actually has a Vision-capable inbound (VLESS or PortFallback
on TCP with TLS or Reality). Hidden otherwise, and cleared when
it disappears.
- IP Limit input is disabled when the panel-level ipLimitEnable
setting is off, fetched into useClients alongside subSettings and
threaded through ClientsPage to both modals.
- Edit modal now shows an "IP Log" section listing IPs that have
connected with the client's credentials, with refresh and clear
buttons (calls the renamed /panel/api/clients/ips and /clearIps
endpoints).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(inbounds): drop manual Fallbacks UI from inbound modal
The PortFallback protocol type now covers the common
VLESS-master-plus-children case with auto-wired dests, so the manual
Fallbacks editor (showFallbacks block in the Protocol tab) is mostly
redundant. Removed:
- the v-if="showFallbacks" template block (SNI/ALPN/Path/dest/PROXY rows)
- the showFallbacks computed
- the addFallback / delFallback helpers
- the .fallbacks-header / .fallbacks-title styles
- the showFallbacks gate from hasProtocolTabContent (so Trojan-over-TCP
no longer shows an empty Protocol tab)
Power users who need a non-inbound fallback dest (nginx, static site)
can still author settings.fallbacks via the Advanced JSON tab.
* feat(clients,inbounds): move search/filter to Clients page + small fixes
Search/filter relocation:
- Remove the search/filter toolbar (search switch + filter radio +
protocol/node selects + the visibleInbounds projection +
inboundsFilterState localStorage + filter CSS + the SearchOutlined/
FilterOutlined/ObjectUtil/Inbound imports it required) from
InboundList. The filters were all client-oriented buckets bolted
onto the inbound row.
- Add a search/filter toolbar to ClientsPage with the same shape:
switch between deep-text search and bucket filter (active /
deactive / depleted / expiring / online) + protocol filter that
matches clients attached to at least one inbound with the chosen
protocol. State persists in clientsFilterState localStorage.
filteredClients drives both the desktop table and the mobile card
list, and select-all / allSelected / someSelected only span the
visible subset.
- useClients now also fetches expireDiff and trafficDiff from
/panel/setting/defaultSettings (used to detect the expiring
bucket); ClientsPage threads them into the client-bucket helper.
Loose fixes folded in:
- Add Client: email field is auto-filled with a random handle on
open, matching uuid/subId/password/auth.
- Inbound clone: parse and reuse the source settings JSON (with
clients reset to []) instead of building a fresh defaulted
Settings, so VLESS Encryption/Decryption and other non-client
fields survive the clone.
- en-US.json: add the ipLog string used by the edit-client modal.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): add Reverse tag field for VLESS-attached clients
Mirrors the Flow field's pattern: a Reverse tag input appears in the
Add/Edit Client modal whenever at least one selected inbound is VLESS
or PortFallback. The value rides over the wire as
client.reverse = { tag: '...' } so it lands directly in model.Client's
*ClientReverse field; an empty value omits the reverse key entirely.
On edit the field is hydrated from props.client.reverse?.tag, and the
showReverseTag watcher clears the field if the user drops the last
VLESS-like inbound from the selection.
* fix(xray): emit only protocol-relevant fields per client entry
The Xray config synthesizer was writing every identifier field (id,
password, flow, auth, security/method, reverse) on every client entry
regardless of the inbound's protocol. Xray ignores unknown fields, so
the config worked, but it diverged from the spec and leaked secrets
across protocols when one client was attached to multiple inbounds —
a VLESS inbound's generated config carried the same client's Trojan
password and Hysteria auth alongside its uuid.
Switch on inbound.Protocol when building each entry:
- VLESS / PortFallback: id, flow, reverse
- VMess: id, security
- Trojan: password, flow
- Shadowsocks: password, method
- Hysteria / Hysteria2: auth
email is emitted for every protocol.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): restore auto-disable kick under new schema
disableInvalidClients still resolved (inbound_tag, email) pairs via
JSON_EACH(inbounds.settings.clients), which is empty after migrating
to the clients + client_inbounds tables. Result: xrayApi.RemoveUser
never ran for depleted clients, clients.enable stayed true so the UI
showed them as active, and only xray_client_traffic.enable got flipped
- making "Restart Xray After Auto Disable" only half-work.
Resolve the targets via a JOIN through the new schema, flip clients.enable
so the Clients page reflects the state, and drop the legacy JSON
write-back plus the subId cascade workaround (email is unique now).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): live WebSocket updates + Ended status surfacing
ClientsPage now subscribes to traffic / client_stats / invalidate
WebSocket events instead of polling /onlines every 10s. Per-row
traffic counters refresh in place, online state stays current, and
list-level mutations elsewhere trigger a refresh.
The client roll-up summary moves from InboundsPage to ClientsPage
where it belongs, restructured into six labeled stat tiles
(Total / Online / Ended / Expiring / Disabled / Active) with email
popovers on the ones with issues.
Auto-disabled clients (traffic exhausted or expiry passed) now
classify as 'depleted' even though clients.enable=false, so they
show up under the Ended filter and render a red Ended tag instead
of looking indistinguishable from an operator-disabled row.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(nodes): per-node client roll-up and panel version
Added transient inboundCount / clientCount / onlineCount /
depletedCount fields to model.Node, populated by NodeService.GetAll
via aggregated queries (one join across inbounds + client_inbounds,
one over client_traffics intersected with the in-memory online
emails). The Nodes list renders these as colored chips on a new
"Clients" column so an operator can see at a glance how many users
each node carries and how many are currently online or depleted.
Also exposes the remote panel's version. The central panel adds
panelVersion to its /api/server/status payload (sourced from
config.GetVersion). Probe reads that field and persists it on the
node row, mirroring how xrayVersion already flows. NodesPage gets
a new column next to Xray Version, in both desktop and mobile
views, with English and Persian strings.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): stop node sync from resurrecting deleted clients
Several related issues around node-managed clients:
- Remote runtime: drop the per-inbound resetAllClientTraffics path
and point traffic/onlines/lastOnline fetches at the new
/panel/api/clients/* routes.
- Delete from master: always push the updated inbound to the node
even when the client was already disabled or depleted, so the
node actually loses the user instead of silently keeping it.
- setRemoteTraffic: mirror remote clients into the central tables
only on first discovery of a node inbound. Matched inbounds let
the master own the join table, so a stale snap can no longer
re-create a ClientRecord (and join row) for a client that was
just deleted on the master.
- ClientService.Delete: route through submitTrafficWrite so deletes
serialize with node traffic merges, and switch the final
ClientRecord delete to an explicit Where("id = ?") clause.
- setRemoteTraffic UNIQUE-constraint fix: use clause.OnConflict on
inserts and email-keyed UPDATEs for client_traffics, so mirroring
a snap doesn't trip the unique email index.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(clients): switch client API endpoints from id to email
All client-scoped routes now use the unique email as the path key
(get, update, del, attach, detach, links). Email is the stable,
protocol-independent identifier — UUIDs don't exist for trojan or
shadowsocks, and internal numeric ids leaked panel implementation
detail into the public API.
Removed the redundant /traffic/byId/:id endpoint (covered by
/traffic/:email) and collapsed /links/:id/:email into /links/:email,
which now returns links across every attached inbound for the client.
Frontend selection, bulk delete, and toggle state are now keyed by
email as well, dropping the id→email lookup workaround.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(server): move cached state and helpers into ServerService
ServerController had grown to hold its own status cache, version-list
TTL cache, history-bucket whitelist, and the loop that drove all three
— concerns that belong in the service layer. Pull them out:
- lastStatus + the @2s refresh become ServerService.RefreshStatus and
ServerService.LastStatus; the controller's cron now just orchestrates
the cross-service side effects (xrayMetrics sample, websocket broadcast).
- The 15-minute Xray-versions cache (with stale-on-error fallback) moves
into ServerService.GetXrayVersionsCached, collapsing the controller
handler to a single call.
- The freedom/blackhole outbound-tag walk used by /xraylogs becomes
ServerService.GetDefaultLogOutboundTags.
- The allowed-history-bucket whitelist moves to package-level
service.IsAllowedHistoryBucket, so both NodeController and
ServerController validate against the same list.
Net result: web/controller/server.go drops from 458 to 365 lines and
contains only HTTP wiring + presentation-y side effects.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* refactor(api): emit JSON-text columns as nested objects
Inbound, ClientRecord, and InboundClientIps store settings /
streamSettings / sniffing / reverse / ips as JSON-text in the DB. The
API was passing that text through verbatim, so every consumer had to
JSON.parse a string inside a string. Add MarshalJSON / UnmarshalJSON so
the wire format is a real nested object, while still accepting the
legacy escaped-string shape on write. Frontend dbinbound.js gets a
matching coerceInboundJsonField helper for the same dual-shape read
path, and inbound.js toJson stops emitting empty/placeholder fields
(externalProxy [], sniffing destOverride when disabled, etc.) so the
new normalised JSON stays terse. api-docs and the inbound-clone path
are updated to the new shape. Controller route lists are regrouped so
all GETs sit above POSTs.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): include inboundIds and traffic in /clients/list
ClientRecord got its own MarshalJSON in the previous commit, and
ClientWithAttachments embeds it to add inboundIds and traffic. Go
promotes the embedded MarshalJSON to the outer struct, so the encoder
was calling ClientRecord.MarshalJSON for the whole value and silently
dropping the extras. The frontend reads row.inboundIds / row.traffic
from /clients/list, so attached inbounds didn't render and newly added
clients looked like they hadn't saved. Add an explicit MarshalJSON on
ClientWithAttachments that splices the extras in.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): gate IP Log on ipLimitEnable + clean access-log dropdown
Legacy panel hid the IP Log section when access logging was off; the
Vue 3 migration left it gated on isEdit only, so the section showed
even when xray's access log was 'none' and nothing was being recorded.
Restore the ipLimitEnable gate on the edit modal's IP Log form-item.
While here, clean up the Xray Settings access-log dropdown: previously
two 'none' entries appeared (an empty value labelled with t('none') and
the literal 'none' from the options array). Drop the empty option for
access log (the literal 'none' covers it) and relabel the empty option
for error log / mask address to t('empty') so they're distinguishable.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(nodes): route per-client ops through node clients API + orphan sweep
Adds Runtime methods AddClient, UpdateUser, and DeleteUser so master
mutates clients on a node via /panel/api/clients/{add,update,del} rather
than pushing the whole inbound. The previous rt.UpdateInbound path made
the node DelInbound+AddInbound on every single-client change, briefly
cycling every other user on the same inbound.
DelInbound no longer filters by enable=true, so a disabled node inbound
actually gets removed from the node instead of being resurrected by the
next snap.
setRemoteTrafficLocked now sweeps any ClientRecord with zero
ClientInbound rows after SyncInbound rebuilds the attachments, which is
how a node-side delete propagates back to master instead of leaving a
detached ghost. ClientService.Delete tombstones the email first so a
snap arriving mid-delete can't re-create the record.
WebSocket broadcasts an "invalidate(clients)" message on every client
mutation so the Clients page refreshes without manual reload.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(balancers): allow fallback on all strategies + feed burstObservatory from random/roundRobin
Drops the random/roundRobin gate on the Fallback field in
BalancerFormModal so every strategy can pick a fallback outbound.
syncObservatories now feeds burstObservatory from leastLoad +
random + roundRobin balancers (was leastLoad only), matching how
leastPing feeds observatory.
Fix the JsonEditor "Unexpected end of JSON input" that appeared
when switching a balancer between leastPing and another strategy:
the obsView watcher was gated on showObsEditor (a boolean OR of
the two flags) and missed the case where one observatory
swapped for the other in the same tick. Watch the individual
flags instead so obsView flips to the surviving editor and the
getter stops pointing at a deleted key.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(inbounds): use sortedInbounds for mobile empty-state check
InboundList referenced an undefined visibleInbounds in the mobile
card list's empty-state guard, throwing "Cannot read properties of
undefined (reading 'length')" and breaking the entire mobile render.
* feat(clients): sortable table columns
Adds the same sortState / sortableCol / sortFns pattern InboundList
uses, wrapping filteredClients in sortedClients so sort composes with
the existing search/filter pipeline. Sortable: enable, email,
inboundIds (attachment count), traffic, remaining, expiryTime;
actions and online stay unsorted.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(shadowsocks): generate valid ss2022 keys and per-client method for legacy ciphers
The Add Client flow on shadowsocks inbounds was producing xray configs
that failed to start:
- 2022-blake3-* ciphers need a base64-encoded key of an exact byte
length per cipher. fillProtocolDefaults was assigning a uuid-style
string, which xray rejects as "bad key". Now the password is
generated (or replaced if invalid) via random.Base64Bytes(n) sized
to the chosen cipher.
- Legacy ciphers (aes-256-gcm, chacha20-*, xchacha20-*) require a
per-client method field in multi-user mode; model.Client has no
Method, so settings.clients was stored without one and xray failed
with "unsupported cipher method:". applyShadowsocksClientMethod
now injects the top-level method into each client on add/update,
and healShadowsocksClientMethods backfills it at xray-config-build
time so existing inbounds heal on the next start.
- xray/api.go ssCipherType switch was missing aes-256-gcm, which
fell through to ss2022 path.
- SSMethods dropdown now offers aes-256-gcm.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): preserve ClientRecord on inbound delete + filter Attached inbounds to multi-client protocols
Replace the global orphan sweep in setRemoteTrafficLocked with a
per-inbound diff cleanup: only delete a ClientRecord whose email
disappeared from a snap-tracked inbound (i.e. a node-side delete).
Inbounds that vanished entirely from the snap (e.g. admin deleted
the inbound on master) aren't iterated, so a client whose last
attachment came from that inbound is now left alone instead of
being deleted alongside the inbound.
ClientFormModal and ClientBulkAddModal now filter the Attached
inbounds dropdown to protocols that actually support multiple
clients: shadowsocks, vless, vmess, trojan, hysteria, hysteria2,
and portfallback (which routes through VLESS settings).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): make empty-state text readable on dark/ultra themes
The "No clients yet" empty state had a hardcoded black color
(rgba(0,0,0,0.45)) that vanished against the dark backgrounds.
Drop the inline color, let it inherit from the AntD theme, and
fade with opacity like the mobile card empty state already does.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(clients): client-first tgbot add flow, tgId field, lightweight inbound options
- tgbot: drop legacy per-protocol Add Client UI in favour of a client-first
multi-inbound flow. New BuildClientDraftMessage / getInboundsAttachPicker
let an admin pick one or more inbounds and submit a single client; per-
protocol secrets are now generated server-side via fillProtocolDefaults.
Drops awaiting_id/awaiting_password_tr/awaiting_password_sh state cases
and add_client_ch_default_id/pass_tr/pass_sh/flow callbacks. Adds a
setTGUser button + awaiting_tg_id state so the bot can set Client.TgID
during Add.
- clients UI: add Telegram user ID input to ClientFormModal (0 = none).
Hide IP Limit field entirely when ipLimitEnable is off — disabled fields
still take layout space, this collapses Auth(Hysteria) to full width.
- inbounds API: new GET /panel/api/inbounds/options that returns just
{id, remark, protocol, port, tlsFlowCapable}. Used by the clients page
pickers so the dropdown payload stays small on panels with thousands of
clients (drops settings JSON, clientStats, streamSettings). Server-side
TlsFlowCapable mirrors Inbound.canEnableTlsFlow so the modal no longer
needs to parse streamSettings client-side.
- clientInfoMsg now shows attached inbound remarks, and getInboundUsages
reports the attached client count per inbound.
- api-docs: document the new /options endpoint and add tgId / flow to the
clients add/update bodies.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(inbounds): keep Node column visible for node-attached inbounds
The Node column was bound to hasActiveNode, so disabling every node hid
the column even when inbounds were still attached to those nodes — the
admin lost the visual cue that those inbounds belonged to a node and
would come back when it was re-enabled. Combine hasActiveNode with a
new hasNodeAttachedInbound check (any dbInbound with nodeId != null) so
the column survives node-disable.
* fix(api-docs): accept functional-component icons in EndpointSection
AntD-Vue icons (SafetyCertificateOutlined, etc.) are functional
components, so the icon prop's type: Object validator was rejecting
them with a "Expected Object, got Function" warning at runtime.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* test: cover crypto, random, netsafe, sub helpers, xray equals, websocket hub, node service
Adds ~110 unit tests across previously untested packages. Focus on
pure-logic and concurrency surfaces where regressions would silently
affect users:
- util/crypto, util/random: password hashing round-trip, ss2022 key
generation, alphabet/length invariants.
- util/netsafe: IsBlockedIP edge cases, NormalizeHost validation,
SSRF guard with AllowPrivate context bypass.
- util/common, util/json_util: traffic formatter, Combine nil-skip,
RawMessage empty-as-null and copy-on-unmarshal.
- sub: splitLinkLines, searchKey/searchHost, kcp share fields,
finalmask normalization, buildVmessLink round-trip.
- xray: Config.Equals and InboundConfig.Equals field-by-field,
getRequiredUserString/getOptionalUserString type checks.
- web/websocket: hub registration, throttling, slow-client eviction,
nil-receiver safety, concurrent register/unregister.
- web/service: NodeService.normalize validation, normalizeBasePath,
HeartbeatPatch.ToUI mapping.
- web/job: atomicBool concurrent set/takeAndReset semantics.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* i18n(clients): replace English fallbacks with proper translation keys
Pulls every hard-coded English label/title in the Clients page and its
four modals through the i18n layer so localized panels stop leaking
English. New keys live under pages.clients (auth, hysteriaAuth, uuid,
flow, flowNone, reverseTag, reverseTagPlaceholder, telegramId,
telegramIdPlaceholder, created, updated, ipLimit) plus refresh at the
root and toasts.bulkDeletedMixed / bulkCreatedMixed for partial-failure
toasts. Also switches the add-client modal's primary button from "Add"
to "Create" for consistency with other create flows.
The bulk-add Random/Random+Prefix/... email-method options stay
hard-coded by request - they're identifier-shaped strings.
* i18n: backfill 99 missing keys across all 12 non-English locales
Brings every translation file up to parity with en-US.json so the
Clients page, the fallback-children inbound section, the new refresh
verb, the Nodes panel-version label and a handful of older holes stop
falling through to the English fallback. New strings span:
- pages.clients.* (labels, confirmations, toasts, emailMethods)
- pages.inbounds.portFallback.* (Reality fallback inbound section)
- pages.nodes.panelVersion, menu.clients, refresh
Technical identifiers (Auth, UUID, Flow, Reverse tag) are intentionally
left untranslated since they correspond to xray-core field names.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* i18n: drop stale pages.client block duplicated in every non-English locale
Every non-English locale carried a pages.client (singular) section with
30 entries that duplicated pages.clients (plural). The plural namespace
is what the Vue code actually consumes; the singular one was dead
weight from an older rename that never got cleaned up in the
non-English files. Removing it brings every locale to exactly 984
keys, matching en-US.json.
* chore: apply modernize analyzer fixes across codebase
Mechanical replacements suggested by golang.org/x/tools/.../modernize:
strings.Cut/CutPrefix/SplitSeq, slices.Contains, maps.Copy, min(),
range-over-int, new(expr), strings.Builder for hot += loops,
reflect.TypeFor[T](), sync.WaitGroup.Go(), drop legacy //+build lines.
* feat(database): add PostgreSQL as an optional backend alongside SQLite
Lets operators with large client counts or multi-node setups pick PostgreSQL
at install time without breaking the existing SQLite default. Backend is
selected at runtime via XUI_DB_TYPE/XUI_DB_DSN, a small dialect layer keeps
the five JSON_EXTRACT/JSON_EACH queries portable, and a new `x-ui migrate-db`
subcommand copies SQLite data into PostgreSQL in FK-aware order.
* fix(inbounds): gate node selector to multi-node-capable protocols
Hide the Deploy-To selector and clear nodeId when switching to a
protocol that can't run on a remote node. Also:
- subs: return 404 (not 400) when subId matches no inbounds, so VPN
clients distinguish "deleted/unknown" from a server error
- hysteria link gen: use the inbound's resolved address so node-managed
inbounds advertise the node host instead of the central panel
- shadowsocks: default network to 'tcp' (udp was causing issues for some
clients on first-create)
- vite dev proxy: rewrite migrated-route bypass against the live base
path instead of a hardcoded single-segment regex
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(clients): bulk add/delete correctness + perf, working pagination, delayed-start in form
Bulk add/delete were serial on the frontend (one toast per call, N round-trips)
and the backend race exposed by parallelizing them lost client attachments and
hit UNIQUE constraint failed on client_inbounds. The single add/edit modal also
had no Start-After-First-Use option, and the table never showed the delayed
duration.
Backend (web/service/client.go):
- Per-inbound mutex on Add/Update/Del InboundClient so concurrent writers on
the same inbound don't lose the read-modify-write of settings JSON.
- SyncInbound skips create+join when the email is tombstoned so a concurrent
maintenance pass (adjustTraffics, autoRenewClients, markClientsDisabledIn-
Settings) that did a stale RMW can't resurrect a just-deleted client with a
fresh id.
- compactOrphans sweeps settings.clients entries whose ClientRecord no longer
exists, applied in Add/DelInboundClient + DelInboundClientByEmail so each
user-initiated mutation self-heals the inbound's settings.
- DelInboundClient uses Pluck instead of First for the stats lookup so a
missing row doesn't abort the delete with a noisy ErrRecordNotFound log.
Frontend:
- HttpUtil.{get,post} accept a silent option that suppresses the auto-toast.
- ClientBulkAddModal fires creates in parallel + silent + one summary toast.
- useClients.removeMany runs deletes in parallel + silent and refreshes once;
ClientsPage bulk delete uses it and shows one aggregate toast.
- useClients.applyInvalidate debounces 200 ms so the burst of N WebSocket
invalidate events from the backend collapses into a single refresh.
- ClientsPage pagination is reactive (paginationState ref + tablePagination
computed); onTableChange persists page-size and page changes.
- ClientFormModal gains a Start-After-First-Use switch + Duration days input
alongside the existing Expiry Date picker; on edit-mode open a negative
expiryTime is decoded back to delayed mode + days; on submit the payload
sends -86400000 * days or the absolute timestamp.
- ClientsPage table shows the delayed-start duration (blue tag Nd, tooltip
Start After First Use: Nd) instead of infinity.
- Telegram ID field in the form is hidden when /panel/setting/defaultSettings
reports tgBotEnable=false; Comment then fills the row.
- Form row 3 collapses UUID (span 12) + Total GB (span 8) + Limit IP (span 4)
when ipLimitEnable is on, else UUID + Total GB at 12/12.
- useInbounds.rollupClients counts only clients with a matching clientStats
row, so orphans in settings.clients no longer inflate the inbound's count.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(windows): clean shutdown, working panel restart, harden kernel32 load
Three Windows-specific issues addressed:
1. Orphaned xray-windows-amd64 after VS Code debugger stop. Delve's
"Stop" sends TerminateProcess to the Go binary, which is uncatchable
— our signal handlers never run, so xrayService.StopXray() is skipped
and xray is left dangling. Spawn xray as a child of a Job Object with
JOB_OBJECT_LIMIT_KILL_ON_JOB_CLOSE so the OS kills xray when our
handle to the job is closed (which happens even on TerminateProcess).
Also trap os.Interrupt in main so Ctrl+C in the terminal runs the
graceful path.
2. /panel/setting/restartPanel logged "failed to send SIGHUP signal: not
supported by windows" because Windows can't deliver arbitrary signals.
Add a restart hook in web/global; main registers it to push SIGHUP
into its own signal channel, and RestartPanel calls the hook before
falling back to the (Unix-only) signal path. Same restart-loop code
runs in both cases.
3. util/sys/sys_windows.go now uses windows.NewLazySystemDLL so the
kernel32.dll resolve is pinned to %SystemRoot%\System32 (prevents
DLL hijacking by a planted DLL next to the binary). Local filetime
type replaced with windows.Filetime, and the unreliable
syscall.GetLastError() fallback replaced with a type assertion on the
errno captured at call time.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(sys): correct CPU/connection accounting on linux + darwin
util/sys/sys_linux.go:
- GetTCPCount/GetUDPCount were counting the column header row in
/proc/net/{tcp,udp}[6] as a connection, inflating the reported total
by 1 per non-empty file (so the panel status line always showed 2
more connections than actually existed). Replace getLinesNum +
safeGetLinesNum with a single bufio.Scanner-based countConnections
that skips the header.
- CPUPercentRaw now opens HostProc("stat") instead of a hardcoded
/proc/stat so HOST_PROC overrides apply, matching the connection
counters in the same file.
- Simplify CPU field unpacking: pad nums to 8 once instead of guarding
every assignment with a len check.
util/sys/sys_darwin.go:
- Fix swapped idle/intr indices on kern.cp_time. BSD CPUSTATES order
is user, nice, sys, intr, idle (CP_INTR=3, CP_IDLE=4) — gopsutil's
cpu_darwin_nocgo.go reads the same layout. The previous code used
out[3] as idle and out[4] as intr, so busy = total - dIdle was
actually subtracting interrupt time, making the panel report CPU
usage close to 100% on macOS regardless of actual load.
- Collapse the per-field delta math into a single loop.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(xray): rotate crash reports into log folder, prevent overwrites
writeCrashReport had two flaws: it wrote to the bin folder (alongside the
xray binary) which conflates artifacts, and the second-precision timestamp
meant a tight restart-loop crash burst overwrote prior reports. Write to
the log folder with nanosecond precision and keep the last 10 reports.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* revert(inbounds): drop unreleased portfallback protocol
The Port-with-Fallback inbound (commit 62fd9f9d) was confusing as a
standalone protocol — fallbacks belong on a regular VLESS/Trojan TCP-TLS
inbound, the way Xray models them natively. Rip out the entire feature
cleanly (no migration needed since it was never released): protocol
constant, fallback children DB table, FallbackService, 2 API endpoints,
all UI rows, related translations and api-docs. A native fallback flow
attached to VLESS/Trojan TCP-TLS/Reality will land in a follow-up commit.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* feat(inbounds): native fallbacks on VLESS/Trojan TCP-TLS, with working child links
A VLESS or Trojan inbound on TCP with TLS or Reality can now act as a
fallback master: pick existing inbounds as children and the panel auto-
fills the SNI / ALPN / path / xver routing fields from each child's
transport, auto-builds settings.fallbacks at config-gen time, and
rewrites the child's client-share link so it advertises the master's
reachable endpoint and TLS state instead of the child's loopback listen.
Layout matches the Xray All-in-One Nginx example: master at :443 with
clients + TLS, each child on 127.0.0.1 with its own transport+clients.
Order matters (Xray walks fallbacks top-to-bottom) — reorder via the
per-row up/down arrows. Path / SNI / ALPN are exposed under a per-row
Edit toggle for the rare cases where the auto-derivation needs
overriding; otherwise just pick a child and you're done.
Backend: new InboundFallback table + FallbackService (GetByMaster /
SetByMaster / GetParentForChild / BuildFallbacksJSON); two routes
(GET / POST /panel/api/inbounds/:id/fallbacks); xray.GetXrayConfig
injects settings.fallbacks for any VLESS/Trojan TCP-TLS/Reality
inbound; GetInbounds annotates each child with FallbackParent so the
frontend can rewrite links without an extra round-trip.
Link projection covers every emission path — clients-page QR/links,
per-inbound Get URL, raw subscription, sub-JSON, sub-Clash, and the
inbounds-page link/info/QR — via a shared projectThroughFallbackMaster
on the backend and a shared projectChildThroughMaster on the frontend
that both handle the panel-tracked relationship and the legacy
unix-socket (@vless-ws) convention.
Strings translated into all 12 non-English locales.
* docs: rewrite CONTRIBUTING with full local-dev setup
The prior three-line CONTRIBUTING left newcomers guessing at every
non-trivial step: which Go / Node versions, where xray comes from, why
the panel goes blank when XUI_DEBUG=true is flipped on, how the Vue
multi-page setup is wired, what to do on Windows when go build trips
on the CGo SQLite driver.
Now covers prerequisites, MinGW-w64 install on Windows (niXman builds
or MSYS2), one-shot first-time setup, two frontend dev workflows with
the XUI_DEBUG asset-cache gotcha called out, the architecture and
conventions of the Vue side, a project-layout map, useful env vars,
and the PR checklist.
---------
1092 lines
No EOL
51 KiB
JSON
1092 lines
No EOL
51 KiB
JSON
{
|
||
"username": "用户名",
|
||
"password": "密码",
|
||
"login": "登录",
|
||
"confirm": "确定",
|
||
"cancel": "取消",
|
||
"close": "关闭",
|
||
"save": "保存",
|
||
"logout": "登出",
|
||
"create": "创建",
|
||
"update": "更新",
|
||
"copy": "复制",
|
||
"copied": "已复制",
|
||
"download": "下载",
|
||
"remark": "备注",
|
||
"enable": "启用",
|
||
"protocol": "协议",
|
||
"search": "搜索",
|
||
"filter": "筛选",
|
||
"loading": "加载中...",
|
||
"refresh": "刷新",
|
||
"clear": "清除",
|
||
"second": "秒",
|
||
"minute": "分钟",
|
||
"hour": "小时",
|
||
"day": "天",
|
||
"check": "查看",
|
||
"indefinite": "无限期",
|
||
"unlimited": "无限制",
|
||
"none": "无",
|
||
"qrCode": "二维码",
|
||
"info": "更多信息",
|
||
"edit": "编辑",
|
||
"delete": "删除",
|
||
"reset": "重置",
|
||
"noData": "无数据。",
|
||
"copySuccess": "复制成功",
|
||
"sure": "确定",
|
||
"encryption": "加密",
|
||
"useIPv4ForHost": "使用 IPv4 连接主机",
|
||
"transmission": "传输",
|
||
"host": "主机",
|
||
"path": "路径",
|
||
"camouflage": "伪装",
|
||
"status": "状态",
|
||
"enabled": "开启",
|
||
"disabled": "关闭",
|
||
"depleted": "耗尽",
|
||
"depletingSoon": "即将耗尽",
|
||
"offline": "离线",
|
||
"online": "在线",
|
||
"domainName": "域名",
|
||
"monitor": "监听",
|
||
"certificate": "数字证书",
|
||
"fail": "失败",
|
||
"comment": "评论",
|
||
"success": "成功",
|
||
"lastOnline": "上次在线",
|
||
"getVersion": "获取版本",
|
||
"install": "安装",
|
||
"clients": "客户端",
|
||
"usage": "使用情况",
|
||
"twoFactorCode": "代码",
|
||
"remained": "剩余",
|
||
"security": "安全",
|
||
"secAlertTitle": "安全警报",
|
||
"secAlertSsl": "此连接不安全。在激活 TLS 进行数据保护之前，请勿输入敏感信息。",
|
||
"secAlertConf": "某些设置易受攻击。建议加强安全协议以防止潜在漏洞。",
|
||
"secAlertSSL": "面板缺少安全连接。请安装 TLS 证书以保护数据安全。",
|
||
"secAlertPanelPort": "面板默认端口存在安全风险。请配置随机端口或特定端口。",
|
||
"secAlertPanelURI": "面板默认 URI 路径不安全。请配置复杂的 URI 路径。",
|
||
"secAlertSubURI": "订阅默认 URI 路径不安全。请配置复杂的 URI 路径。",
|
||
"secAlertSubJsonURI": "订阅 JSON 默认 URI 路径不安全。请配置复杂的 URI 路径。",
|
||
"emptyDnsDesc": "未添加DNS服务器。",
|
||
"emptyFakeDnsDesc": "未添加Fake DNS服务器。",
|
||
"emptyBalancersDesc": "未添加负载均衡器。",
|
||
"emptyReverseDesc": "未添加反向代理。",
|
||
"somethingWentWrong": "出了点问题",
|
||
"subscription": {
|
||
"title": "订阅信息",
|
||
"subId": "订阅 ID",
|
||
"status": "状态",
|
||
"downloaded": "已下载",
|
||
"uploaded": "已上传",
|
||
"expiry": "到期",
|
||
"totalQuota": "总配额",
|
||
"individualLinks": "单独链接",
|
||
"active": "启用",
|
||
"inactive": "停用",
|
||
"unlimited": "无限制",
|
||
"noExpiry": "无到期"
|
||
},
|
||
"menu": {
|
||
"theme": "主题",
|
||
"dark": "暗色",
|
||
"ultraDark": "超暗色",
|
||
"dashboard": "系统状态",
|
||
"inbounds": "入站列表",
|
||
"clients": "客户端",
|
||
"nodes": "节点",
|
||
"settings": "面板设置",
|
||
"xray": "Xray 设置",
|
||
"apiDocs": "API 文档",
|
||
"logout": "退出登录",
|
||
"link": "管理"
|
||
},
|
||
"pages": {
|
||
"login": {
|
||
"hello": "你好",
|
||
"title": "欢迎",
|
||
"loginAgain": "登录时效已过，请重新登录",
|
||
"toasts": {
|
||
"invalidFormData": "数据格式错误",
|
||
"emptyUsername": "请输入用户名",
|
||
"emptyPassword": "请输入密码",
|
||
"wrongUsernameOrPassword": "用户名、密码或双重验证码无效。",
|
||
"successLogin": "您已成功登录您的账户。"
|
||
}
|
||
},
|
||
"index": {
|
||
"title": "系统状态",
|
||
"cpu": "CPU",
|
||
"logicalProcessors": "逻辑处理器",
|
||
"frequency": "频率",
|
||
"swap": "交换分区",
|
||
"storage": "存储",
|
||
"memory": "内存",
|
||
"threads": "线程",
|
||
"xrayStatus": "Xray",
|
||
"stopXray": "停止",
|
||
"restartXray": "重启",
|
||
"xraySwitch": "版本",
|
||
"xrayUpdates": "Xray 更新",
|
||
"xraySwitchClick": "选择你要切换到的版本",
|
||
"xraySwitchClickDesk": "请谨慎选择，因为较旧版本可能与当前配置不兼容",
|
||
"updatePanel": "更新面板",
|
||
"panelUpdateDesc": "这将把 3X-UI 更新到最新版本并重启面板服务。",
|
||
"currentPanelVersion": "当前面板版本",
|
||
"latestPanelVersion": "最新面板版本",
|
||
"panelUpToDate": "面板已是最新",
|
||
"upToDate": "已是最新",
|
||
"xrayStatusUnknown": "未知",
|
||
"xrayStatusRunning": "运行中",
|
||
"xrayStatusStop": "停止",
|
||
"xrayStatusError": "错误",
|
||
"xrayErrorPopoverTitle": "运行Xray时发生错误",
|
||
"operationHours": "系统正常运行时间",
|
||
"systemHistoryTitle": "系统历史",
|
||
"charts": "图表",
|
||
"xrayMetricsTitle": "Xray 指标",
|
||
"xrayMetricsDisabled": "未配置 Xray 指标端点",
|
||
"xrayMetricsHint": "在 xray 配置中添加顶级 metrics 块,tag 为 metrics_out,listen 为 127.0.0.1:11111,然后重启 xray。",
|
||
"xrayObservatoryEmpty": "暂无 Observatory 数据",
|
||
"xrayObservatoryHint": "在 xray 配置中添加 observatory 块,列出要探测的出站 tag,然后重启 xray。",
|
||
"xrayObservatoryTagPlaceholder": "选择出站",
|
||
"xrayObservatoryAlive": "在线",
|
||
"xrayObservatoryDead": "离线",
|
||
"xrayObservatoryLastSeen": "最后在线",
|
||
"xrayObservatoryLastTry": "最后尝试",
|
||
"trendLast2Min": "最近 2 分钟",
|
||
"systemLoad": "系统负载",
|
||
"systemLoadDesc": "过去 1、5 和 15 分钟的系统平均负载",
|
||
"connectionCount": "连接数",
|
||
"ipAddresses": "IP地址",
|
||
"toggleIpVisibility": "切换IP可见性",
|
||
"overallSpeed": "整体速度",
|
||
"upload": "上传",
|
||
"download": "下载",
|
||
"totalData": "总数据",
|
||
"sent": "已发送",
|
||
"received": "已接收",
|
||
"documentation": "文档",
|
||
"xraySwitchVersionDialog": "您确定要更改Xray版本吗？",
|
||
"xraySwitchVersionDialogDesc": "这将把Xray版本更改为#version#。",
|
||
"xraySwitchVersionPopover": "Xray 更新成功",
|
||
"panelUpdateDialog": "您确定要更新面板吗？",
|
||
"panelUpdateDialogDesc": "这将把 3X-UI 更新到 #version# 并重启面板服务。",
|
||
"panelUpdateCheckPopover": "面板更新检查失败",
|
||
"panelUpdateStartedPopover": "已开始更新面板",
|
||
"geofileUpdateDialog": "您确定要更新地理文件吗？",
|
||
"geofileUpdateDialogDesc": "这将更新 #filename# 文件。",
|
||
"geofilesUpdateDialogDesc": "这将更新所有文件。",
|
||
"geofilesUpdateAll": "全部更新",
|
||
"geofileUpdatePopover": "地理文件更新成功",
|
||
"customGeoTitle": "自定义 GeoSite / GeoIP",
|
||
"customGeoAdd": "添加",
|
||
"customGeoType": "类型",
|
||
"customGeoAlias": "别名",
|
||
"customGeoUrl": "URL",
|
||
"customGeoEnabled": "启用",
|
||
"customGeoLastUpdated": "上次更新",
|
||
"customGeoExtColumn": "路由 (ext:…)",
|
||
"customGeoToastUpdateAll": "所有自定义来源已更新",
|
||
"customGeoActions": "操作",
|
||
"customGeoEdit": "编辑",
|
||
"customGeoDelete": "删除",
|
||
"customGeoDownload": "立即更新",
|
||
"customGeoModalAdd": "添加自定义 geo",
|
||
"customGeoModalEdit": "编辑自定义 geo",
|
||
"customGeoModalSave": "保存",
|
||
"customGeoDeleteConfirm": "删除此自定义 geo 源？",
|
||
"customGeoRoutingHint": "在路由规则中将值列写为 ext:文件.dat:标签（替换标签）。",
|
||
"customGeoInvalidId": "无效的资源 ID",
|
||
"customGeoAliasesError": "加载自定义 geo 别名失败",
|
||
"customGeoValidationAlias": "别名只能包含小写字母、数字、- 和 _",
|
||
"customGeoValidationUrl": "URL 必须以 http:// 或 https:// 开头",
|
||
"customGeoAliasPlaceholder": "a-z 0-9 _ -",
|
||
"customGeoAliasLabelSuffix": "（自定义）",
|
||
"customGeoToastList": "自定义 geo 列表",
|
||
"customGeoToastAdd": "添加自定义 geo",
|
||
"customGeoToastUpdate": "更新自定义 geo",
|
||
"customGeoToastDelete": "自定义 geofile「{{ .fileName }}」已删除",
|
||
"customGeoToastDownload": "geofile「{{ .fileName }}」已更新",
|
||
"customGeoErrInvalidType": "类型必须是 geosite 或 geoip",
|
||
"customGeoErrAliasRequired": "请填写别名",
|
||
"customGeoErrAliasPattern": "别名包含不允许的字符",
|
||
"customGeoErrAliasReserved": "该别名已保留",
|
||
"customGeoErrUrlRequired": "请填写 URL",
|
||
"customGeoErrInvalidUrl": "URL 无效",
|
||
"customGeoErrUrlScheme": "URL 必须使用 http 或 https",
|
||
"customGeoErrUrlHost": "URL 主机无效",
|
||
"customGeoErrDuplicateAlias": "此类型下已使用该别名",
|
||
"customGeoErrNotFound": "未找到自定义 geo 源",
|
||
"customGeoErrDownload": "下载失败",
|
||
"customGeoErrUpdateAllIncomplete": "有一个或多个自定义 geo 源更新失败",
|
||
"customGeoEmpty": "暂无自定义 geo 源 — 点击「添加」以创建",
|
||
"dontRefresh": "安装中，请勿刷新此页面",
|
||
"logs": "日志",
|
||
"config": "配置",
|
||
"backup": "备份",
|
||
"backupTitle": "备份和恢复",
|
||
"exportDatabase": "备份",
|
||
"exportDatabaseDesc": "点击下载包含当前数据库备份的 .db 文件到您的设备。",
|
||
"importDatabase": "恢复",
|
||
"importDatabaseDesc": "点击选择并上传设备中的 .db 文件以从备份恢复数据库。",
|
||
"importDatabaseSuccess": "数据库导入成功",
|
||
"importDatabaseError": "导入数据库时出错",
|
||
"readDatabaseError": "读取数据库时出错",
|
||
"getDatabaseError": "检索数据库时出错",
|
||
"getConfigError": "检索配置文件时出错"
|
||
},
|
||
"inbounds": {
|
||
"title": "入站列表",
|
||
"totalDownUp": "总上传 / 下载",
|
||
"totalUsage": "总用量",
|
||
"inboundCount": "入站数量",
|
||
"operate": "菜单",
|
||
"enable": "启用",
|
||
"remark": "备注",
|
||
"node": "节点",
|
||
"deployTo": "部署到",
|
||
"localPanel": "本地面板",
|
||
"fallbacks": {
|
||
"title": "回落",
|
||
"help": "当此入站的连接未匹配任何客户端时，将其路由到另一个入站。在下方选择一个子入站，路由字段（SNI / ALPN / Path / xver）会从子入站的传输方式中自动填充——大多数场景无需再调整。每个子入站应监听 127.0.0.1，security=none。",
|
||
"empty": "暂无回落",
|
||
"add": "添加回落",
|
||
"pickInbound": "选择一个入站",
|
||
"matchAny": "任意",
|
||
"rederive": "从子入站重新填充",
|
||
"rederived": "已从子入站重新填充",
|
||
"editAdvanced": "编辑路由字段",
|
||
"hideAdvanced": "隐藏高级",
|
||
"quickAddAll": "一键添加所有可用入站",
|
||
"quickAdded": "已添加 {n} 条回落",
|
||
"quickAddedNone": "没有可添加的新入站",
|
||
"routesWhen": "当满足条件时路由",
|
||
"defaultCatchAll": "默认 — 兜底匹配其他所有"
|
||
},
|
||
"protocol": "协议",
|
||
"port": "端口",
|
||
"portMap": "端口映射",
|
||
"traffic": "流量",
|
||
"details": "详细信息",
|
||
"transportConfig": "传输配置",
|
||
"expireDate": "到期时间",
|
||
"createdAt": "创建时间",
|
||
"updatedAt": "更新时间",
|
||
"resetTraffic": "重置流量",
|
||
"addInbound": "添加入站",
|
||
"generalActions": "通用操作",
|
||
"modifyInbound": "修改入站",
|
||
"deleteInbound": "删除入站",
|
||
"deleteInboundContent": "确定要删除入站吗？",
|
||
"deleteClient": "删除客户端",
|
||
"deleteClientContent": "确定要删除客户端吗？",
|
||
"resetTrafficContent": "确定要重置流量吗？",
|
||
"copyLink": "复制链接",
|
||
"address": "地址",
|
||
"network": "网络",
|
||
"destinationPort": "目标端口",
|
||
"targetAddress": "目标地址",
|
||
"monitorDesc": "留空表示监听所有 IP",
|
||
"meansNoLimit": "= 无限制（单位：GB)",
|
||
"totalFlow": "总流量",
|
||
"leaveBlankToNeverExpire": "留空表示永不过期",
|
||
"noRecommendKeepDefault": "建议保留默认值",
|
||
"certificatePath": "文件路径",
|
||
"certificateContent": "文件内容",
|
||
"publicKey": "公钥",
|
||
"privatekey": "私钥",
|
||
"clickOnQRcode": "点击二维码复制",
|
||
"client": "客户",
|
||
"export": "导出链接",
|
||
"clone": "克隆",
|
||
"cloneInbound": "克隆",
|
||
"cloneInboundContent": "此入站规则除端口（Port）、监听 IP（Listening IP）和客户端（Clients）以外的所有配置都将应用于克隆",
|
||
"cloneInboundOk": "创建克隆",
|
||
"resetAllTraffic": "重置所有入站流量",
|
||
"resetAllTrafficTitle": "重置所有入站流量",
|
||
"resetAllTrafficContent": "确定要重置所有入站流量吗？",
|
||
"resetInboundClientTraffics": "重置客户端流量",
|
||
"resetInboundClientTrafficTitle": "重置所有客户端流量",
|
||
"resetInboundClientTrafficContent": "确定要重置此入站客户端的所有流量吗？",
|
||
"resetAllClientTraffics": "重置所有客户端流量",
|
||
"resetAllClientTrafficTitle": "重置所有客户端流量",
|
||
"resetAllClientTrafficContent": "确定要重置所有客户端的所有流量吗？",
|
||
"delDepletedClients": "删除流量耗尽的客户端",
|
||
"delDepletedClientsTitle": "删除流量耗尽的客户端",
|
||
"delDepletedClientsContent": "确定要删除所有流量耗尽的客户端吗？",
|
||
"email": "电子邮件",
|
||
"emailDesc": "电子邮件必须完全唯一",
|
||
"IPLimit": "IP 限制",
|
||
"IPLimitDesc": "如果数量超过设置值，则禁用入站流量。（0 = 禁用）",
|
||
"IPLimitlog": "IP 日志",
|
||
"IPLimitlogDesc": "IP 历史日志（要启用被禁用的入站流量，请清除日志）",
|
||
"IPLimitlogclear": "清除日志",
|
||
"setDefaultCert": "从面板设置证书",
|
||
"streamTab": "流",
|
||
"securityTab": "安全",
|
||
"sniffingTab": "嗅探",
|
||
"sniffingMetadataOnly": "仅元数据",
|
||
"sniffingRouteOnly": "仅路由",
|
||
"sniffingIpsExcluded": "排除的 IP",
|
||
"sniffingDomainsExcluded": "排除的域名",
|
||
"decryption": "解密",
|
||
"encryption": "加密",
|
||
"vlessAuthX25519": "X25519 认证",
|
||
"vlessAuthMlkem768": "ML-KEM-768 认证",
|
||
"vlessAuthCustom": "自定义",
|
||
"vlessAuthSelected": "已选择：{auth}",
|
||
"advanced": {
|
||
"title": "入站 JSON 部分",
|
||
"subtitle": "完整入站 JSON 以及针对 settings、sniffing 和 streamSettings 的专用编辑器。",
|
||
"all": "全部",
|
||
"allHelp": "在单个编辑器中编辑包含所有字段的完整入站对象。",
|
||
"settings": "设置",
|
||
"settingsHelp": "Xray settings 块包装：",
|
||
"sniffing": "嗅探",
|
||
"sniffingHelp": "Xray sniffing 块包装：",
|
||
"stream": "流",
|
||
"streamHelp": "Xray stream 块包装：",
|
||
"jsonErrorPrefix": "高级 JSON"
|
||
},
|
||
"telegramDesc": "请提供Telegram聊天ID。（在机器人中使用'/id'命令）或（{'@'}userinfobot",
|
||
"subscriptionDesc": "要找到你的订阅 URL，请导航到“详细信息”。此外，你可以为多个客户端使用相同的名称。",
|
||
"info": "信息",
|
||
"same": "相同",
|
||
"inboundData": "入站数据",
|
||
"exportInbound": "导出入站规则",
|
||
"import": "导入",
|
||
"importInbound": "导入入站规则",
|
||
"periodicTrafficResetTitle": "流量重置",
|
||
"periodicTrafficResetDesc": "按指定间隔自动重置流量计数器",
|
||
"lastReset": "上次重置",
|
||
"periodicTrafficReset": {
|
||
"never": "从不",
|
||
"daily": "每日",
|
||
"weekly": "每周",
|
||
"monthly": "每月",
|
||
"hourly": "每小时"
|
||
},
|
||
"toasts": {
|
||
"obtain": "获取",
|
||
"updateSuccess": "更新成功",
|
||
"logCleanSuccess": "日志已清除",
|
||
"inboundsUpdateSuccess": "入站连接已成功更新",
|
||
"inboundUpdateSuccess": "入站连接已成功更新",
|
||
"inboundCreateSuccess": "入站连接已成功创建",
|
||
"inboundDeleteSuccess": "入站连接已成功删除",
|
||
"inboundClientAddSuccess": "已添加入站客户端",
|
||
"inboundClientDeleteSuccess": "入站客户端已删除",
|
||
"inboundClientUpdateSuccess": "入站客户端已更新",
|
||
"delDepletedClientsSuccess": "所有耗尽客户端已删除",
|
||
"resetAllClientTrafficSuccess": "客户端所有流量已重置",
|
||
"resetAllTrafficSuccess": "所有流量已重置",
|
||
"resetInboundClientTrafficSuccess": "流量已重置",
|
||
"resetInboundTrafficSuccess": "入站流量已重置",
|
||
"trafficGetError": "获取流量数据时出错",
|
||
"getNewX25519CertError": "获取X25519证书时出错。",
|
||
"getNewmldsa65Error": "获取mldsa65证书时出错。",
|
||
"getNewVlessEncError": "获取VlessEnc证书时出错。"
|
||
},
|
||
"stream": {
|
||
"general": {
|
||
"request": "请求",
|
||
"response": "响应",
|
||
"name": "名称",
|
||
"value": "值"
|
||
},
|
||
"tcp": {
|
||
"version": "版本",
|
||
"method": "方法",
|
||
"path": "路径",
|
||
"status": "状态",
|
||
"statusDescription": "状态说明",
|
||
"requestHeader": "请求头",
|
||
"responseHeader": "响应头"
|
||
}
|
||
}
|
||
},
|
||
"clients": {
|
||
"add": "添加客户端",
|
||
"edit": "编辑客户端",
|
||
"submitAdd": "添加客户端",
|
||
"submitEdit": "保存更改",
|
||
"clientCount": "客户端数量",
|
||
"bulk": "批量添加",
|
||
"copyFromInbound": "从入站复制客户端",
|
||
"copyToInbound": "复制客户端到",
|
||
"copySelected": "复制所选",
|
||
"copySource": "来源",
|
||
"copyEmailPreview": "生成的邮箱预览",
|
||
"copySelectSourceFirst": "请先选择一个来源入站。",
|
||
"copyResult": "复制结果",
|
||
"copyResultSuccess": "复制成功",
|
||
"copyResultNone": "没有内容可复制：未选中客户端或来源为空",
|
||
"copyResultErrors": "复制错误",
|
||
"copyFlowLabel": "新客户端的 Flow (VLESS)",
|
||
"copyFlowHint": "应用于所有被复制的客户端。留空则跳过。",
|
||
"selectAll": "全选",
|
||
"clearAll": "全部清除",
|
||
"method": "方式",
|
||
"first": "首个",
|
||
"last": "末位",
|
||
"ipLog": "IP 日志",
|
||
"prefix": "前缀",
|
||
"postfix": "后缀",
|
||
"delayedStart": "首次使用后开始",
|
||
"expireDays": "时长",
|
||
"days": "天",
|
||
"renew": "自动续期",
|
||
"renewDesc": "到期后自动续期。(0 = 禁用) (单位: 天)",
|
||
"title": "客户端",
|
||
"actions": "操作",
|
||
"totalGB": "总上传/下载 (GB)",
|
||
"expiryTime": "过期时间",
|
||
"addClients": "添加客户端",
|
||
"limitIp": "IP 限制",
|
||
"password": "密码",
|
||
"subId": "订阅 ID",
|
||
"online": "在线",
|
||
"email": "邮箱",
|
||
"comment": "备注",
|
||
"traffic": "流量",
|
||
"offline": "离线",
|
||
"addTitle": "添加客户端",
|
||
"qrCode": "二维码",
|
||
"moreInformation": "更多信息",
|
||
"delete": "删除",
|
||
"reset": "重置流量",
|
||
"editTitle": "编辑客户端",
|
||
"client": "客户端",
|
||
"enabled": "已启用",
|
||
"remaining": "剩余",
|
||
"duration": "时长",
|
||
"attachedInbounds": "关联入站",
|
||
"selectInbound": "选择一个或多个入站",
|
||
"noSubId": "该客户端没有 subId，无法生成共享链接。",
|
||
"noLinks": "没有可共享的链接 — 请先将此客户端关联到支持协议的入站。",
|
||
"link": "链接",
|
||
"resetNotPossible": "请先将此客户端关联到入站。",
|
||
"general": "通用",
|
||
"resetAllTraffics": "重置所有客户端流量",
|
||
"resetAllTrafficsTitle": "重置所有客户端流量？",
|
||
"resetAllTrafficsContent": "所有客户端的上下行计数器将归零。配额与过期时间不受影响。该操作不可撤销。",
|
||
"empty": "尚无客户端 — 添加一个开始使用。",
|
||
"deleteConfirmTitle": "删除客户端 {email}？",
|
||
"deleteConfirmContent": "将从所有关联入站中移除该客户端并删除其流量记录。该操作不可撤销。",
|
||
"deleteSelected": "删除 ({count})",
|
||
"bulkDeleteConfirmTitle": "删除 {count} 个客户端？",
|
||
"bulkDeleteConfirmContent": "每个所选客户端都会从关联的入站中被移除，其流量记录也会被删除。该操作不可撤销。",
|
||
"delDepleted": "删除已耗尽",
|
||
"delDepletedConfirmTitle": "删除已耗尽的客户端？",
|
||
"delDepletedConfirmContent": "删除所有流量配额已用尽或已过期的客户端。该操作不可撤销。",
|
||
"auth": "Auth",
|
||
"hysteriaAuth": "Hysteria Auth",
|
||
"uuid": "UUID",
|
||
"flow": "Flow",
|
||
"reverseTag": "Reverse tag",
|
||
"reverseTagPlaceholder": "可选 Reverse tag",
|
||
"telegramId": "Telegram 用户 ID",
|
||
"telegramIdPlaceholder": "数字形式的 Telegram 用户 ID (0 = 无)",
|
||
"created": "创建时间",
|
||
"updated": "更新时间",
|
||
"ipLimit": "IP 限制",
|
||
"toasts": {
|
||
"deleted": "客户端已删除",
|
||
"trafficReset": "流量已重置",
|
||
"allTrafficsReset": "所有客户端流量已重置",
|
||
"bulkDeleted": "已删除 {count} 个客户端",
|
||
"bulkDeletedMixed": "已删除 {ok} 个，失败 {failed} 个",
|
||
"bulkCreated": "已创建 {count} 个客户端",
|
||
"bulkCreatedMixed": "已创建 {ok} 个，失败 {failed} 个",
|
||
"delDepleted": "已删除 {count} 个已耗尽的客户端"
|
||
}
|
||
},
|
||
"nodes": {
|
||
"title": "节点",
|
||
"addNode": "添加节点",
|
||
"editNode": "编辑节点",
|
||
"totalNodes": "节点总数",
|
||
"onlineNodes": "在线",
|
||
"offlineNodes": "离线",
|
||
"avgLatency": "平均延迟",
|
||
"name": "名称",
|
||
"namePlaceholder": "例如：de-frankfurt-1",
|
||
"addressPlaceholder": "panel.example.com 或 1.2.3.4",
|
||
"remark": "备注",
|
||
"scheme": "协议",
|
||
"address": "地址",
|
||
"port": "端口",
|
||
"basePath": "基础路径",
|
||
"apiToken": "API 令牌",
|
||
"apiTokenPlaceholder": "远程面板设置页中的令牌",
|
||
"apiTokenHint": "远程面板在 设置 → API 令牌 中显示其 API 令牌。",
|
||
"regenerate": "重新生成令牌",
|
||
"regenerateConfirm": "重新生成会使当前令牌失效。任何使用该令牌的中央面板都会失去访问权限，直至更新。是否继续？",
|
||
"allowPrivateAddress": "允许私有地址",
|
||
"allowPrivateAddressHint": "仅对私有网络或VPN上的节点启用。",
|
||
"enable": "已启用",
|
||
"status": "状态",
|
||
"cpu": "CPU",
|
||
"mem": "内存",
|
||
"uptime": "运行时间",
|
||
"latency": "延迟",
|
||
"lastHeartbeat": "上次心跳",
|
||
"xrayVersion": "Xray 版本",
|
||
"panelVersion": "面板版本",
|
||
"actions": "操作",
|
||
"probe": "立即探测",
|
||
"testConnection": "测试连接",
|
||
"connectionOk": "连接正常 ({ms} ms)",
|
||
"connectionFailed": "连接失败",
|
||
"never": "从未",
|
||
"justNow": "刚刚",
|
||
"deleteConfirmTitle": "删除节点 \"{name}\"？",
|
||
"deleteConfirmContent": "这将停止监控该节点。远程面板本身不受影响。",
|
||
"statusValues": {
|
||
"online": "在线",
|
||
"offline": "离线",
|
||
"unknown": "未知"
|
||
},
|
||
"toasts": {
|
||
"list": "加载节点失败",
|
||
"obtain": "加载节点失败",
|
||
"add": "添加节点",
|
||
"update": "更新节点",
|
||
"delete": "删除节点",
|
||
"deleted": "节点已删除",
|
||
"test": "测试连接",
|
||
"fillRequired": "名称、地址、端口和 API 令牌为必填项",
|
||
"probeFailed": "探测失败"
|
||
}
|
||
},
|
||
"settings": {
|
||
"title": "面板设置",
|
||
"save": "保存",
|
||
"infoDesc": "此处的所有更改都需要保存并重启面板才能生效",
|
||
"restartPanel": "重启面板",
|
||
"restartPanelDesc": "确定要重启面板吗？若重启后无法访问面板，请前往服务器查看面板日志信息",
|
||
"restartPanelSuccess": "面板已成功重启",
|
||
"actions": "操作",
|
||
"resetDefaultConfig": "重置为默认配置",
|
||
"panelSettings": "常规",
|
||
"securitySettings": "安全设定",
|
||
"TGBotSettings": "Telegram 机器人配置",
|
||
"panelListeningIP": "面板监听 IP",
|
||
"panelListeningIPDesc": "默认留空监听所有 IP",
|
||
"panelListeningDomain": "面板监听域名",
|
||
"panelListeningDomainDesc": "默认情况下留空以监视所有域名和 IP 地址",
|
||
"panelPort": "面板监听端口",
|
||
"panelPortDesc": "重启面板生效",
|
||
"publicKeyPath": "面板证书公钥文件路径",
|
||
"publicKeyPathDesc": "填写一个 '/' 开头的绝对路径",
|
||
"privateKeyPath": "面板证书密钥文件路径",
|
||
"privateKeyPathDesc": "填写一个 '/' 开头的绝对路径",
|
||
"panelUrlPath": "面板 url 根路径",
|
||
"panelUrlPathDesc": "必须以 '/' 开头，以 '/' 结尾",
|
||
"pageSize": "分页大小",
|
||
"pageSizeDesc": "定义入站表的页面大小。设置 0 表示禁用",
|
||
"remarkModel": "备注模型和分隔符",
|
||
"datepicker": "日期选择器",
|
||
"datepickerPlaceholder": "选择日期",
|
||
"datepickerDescription": "选择器日历类型指定到期日期",
|
||
"sampleRemark": "备注示例",
|
||
"oldUsername": "原用户名",
|
||
"currentPassword": "原密码",
|
||
"newUsername": "新用户名",
|
||
"newPassword": "新密码",
|
||
"telegramBotEnable": "启用 Telegram 机器人",
|
||
"telegramBotEnableDesc": "启用 Telegram 机器人功能",
|
||
"telegramToken": "Telegram 机器人令牌（token）",
|
||
"telegramTokenDesc": "从 '{'@'}BotFather' 获取的 Telegram 机器人令牌",
|
||
"telegramProxy": "SOCKS5 Proxy",
|
||
"telegramProxyDesc": "启用 SOCKS5 代理连接到 Telegram（根据指南调整设置）",
|
||
"telegramAPIServer": "Telegram API Server",
|
||
"telegramAPIServerDesc": "要使用的 Telegram API 服务器。留空以使用默认服务器。",
|
||
"telegramChatId": "管理员聊天 ID",
|
||
"telegramChatIdDesc": "Telegram 管理员聊天 ID (多个以逗号分隔)（可通过 {'@'}userinfobot 获取，或在机器人中使用 '/id' 命令获取）",
|
||
"telegramNotifyTime": "通知时间",
|
||
"telegramNotifyTimeDesc": "设置周期性的 Telegram 机器人通知时间（使用 crontab 时间格式）",
|
||
"tgNotifyBackup": "数据库备份",
|
||
"tgNotifyBackupDesc": "发送带有报告的数据库备份文件",
|
||
"tgNotifyLogin": "登录通知",
|
||
"tgNotifyLoginDesc": "当有人试图登录你的面板时显示用户名、IP 地址和时间",
|
||
"sessionMaxAge": "会话时长",
|
||
"sessionMaxAgeDesc": "保持登录状态的时长（单位：分钟）",
|
||
"expireTimeDiff": "到期通知阈值",
|
||
"expireTimeDiffDesc": "达到此阈值时，将收到有关到期时间的通知（单位：天）",
|
||
"trafficDiff": "流量耗尽阈值",
|
||
"trafficDiffDesc": "达到此阈值时，将收到有关流量耗尽的通知（单位：GB）",
|
||
"tgNotifyCpu": "CPU 负载通知阈值",
|
||
"tgNotifyCpuDesc": "CPU 负载超过此阈值时，将收到通知（单位：%）",
|
||
"timeZone": "时区",
|
||
"timeZoneDesc": "定时任务将按照该时区的时间运行",
|
||
"subSettings": "订阅设置",
|
||
"subEnable": "启用订阅服务",
|
||
"subEnableDesc": "启用订阅服务功能",
|
||
"subJsonEnable": "单独启用/禁用 JSON 订阅端点。",
|
||
"subTitle": "订阅标题",
|
||
"subTitleDesc": "在VPN客户端中显示的标题",
|
||
"subSupportUrl": "支持链接",
|
||
"subSupportUrlDesc": "VPN 客户端中显示的技术支持链接",
|
||
"subProfileUrl": "个人资料链接",
|
||
"subProfileUrlDesc": "VPN 客户端中显示的网站链接",
|
||
"subAnnounce": "公告",
|
||
"subAnnounceDesc": "VPN 客户端中显示的公告文本",
|
||
"subEnableRouting": "启用路由",
|
||
"subEnableRoutingDesc": "在 VPN 客户端中启用路由的全局设置。（僅限 Happ）",
|
||
"subRoutingRules": "路由規則",
|
||
"subRoutingRulesDesc": "VPN 用戶端的全域路由規則。（僅限 Happ）",
|
||
"subListen": "监听 IP",
|
||
"subListenDesc": "订阅服务监听的 IP 地址（留空表示监听所有 IP）",
|
||
"subPort": "监听端口",
|
||
"subPortDesc": "订阅服务监听的端口号（必须是未使用的端口）",
|
||
"subCertPath": "公钥路径",
|
||
"subCertPathDesc": "订阅服务使用的公钥文件路径（以 '/' 开头）",
|
||
"subKeyPath": "私钥路径",
|
||
"subKeyPathDesc": "订阅服务使用的私钥文件路径（以 '/' 开头）",
|
||
"subPath": "URI 路径",
|
||
"subPathDesc": "订阅服务使用的 URI 路径（以 '/' 开头，以 '/' 结尾）",
|
||
"subDomain": "监听域名",
|
||
"subDomainDesc": "订阅服务监听的域名（留空表示监听所有域名和 IP）",
|
||
"subUpdates": "更新间隔",
|
||
"subUpdatesDesc": "客户端应用中订阅 URL 的更新间隔（单位：小时）",
|
||
"subEncrypt": "编码",
|
||
"subEncryptDesc": "订阅服务返回的内容将采用 Base64 编码",
|
||
"subShowInfo": "显示使用信息",
|
||
"subShowInfoDesc": "客户端应用中将显示剩余流量和日期信息",
|
||
"subEmailInRemark": "在名称中包含邮箱",
|
||
"subEmailInRemarkDesc": "在订阅配置名称中包含客户端邮箱。",
|
||
"subURI": "反向代理 URI",
|
||
"subURIDesc": "用于代理后面的订阅 URL 的 URI 路径",
|
||
"externalTrafficInformEnable": "外部交通通知",
|
||
"externalTrafficInformEnableDesc": "每次流量更新时通知外部 API",
|
||
"externalTrafficInformURI": "外部流量通知 URI",
|
||
"externalTrafficInformURIDesc": "流量更新将发送到此 URI",
|
||
"restartXrayOnClientDisable": "客户端自动禁用后重启 Xray",
|
||
"restartXrayOnClientDisableDesc": "当客户端因到期或流量超限被自动禁用时，重启 Xray。",
|
||
"fragment": "分片",
|
||
"fragmentDesc": "启用 TLS hello 数据包分片",
|
||
"fragmentSett": "设置",
|
||
"noisesDesc": "启用 Noises.",
|
||
"noisesSett": "Noises 设置",
|
||
"mux": "多路复用器",
|
||
"muxDesc": "在已建立的数据流内传输多个独立的数据流",
|
||
"muxSett": "复用器设置",
|
||
"direct": "直接连接",
|
||
"directDesc": "直接与特定国家的域或IP范围建立连接",
|
||
"notifications": "通知",
|
||
"certs": "证书",
|
||
"externalTraffic": "外部流量",
|
||
"dateAndTime": "日期和时间",
|
||
"proxyAndServer": "代理和服务器",
|
||
"intervals": "间隔",
|
||
"information": "信息",
|
||
"language": "语言",
|
||
"telegramBotLanguage": "Telegram 机器人语言",
|
||
"security": {
|
||
"admin": "管理员凭据",
|
||
"twoFactor": "双重验证",
|
||
"twoFactorEnable": "启用2FA",
|
||
"twoFactorEnableDesc": "增加额外的验证层以提高安全性。",
|
||
"twoFactorModalSetTitle": "启用双重认证",
|
||
"twoFactorModalDeleteTitle": "停用双重认证",
|
||
"twoFactorModalSteps": "要设定双重认证，请执行以下步骤：",
|
||
"twoFactorModalFirstStep": "1. 在认证应用程序中扫描此QR码，或复制QR码附近的令牌并粘贴到应用程序中",
|
||
"twoFactorModalSecondStep": "2. 输入应用程序中的验证码",
|
||
"twoFactorModalRemoveStep": "输入应用程序中的验证码以移除双重认证。",
|
||
"twoFactorModalChangeCredentialsTitle": "更改凭据",
|
||
"twoFactorModalChangeCredentialsStep": "输入应用程序中的代码以更改管理员凭据。",
|
||
"twoFactorModalSetSuccess": "双因素认证已成功建立",
|
||
"twoFactorModalDeleteSuccess": "双因素认证已成功删除",
|
||
"twoFactorModalError": "验证码错误",
|
||
"show": "显示",
|
||
"hide": "隐藏",
|
||
"apiTokenNew": "新建令牌",
|
||
"apiTokenName": "名称",
|
||
"apiTokenNamePlaceholder": "例如 central-panel-a",
|
||
"apiTokenNameRequired": "名称必填",
|
||
"apiTokenEmpty": "暂无令牌 — 创建一个用于认证机器人或远程面板。",
|
||
"apiTokenDeleteWarning": "使用此令牌的任何调用方将立即无法认证。"
|
||
},
|
||
"toasts": {
|
||
"modifySettings": "参数已更改。",
|
||
"getSettings": "获取参数时发生错误",
|
||
"modifyUserError": "更改管理员凭据时发生错误。",
|
||
"modifyUser": "您已成功更改管理员凭据。",
|
||
"originalUserPassIncorrect": "原用户名或原密码错误",
|
||
"userPassMustBeNotEmpty": "新用户名和新密码不能为空",
|
||
"getOutboundTrafficError": "获取出站流量错误",
|
||
"resetOutboundTrafficError": "重置出站流量错误"
|
||
}
|
||
},
|
||
"xray": {
|
||
"title": "Xray 配置",
|
||
"save": "保存",
|
||
"restart": "重新启动 Xray",
|
||
"restartSuccess": "Xray 已成功重新启动",
|
||
"stopSuccess": "Xray 已成功停止",
|
||
"restartError": "重启Xray时发生错误。",
|
||
"stopError": "停止Xray时发生错误。",
|
||
"basicTemplate": "基础配置",
|
||
"advancedTemplate": "高级配置",
|
||
"generalConfigs": "常规配置",
|
||
"generalConfigsDesc": "这些选项将决定常规配置",
|
||
"logConfigs": "日志",
|
||
"logConfigsDesc": "日志可能会影响服务器的性能，建议仅在需要时启用",
|
||
"blockConfigsDesc": "这些选项将阻止用户连接到特定协议和网站",
|
||
"basicRouting": "基本路由",
|
||
"blockConnectionsConfigsDesc": "这些选项将根据特定的请求国家阻止流量。",
|
||
"directConnectionsConfigsDesc": "直接连接确保特定的流量不会通过其他服务器路由。",
|
||
"blockips": "阻止IP",
|
||
"blockdomains": "阻止域名",
|
||
"directips": "直接IP",
|
||
"directdomains": "直接域名",
|
||
"ipv4Routing": "IPv4 路由",
|
||
"ipv4RoutingDesc": "此选项将仅通过 IPv4 路由到目标域",
|
||
"warpRouting": "WARP 路由",
|
||
"warpRoutingDesc": "注意：在使用这些选项之前，请按照面板 GitHub 上的步骤在你的服务器上以 socks5 代理模式安装 WARP。WARP 将通过 Cloudflare 服务器将流量路由到网站。",
|
||
"nordRouting": "NordVPN 路由",
|
||
"nordRoutingDesc": "这些选项将根据特定目的地通过 NordVPN 路由流量。",
|
||
"Template": "高级 Xray 配置模板",
|
||
"TemplateDesc": "最终的 Xray 配置文件将基于此模板生成",
|
||
"FreedomStrategy": "Freedom 协议策略",
|
||
"FreedomStrategyDesc": "设置 Freedom 协议中网络的输出策略",
|
||
"RoutingStrategy": "配置路由域策略",
|
||
"RoutingStrategyDesc": "设置 DNS 解析的整体路由策略",
|
||
"outboundTestUrl": "出站测试 URL",
|
||
"outboundTestUrlDesc": "测试出站连接时使用的 URL",
|
||
"Torrent": "屏蔽 BitTorrent 协议",
|
||
"Inbounds": "入站规则",
|
||
"InboundsDesc": "接受来自特定客户端的流量",
|
||
"Outbounds": "出站规则",
|
||
"Balancers": "负载均衡",
|
||
"OutboundsDesc": "设置出站流量传出方式",
|
||
"Routings": "路由规则",
|
||
"RoutingsDesc": "每条规则的优先级都很重要",
|
||
"completeTemplate": "全部",
|
||
"logLevel": "日志级别",
|
||
"logLevelDesc": "错误日志的日志级别，用于指示需要记录的信息",
|
||
"accessLog": "访问日志",
|
||
"accessLogDesc": "访问日志的文件路径。特殊值 'none' 禁用访问日志",
|
||
"errorLog": "错误日志",
|
||
"errorLogDesc": "错误日志的文件路径。特殊值 'none' 禁用错误日志",
|
||
"dnsLog": "DNS 日志",
|
||
"dnsLogDesc": "是否启用 DNS 查询日志",
|
||
"maskAddress": "隐藏地址",
|
||
"maskAddressDesc": "IP 地址掩码，启用时会自动替换日志中出现的 IP 地址。",
|
||
"statistics": "统计",
|
||
"statsInboundUplink": "入站上传统计",
|
||
"statsInboundUplinkDesc": "启用所有入站代理的上行流量统计收集。",
|
||
"statsInboundDownlink": "入站下载统计",
|
||
"statsInboundDownlinkDesc": "启用所有入站代理的下行流量统计收集。",
|
||
"statsOutboundUplink": "出站上传统计",
|
||
"statsOutboundUplinkDesc": "启用所有出站代理的上行流量统计收集。",
|
||
"statsOutboundDownlink": "出站下载统计",
|
||
"statsOutboundDownlinkDesc": "启用所有出站代理的下行流量统计收集。",
|
||
"rules": {
|
||
"first": "置顶",
|
||
"last": "置底",
|
||
"up": "向上",
|
||
"down": "向下",
|
||
"source": "来源",
|
||
"dest": "目的地址",
|
||
"inbound": "入站",
|
||
"outbound": "出站",
|
||
"balancer": "负载均衡",
|
||
"info": "信息",
|
||
"add": "添加规则",
|
||
"edit": "编辑规则",
|
||
"useComma": "逗号分隔的项目"
|
||
},
|
||
"outbound": {
|
||
"addOutbound": "添加出站",
|
||
"addReverse": "添加反向",
|
||
"editOutbound": "编辑出站",
|
||
"editReverse": "编辑反向",
|
||
"reverseTag": "反向标签",
|
||
"reverseTagDesc": "VLESS 简易反向代理出站标签。留空则禁用。设置后，此客户端的连接可用作反向代理隧道。",
|
||
"reverseTagPlaceholder": "出站标签（留空则禁用）",
|
||
"tag": "标签",
|
||
"tagDesc": "唯一标签",
|
||
"address": "地址",
|
||
"reverse": "反向",
|
||
"domain": "域名",
|
||
"type": "类型",
|
||
"bridge": "Bridge",
|
||
"portal": "Portal",
|
||
"link": "链接",
|
||
"intercon": "互连",
|
||
"settings": "设置",
|
||
"accountInfo": "帐户信息",
|
||
"outboundStatus": "出站状态",
|
||
"sendThrough": "发送通过",
|
||
"test": "测试",
|
||
"testResult": "测试结果",
|
||
"testing": "正在测试连接...",
|
||
"testSuccess": "测试成功",
|
||
"testFailed": "测试失败",
|
||
"testError": "测试出站失败",
|
||
"nordvpn": "NordVPN",
|
||
"accessToken": "访问令牌",
|
||
"country": "国家",
|
||
"server": "服务器",
|
||
"city": "城市",
|
||
"allCities": "所有城市",
|
||
"privateKey": "私钥",
|
||
"load": "负载"
|
||
},
|
||
"balancer": {
|
||
"addBalancer": "添加负载均衡",
|
||
"editBalancer": "编辑负载均衡",
|
||
"balancerStrategy": "策略",
|
||
"balancerSelectors": "选择器",
|
||
"tag": "标签",
|
||
"tagDesc": "唯一标签",
|
||
"balancerDesc": "无法同时使用 balancerTag 和 outboundTag。如果同时使用，则只有 outboundTag 会生效。"
|
||
},
|
||
"wireguard": {
|
||
"secretKey": "密钥",
|
||
"publicKey": "公钥",
|
||
"allowedIPs": "允许的 IP",
|
||
"endpoint": "端点",
|
||
"psk": "共享密钥",
|
||
"domainStrategy": "域策略"
|
||
},
|
||
"tun": {
|
||
"nameDesc": "TUN 接口的名称。默认值为 'xray0'",
|
||
"mtuDesc": "最大传输单元。数据包的最大大小。默认值为 1500",
|
||
"userLevel": "用户级别",
|
||
"userLevelDesc": "通过此入站的所有连接都将使用此用户级别。默认值为 0"
|
||
},
|
||
"dns": {
|
||
"enable": "启用 DNS",
|
||
"enableDesc": "启用内置 DNS 服务器",
|
||
"tag": "DNS 入站标签",
|
||
"tagDesc": "此标签将在路由规则中可用作入站标签",
|
||
"clientIp": "客户端IP",
|
||
"clientIpDesc": "用于在DNS查询期间通知服务器指定的IP位置",
|
||
"disableCache": "禁用缓存",
|
||
"disableCacheDesc": "禁用DNS缓存",
|
||
"disableFallback": "禁用回退",
|
||
"disableFallbackDesc": "禁用回退DNS查询",
|
||
"disableFallbackIfMatch": "匹配时禁用回退",
|
||
"disableFallbackIfMatchDesc": "当DNS服务器的匹配域名列表命中时，禁用回退DNS查询",
|
||
"enableParallelQuery": "启用并行查询",
|
||
"enableParallelQueryDesc": "启用并行DNS查询到多个服务器以实现更快的解析",
|
||
"strategy": "查询策略",
|
||
"strategyDesc": "解析域名的总体策略",
|
||
"add": "添加服务器",
|
||
"edit": "编辑服务器",
|
||
"domains": "域",
|
||
"expectIPs": "预期 IP",
|
||
"unexpectIPs": "意外IP",
|
||
"useSystemHosts": "使用系统Hosts",
|
||
"useSystemHostsDesc": "使用已安装系统的hosts文件",
|
||
"serveStale": "提供过期结果",
|
||
"serveStaleDesc": "在后台刷新时返回过期的缓存结果",
|
||
"serveExpiredTTL": "过期TTL",
|
||
"serveExpiredTTLDesc": "过期缓存条目的有效期（秒）；0 = 永不过期",
|
||
"timeoutMs": "超时 (毫秒)",
|
||
"skipFallback": "跳过回退",
|
||
"finalQuery": "最终查询",
|
||
"hosts": "Hosts",
|
||
"hostsAdd": "添加 Host",
|
||
"hostsEmpty": "未定义任何 Host",
|
||
"hostsDomain": "域名 (例如 domain:example.com)",
|
||
"hostsValues": "IP 或域名 — 输入后按 Enter",
|
||
"usePreset": "使用模板",
|
||
"dnsPresetTitle": "DNS模板",
|
||
"dnsPresetFamily": "家庭",
|
||
"clearAll": "删除全部",
|
||
"clearAllTitle": "删除所有 DNS 服务器？",
|
||
"clearAllConfirm": "此操作将从列表中删除所有 DNS 服务器，且无法撤销。"
|
||
},
|
||
"fakedns": {
|
||
"add": "添加假 DNS",
|
||
"edit": "编辑假 DNS",
|
||
"ipPool": "IP 池子网",
|
||
"poolSize": "池大小"
|
||
}
|
||
}
|
||
},
|
||
"tgbot": {
|
||
"keyboardClosed": "❌ 自定义键盘已关闭！",
|
||
"noResult": "❗ 没有结果！",
|
||
"noQuery": "❌ 未找到查询！请再次使用该命令！",
|
||
"wentWrong": "❌ 出了点问题！",
|
||
"noIpRecord": "❗ 没有IP记录！",
|
||
"noInbounds": "❗ 未找到入站！",
|
||
"unlimited": "♾ 无限（重置）",
|
||
"add": "添加",
|
||
"month": "月",
|
||
"months": "月",
|
||
"day": "天",
|
||
"days": "天",
|
||
"hours": "小时",
|
||
"minutes": "分钟",
|
||
"unknown": "未知",
|
||
"inbounds": "入站",
|
||
"clients": "客户端",
|
||
"offline": "🔴 离线",
|
||
"online": "🟢 在线",
|
||
"commands": {
|
||
"unknown": "❗ 未知命令",
|
||
"pleaseChoose": "👇 请选择：\r\n",
|
||
"help": "🤖 欢迎使用本机器人！它旨在为您提供来自服务器的特定数据，并允许您进行必要的修改。\r\n\r\n",
|
||
"start": "👋 你好，<i>{{ .Firstname }}</i>。\r\n",
|
||
"welcome": "🤖 欢迎来到 <b>{{ .Hostname }}</b> 管理机器人。\r\n",
|
||
"status": "✅ 机器人正常运行！",
|
||
"usage": "❗ 请输入要搜索的文本！",
|
||
"getID": "🆔 您的 ID 为：<code>{{ .ID }}</code>",
|
||
"helpAdminCommands": "要重新启动 Xray Core：\r\n<code>/restart</code>\r\n\r\n要搜索客户电子邮件：\r\n<code>/usage [电子邮件]</code>\r\n\r\n要搜索入站（带有客户统计数据）：\r\n<code>/inbound [备注]</code>\r\n\r\nTelegram聊天ID：\r\n<code>/id</code>",
|
||
"helpClientCommands": "要搜索统计数据，请使用以下命令：\r\n<code>/usage [电子邮件]</code>\r\n\r\nTelegram聊天ID：\r\n<code>/id</code>",
|
||
"restartUsage": "\r\n\r\n<code>/restart</code>",
|
||
"restartSuccess": "✅ 操作成功!",
|
||
"restartFailed": "❗ 操作错误。\r\n\r\n<code>错误: {{ .Error }}</code>.",
|
||
"xrayNotRunning": "❗ Xray Core 未运行。",
|
||
"startDesc": "显示主菜单",
|
||
"helpDesc": "机器人帮助",
|
||
"statusDesc": "检查机器人状态",
|
||
"idDesc": "显示您的 Telegram ID"
|
||
},
|
||
"messages": {
|
||
"cpuThreshold": "🔴 CPU 使用率为 {{ .Percent }}%，超过阈值 {{ .Threshold }}%",
|
||
"selectUserFailed": "❌ 用户选择错误！",
|
||
"userSaved": "✅ 电报用户已保存。",
|
||
"loginSuccess": "✅ 成功登录到面板。\r\n",
|
||
"loginFailed": "❗️ 面板登录失败。\r\n",
|
||
"2faFailed": "2FA 失败",
|
||
"report": "🕰 定时报告：{{ .RunTime }}\r\n",
|
||
"datetime": "⏰ 日期时间：{{ .DateTime }}\r\n",
|
||
"hostname": "💻 主机名：{{ .Hostname }}\r\n",
|
||
"version": "🚀 X-UI 版本：{{ .Version }}\r\n",
|
||
"xrayVersion": "📡 Xray 版本: {{ .XrayVersion }}\r\n",
|
||
"ipv6": "🌐 IPv6：{{ .IPv6 }}\r\n",
|
||
"ipv4": "🌐 IPv4：{{ .IPv4 }}\r\n",
|
||
"ip": "🌐 IP：{{ .IP }}\r\n",
|
||
"ips": "🔢 IP 地址：\r\n{{ .IPs }}\r\n",
|
||
"serverUpTime": "⏳ 服务器运行时间：{{ .UpTime }} {{ .Unit }}\r\n",
|
||
"serverLoad": "📈 服务器负载：{{ .Load1 }}, {{ .Load2 }}, {{ .Load3 }}\r\n",
|
||
"serverMemory": "📋 服务器内存：{{ .Current }}/{{ .Total }}\r\n",
|
||
"tcpCount": "🔹 TCP 连接数：{{ .Count }}\r\n",
|
||
"udpCount": "🔸 UDP 连接数：{{ .Count }}\r\n",
|
||
"traffic": "🚦 流量：{{ .Total }} (↑{{ .Upload }},↓{{ .Download }})\r\n",
|
||
"xrayStatus": "ℹ️ Xray 状态：{{ .State }}\r\n",
|
||
"username": "👤 用户名：{{ .Username }}\r\n",
|
||
"reason": "❗️ 原因：{{ .Reason }}\r\n",
|
||
"time": "⏰ 时间：{{ .Time }}\r\n",
|
||
"inbound": "📍 入站：{{ .Remark }}\r\n",
|
||
"port": "🔌 端口：{{ .Port }}\r\n",
|
||
"expire": "📅 过期日期：{{ .Time }}\r\n",
|
||
"expireIn": "📅 剩余时间：{{ .Time }}\r\n",
|
||
"active": "💡 激活：{{ .Enable }}\r\n",
|
||
"enabled": "🚨 已启用：{{ .Enable }}\r\n",
|
||
"online": "🌐 连接状态：{{ .Status }}\r\n",
|
||
"lastOnline": "🔙 上次在线: {{ .Time }}\r\n",
|
||
"email": "📧 邮箱：{{ .Email }}\r\n",
|
||
"upload": "🔼 上传↑：{{ .Upload }}\r\n",
|
||
"download": "🔽 下载↓：{{ .Download }}\r\n",
|
||
"total": "📊 总计：{{ .UpDown }} / {{ .Total }}\r\n",
|
||
"TGUser": "👤 电报用户：{{ .TelegramID }}\r\n",
|
||
"exhaustedMsg": "🚨 耗尽的 {{ .Type }}：\r\n",
|
||
"exhaustedCount": "🚨 耗尽的 {{ .Type }} 数量：\r\n",
|
||
"onlinesCount": "🌐 在线客户：{{ .Count }}\r\n",
|
||
"disabled": "🛑 禁用：{{ .Disabled }}\r\n",
|
||
"depleteSoon": "🔜 即将耗尽：{{ .Deplete }}\r\n\r\n",
|
||
"backupTime": "🗄 备份时间：{{ .Time }}\r\n",
|
||
"refreshedOn": "\r\n📋🔄 刷新时间：{{ .Time }}\r\n\r\n",
|
||
"yes": "✅ 是的",
|
||
"no": "❌ 没有",
|
||
"received_id": "🔑📥 ID 已更新。",
|
||
"received_password": "🔑📥 密码已更新。",
|
||
"received_email": "📧📥 邮箱已更新。",
|
||
"received_comment": "💬📥 评论已更新。",
|
||
"id_prompt": "🔑 默认 ID: {{ .ClientId }}\n\n请输入您的 ID。",
|
||
"pass_prompt": "🔑 默认密码: {{ .ClientPassword }}\n\n请输入您的密码。",
|
||
"email_prompt": "📧 默认邮箱: {{ .ClientEmail }}\n\n请输入您的邮箱。",
|
||
"comment_prompt": "💬 默认评论: {{ .ClientComment }}\n\n请输入您的评论。",
|
||
"inbound_client_data_id": "🔄 入站: {{ .InboundRemark }}\n\n🔑 ID: {{ .ClientId }}\n📧 邮箱: {{ .ClientEmail }}\n📊 流量: {{ .ClientTraffic }}\n📅 到期日期: {{ .ClientExp }}\n🌐 IP 限制: {{ .IpLimit }}\n💬 备注: {{ .ClientComment }}\n\n你现在可以将客户添加到入站了！",
|
||
"inbound_client_data_pass": "🔄 入站: {{ .InboundRemark }}\n\n🔑 密码: {{ .ClientPass }}\n📧 邮箱: {{ .ClientEmail }}\n📊 流量: {{ .ClientTraffic }}\n📅 到期日期: {{ .ClientExp }}\n🌐 IP 限制: {{ .IpLimit }}\n💬 备注: {{ .ClientComment }}\n\n你现在可以将客户添加到入站了！",
|
||
"cancel": "❌ 进程已取消！\n\n您可以随时使用 /start 重新开始。 🔄",
|
||
"error_add_client": "⚠️ 错误:\n\n {{ .error }}",
|
||
"using_default_value": "好的，我会使用默认值。 😊",
|
||
"incorrect_input": "您的输入无效。\n短语应连续输入，不能有空格。\n正确示例: aaaaaa\n错误示例: aaa aaa 🚫",
|
||
"AreYouSure": "你确定吗？🤔",
|
||
"SuccessResetTraffic": "📧 邮箱: {{ .ClientEmail }}\n🏁 结果: ✅ 成功",
|
||
"FailedResetTraffic": "📧 邮箱: {{ .ClientEmail }}\n🏁 结果: ❌ 失败 \n\n🛠️ 错误: [ {{ .ErrorMessage }} ]",
|
||
"FinishProcess": "🔚 所有客户的流量重置已完成。"
|
||
},
|
||
"buttons": {
|
||
"closeKeyboard": "❌ 关闭键盘",
|
||
"cancel": "❌ 取消",
|
||
"cancelReset": "❌ 取消重置",
|
||
"cancelIpLimit": "❌ 取消 IP 限制",
|
||
"confirmResetTraffic": "✅ 确认重置流量？",
|
||
"confirmClearIps": "✅ 确认清除 IP？",
|
||
"confirmRemoveTGUser": "✅ 确认移除 Telegram 用户？",
|
||
"confirmToggle": "✅ 确认启用/禁用用户？",
|
||
"dbBackup": "获取数据库备份",
|
||
"serverUsage": "服务器使用情况",
|
||
"getInbounds": "获取入站信息",
|
||
"depleteSoon": "即将耗尽",
|
||
"clientUsage": "获取使用情况",
|
||
"onlines": "在线客户端",
|
||
"commands": "命令",
|
||
"refresh": "🔄 刷新",
|
||
"clearIPs": "❌ 清除 IP",
|
||
"removeTGUser": "❌ 移除 Telegram 用户",
|
||
"selectTGUser": "👤 选择 Telegram 用户",
|
||
"selectOneTGUser": "👤 选择一个 Telegram 用户：",
|
||
"resetTraffic": "📈 重置流量",
|
||
"resetExpire": "📅 更改到期日期",
|
||
"ipLog": "🔢 IP 日志",
|
||
"ipLimit": "🔢 IP 限制",
|
||
"setTGUser": "👤 设置 Telegram 用户",
|
||
"toggle": "🔘 启用/禁用",
|
||
"custom": "🔢 风俗",
|
||
"confirmNumber": "✅ 确认: {{ .Num }}",
|
||
"confirmNumberAdd": "✅ 确认添加：{{ .Num }}",
|
||
"limitTraffic": "🚧 流量限制",
|
||
"getBanLogs": "禁止日志",
|
||
"allClients": "所有客户",
|
||
"addClient": "添加客户",
|
||
"submitDisable": "提交为禁用 ☑️",
|
||
"submitEnable": "提交为启用 ✅",
|
||
"use_default": "🏷️ 使用默认",
|
||
"change_id": "⚙️🔑 ID",
|
||
"change_password": "⚙️🔑 密码",
|
||
"change_email": "⚙️📧 邮箱",
|
||
"change_comment": "⚙️💬 评论",
|
||
"change_flow": "⚙️🚦 流控",
|
||
"ResetAllTraffics": "重置所有流量",
|
||
"SortedTrafficUsageReport": "排序的流量使用报告"
|
||
},
|
||
"answers": {
|
||
"successfulOperation": "✅ 成功！",
|
||
"errorOperation": "❗ 操作错误。",
|
||
"getInboundsFailed": "❌ 获取入站信息失败。",
|
||
"getClientsFailed": "❌ 获取客户失败。",
|
||
"canceled": "❌ {{ .Email }}：操作已取消。",
|
||
"clientRefreshSuccess": "✅ {{ .Email }}：客户端刷新成功。",
|
||
"IpRefreshSuccess": "✅ {{ .Email }}：IP 刷新成功。",
|
||
"TGIdRefreshSuccess": "✅ {{ .Email }}：客户端的 Telegram 用户刷新成功。",
|
||
"resetTrafficSuccess": "✅ {{ .Email }}：流量已重置成功。",
|
||
"setTrafficLimitSuccess": "✅ {{ .Email }}: 流量限制保存成功。",
|
||
"expireResetSuccess": "✅ {{ .Email }}：过期天数已重置成功。",
|
||
"resetIpSuccess": "✅ {{ .Email }}：成功保存 IP 限制数量为 {{ .Count }}。",
|
||
"clearIpSuccess": "✅ {{ .Email }}：IP 已成功清除。",
|
||
"getIpLog": "✅ {{ .Email }}：获取 IP 日志。",
|
||
"getUserInfo": "✅ {{ .Email }}：获取 Telegram 用户信息。",
|
||
"removedTGUserSuccess": "✅ {{ .Email }}：Telegram 用户已成功移除。",
|
||
"enableSuccess": "✅ {{ .Email }}：已成功启用。",
|
||
"disableSuccess": "✅ {{ .Email }}：已成功禁用。",
|
||
"askToAddUserId": "未找到您的配置！\r\n请向管理员询问，在您的配置中使用您的 Telegram 用户 ChatID。\r\n\r\n您的用户 ChatID：<code>{{ .TgUserID }}</code>",
|
||
"chooseClient": "为入站 {{ .Inbound }} 选择一个客户",
|
||
"chooseInbound": "选择一个入站"
|
||
}
|
||
}
|
||
} |