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
59 KiB
JSON
1092 lines
No EOL
59 KiB
JSON
{
|
||
"username": "Nombre de Usuario",
|
||
"password": "Contraseña",
|
||
"login": "Acceder",
|
||
"confirm": "Confirmar",
|
||
"cancel": "Cancelar",
|
||
"close": "Cerrar",
|
||
"save": "Guardar",
|
||
"logout": "Cerrar Sesión",
|
||
"create": "Crear",
|
||
"update": "Actualizar",
|
||
"copy": "Copiar",
|
||
"copied": "Copiado",
|
||
"download": "Descargar",
|
||
"remark": "Notas",
|
||
"enable": "Habilitar",
|
||
"protocol": "Protocolo",
|
||
"search": "Buscar",
|
||
"filter": "Filtrar",
|
||
"loading": "Cargando...",
|
||
"refresh": "Actualizar",
|
||
"clear": "Borrar",
|
||
"second": "Segundo",
|
||
"minute": "Minuto",
|
||
"hour": "Hora",
|
||
"day": "Día",
|
||
"check": "Verificar",
|
||
"indefinite": "Indefinido",
|
||
"unlimited": "Ilimitado",
|
||
"none": "None",
|
||
"qrCode": "Código QR",
|
||
"info": "Más Información",
|
||
"edit": "Editar",
|
||
"delete": "Eliminar",
|
||
"reset": "Restablecer",
|
||
"noData": "Sin datos",
|
||
"copySuccess": "Copiado exitosamente",
|
||
"sure": "Seguro",
|
||
"encryption": "Encriptación",
|
||
"useIPv4ForHost": "Usar IPv4 para el host",
|
||
"transmission": "Transmisión",
|
||
"host": "Host",
|
||
"path": "Path",
|
||
"camouflage": "Camuflaje",
|
||
"status": "Estado",
|
||
"enabled": "Habilitado",
|
||
"disabled": "Deshabilitado",
|
||
"depleted": "Agotado",
|
||
"depletingSoon": "Agotándose",
|
||
"offline": "fuera de línea",
|
||
"online": "en línea",
|
||
"domainName": "Nombre de dominio",
|
||
"monitor": "Listening IP",
|
||
"certificate": "Certificado Digital",
|
||
"fail": "Falló",
|
||
"comment": "Comentario",
|
||
"success": "Éxito",
|
||
"lastOnline": "Última conexión",
|
||
"getVersion": "Obtener versión",
|
||
"install": "Instalar",
|
||
"clients": "Clientes",
|
||
"usage": "Uso",
|
||
"twoFactorCode": "Código",
|
||
"remained": "Restante",
|
||
"security": "Seguridad",
|
||
"secAlertTitle": "Alerta de Seguridad",
|
||
"secAlertSsl": "Esta conexión no es segura. Por favor, evite ingresar información sensible hasta que se active TLS para la protección de datos.",
|
||
"secAlertConf": "Ciertas configuraciones son vulnerables a ataques. Se recomienda reforzar los protocolos de seguridad para prevenir posibles violaciones.",
|
||
"secAlertSSL": "El panel carece de una conexión segura. Por favor, instale un certificado TLS para la protección de datos.",
|
||
"secAlertPanelPort": "El puerto predeterminado del panel es vulnerable. Por favor, configure un puerto aleatorio o específico.",
|
||
"secAlertPanelURI": "La ruta URI predeterminada del panel no es segura. Por favor, configure una ruta URI compleja.",
|
||
"secAlertSubURI": "La ruta URI predeterminada de la suscripción no es segura. Por favor, configure una ruta URI compleja.",
|
||
"secAlertSubJsonURI": "La ruta URI JSON predeterminada de la suscripción no es segura. Por favor, configure una ruta URI compleja.",
|
||
"emptyDnsDesc": "No hay servidores DNS añadidos.",
|
||
"emptyFakeDnsDesc": "No hay servidores Fake DNS añadidos.",
|
||
"emptyBalancersDesc": "No hay balanceadores añadidos.",
|
||
"emptyReverseDesc": "No hay proxies inversos añadidos.",
|
||
"somethingWentWrong": "Algo salió mal",
|
||
"subscription": {
|
||
"title": "Información de suscripción",
|
||
"subId": "ID de suscripción",
|
||
"status": "Estado",
|
||
"downloaded": "Descargado",
|
||
"uploaded": "Subido",
|
||
"expiry": "Caducidad",
|
||
"totalQuota": "Cuota total",
|
||
"individualLinks": "Enlaces individuales",
|
||
"active": "Activo",
|
||
"inactive": "Inactivo",
|
||
"unlimited": "Ilimitado",
|
||
"noExpiry": "Sin caducidad"
|
||
},
|
||
"menu": {
|
||
"theme": "Tema",
|
||
"dark": "Oscuro",
|
||
"ultraDark": "Ultra Oscuro",
|
||
"dashboard": "Estado del Sistema",
|
||
"inbounds": "Entradas",
|
||
"clients": "Clientes",
|
||
"nodes": "Nodos",
|
||
"settings": "Configuraciones",
|
||
"xray": "Ajustes Xray",
|
||
"apiDocs": "Documentación de la API",
|
||
"logout": "Cerrar Sesión",
|
||
"link": "Gestionar"
|
||
},
|
||
"pages": {
|
||
"login": {
|
||
"hello": "Hola",
|
||
"title": "Bienvenido",
|
||
"loginAgain": "El límite de tiempo de inicio de sesión ha expirado. Por favor, inicia sesión nuevamente.",
|
||
"toasts": {
|
||
"invalidFormData": "El formato de los datos de entrada es inválido.",
|
||
"emptyUsername": "Por favor ingresa el nombre de usuario.",
|
||
"emptyPassword": "Por favor ingresa la contraseña.",
|
||
"wrongUsernameOrPassword": "Nombre de usuario, contraseña o código de dos factores incorrecto.",
|
||
"successLogin": "Has iniciado sesión en tu cuenta correctamente."
|
||
}
|
||
},
|
||
"index": {
|
||
"title": "Estado del Sistema",
|
||
"cpu": "CPU",
|
||
"logicalProcessors": "Procesadores lógicos",
|
||
"frequency": "Frecuencia",
|
||
"swap": "Memoria Virtual",
|
||
"storage": "Almacenamiento",
|
||
"memory": "RAM",
|
||
"threads": "Hilos",
|
||
"xrayStatus": "Xray",
|
||
"stopXray": "Detener",
|
||
"restartXray": "Reiniciar",
|
||
"xraySwitch": "Versión",
|
||
"xrayUpdates": "Actualizaciones de Xray",
|
||
"xraySwitchClick": "Elige la versión a la que deseas cambiar.",
|
||
"xraySwitchClickDesk": "Elige sabiamente, ya que las versiones anteriores pueden no ser compatibles con las configuraciones actuales.",
|
||
"updatePanel": "Actualizar panel",
|
||
"panelUpdateDesc": "Esto actualizará 3X-UI a la última versión y reiniciará el servicio del panel.",
|
||
"currentPanelVersion": "Versión actual del panel",
|
||
"latestPanelVersion": "Última versión del panel",
|
||
"panelUpToDate": "El panel está actualizado",
|
||
"upToDate": "Actualizado",
|
||
"xrayStatusUnknown": "Desconocido",
|
||
"xrayStatusRunning": "En ejecución",
|
||
"xrayStatusStop": "Detenido",
|
||
"xrayStatusError": "Error",
|
||
"xrayErrorPopoverTitle": "Se produjo un error al ejecutar Xray",
|
||
"operationHours": "Tiempo de Funcionamiento",
|
||
"systemHistoryTitle": "Historial del Sistema",
|
||
"charts": "Gráficos",
|
||
"xrayMetricsTitle": "Métricas de Xray",
|
||
"xrayMetricsDisabled": "Endpoint de métricas de Xray no configurado",
|
||
"xrayMetricsHint": "Añade un bloque metrics de nivel superior a la configuración de xray con tag metrics_out y listen 127.0.0.1:11111, luego reinicia xray.",
|
||
"xrayObservatoryEmpty": "Aún no hay datos de Observatory",
|
||
"xrayObservatoryHint": "Añade un bloque observatory a la configuración de xray listando los tags de outbound a sondear, luego reinicia xray.",
|
||
"xrayObservatoryTagPlaceholder": "Seleccionar outbound",
|
||
"xrayObservatoryAlive": "Activo",
|
||
"xrayObservatoryDead": "Caído",
|
||
"xrayObservatoryLastSeen": "Visto por última vez",
|
||
"xrayObservatoryLastTry": "Último intento",
|
||
"trendLast2Min": "Últimos 2 minutos",
|
||
"systemLoad": "Carga del Sistema",
|
||
"systemLoadDesc": "promedio de carga del sistema en los últimos 1, 5 y 15 minutos",
|
||
"connectionCount": "Número de Conexiones",
|
||
"ipAddresses": "Direcciones IP",
|
||
"toggleIpVisibility": "Alternar visibilidad de la IP",
|
||
"overallSpeed": "Velocidad general",
|
||
"upload": "Subida",
|
||
"download": "Descarga",
|
||
"totalData": "Datos totales",
|
||
"sent": "Enviado",
|
||
"received": "Recibido",
|
||
"documentation": "Documentación",
|
||
"xraySwitchVersionDialog": "¿Realmente deseas cambiar la versión de Xray?",
|
||
"xraySwitchVersionDialogDesc": "Esto cambiará la versión de Xray a #version#.",
|
||
"xraySwitchVersionPopover": "Xray se actualizó correctamente",
|
||
"panelUpdateDialog": "¿Deseas actualizar el panel?",
|
||
"panelUpdateDialogDesc": "Esto actualizará 3X-UI a la versión #version# y reiniciará el servicio del panel.",
|
||
"panelUpdateCheckPopover": "Fallo al comprobar actualización del panel",
|
||
"panelUpdateStartedPopover": "Actualización del panel iniciada",
|
||
"geofileUpdateDialog": "¿Realmente deseas actualizar el geofichero?",
|
||
"geofileUpdateDialogDesc": "Esto actualizará el archivo #filename#.",
|
||
"geofilesUpdateDialogDesc": "Esto actualizará todos los archivos.",
|
||
"geofilesUpdateAll": "Actualizar todo",
|
||
"geofileUpdatePopover": "Geofichero actualizado correctamente",
|
||
"customGeoTitle": "GeoSite / GeoIP personalizados",
|
||
"customGeoAdd": "Añadir",
|
||
"customGeoType": "Tipo",
|
||
"customGeoAlias": "Alias",
|
||
"customGeoUrl": "URL",
|
||
"customGeoEnabled": "Activado",
|
||
"customGeoLastUpdated": "Última actualización",
|
||
"customGeoExtColumn": "Enrutamiento (ext:…)",
|
||
"customGeoToastUpdateAll": "Todas las fuentes personalizadas se actualizaron",
|
||
"customGeoActions": "Acciones",
|
||
"customGeoEdit": "Editar",
|
||
"customGeoDelete": "Eliminar",
|
||
"customGeoDownload": "Actualizar ahora",
|
||
"customGeoModalAdd": "Añadir geo personalizado",
|
||
"customGeoModalEdit": "Editar geo personalizado",
|
||
"customGeoModalSave": "Guardar",
|
||
"customGeoDeleteConfirm": "¿Eliminar esta fuente geo personalizada?",
|
||
"customGeoRoutingHint": "En reglas de enrutamiento use la columna de valor como ext:archivo.dat:etiqueta (sustituya la etiqueta).",
|
||
"customGeoInvalidId": "Id de recurso no válido",
|
||
"customGeoAliasesError": "No se pudieron cargar los alias geo personalizados",
|
||
"customGeoValidationAlias": "El alias solo puede contener letras minúsculas, dígitos, - y _",
|
||
"customGeoValidationUrl": "La URL debe comenzar con http:// o https://",
|
||
"customGeoAliasPlaceholder": "a-z 0-9 _ -",
|
||
"customGeoAliasLabelSuffix": " (personalizado)",
|
||
"customGeoToastList": "Lista de geo personalizado",
|
||
"customGeoToastAdd": "Añadir geo personalizado",
|
||
"customGeoToastUpdate": "Actualizar geo personalizado",
|
||
"customGeoToastDelete": "Geofile personalizado «{{ .fileName }}» eliminado",
|
||
"customGeoToastDownload": "Geofile «{{ .fileName }}» actualizado",
|
||
"customGeoErrInvalidType": "El tipo debe ser geosite o geoip",
|
||
"customGeoErrAliasRequired": "El alias es obligatorio",
|
||
"customGeoErrAliasPattern": "El alias contiene caracteres no permitidos",
|
||
"customGeoErrAliasReserved": "Este alias está reservado",
|
||
"customGeoErrUrlRequired": "La URL es obligatoria",
|
||
"customGeoErrInvalidUrl": "La URL no es válida",
|
||
"customGeoErrUrlScheme": "La URL debe usar http o https",
|
||
"customGeoErrUrlHost": "El host de la URL no es válido",
|
||
"customGeoErrDuplicateAlias": "Este alias ya se usa para este tipo",
|
||
"customGeoErrNotFound": "Fuente geo personalizada no encontrada",
|
||
"customGeoErrDownload": "Error de descarga",
|
||
"customGeoErrUpdateAllIncomplete": "No se pudieron actualizar una o más fuentes geo personalizadas",
|
||
"customGeoEmpty": "Aún no hay fuentes geo personalizadas — haz clic en Añadir para crear una",
|
||
"dontRefresh": "La instalación está en progreso, por favor no actualices esta página.",
|
||
"logs": "Registros",
|
||
"config": "Configuración",
|
||
"backup": "Сopia de Seguridad",
|
||
"backupTitle": "Copia & Restauración",
|
||
"exportDatabase": "Copia de seguridad",
|
||
"exportDatabaseDesc": "Haz clic para descargar un archivo .db que contiene una copia de seguridad de tu base de datos actual en tu dispositivo.",
|
||
"importDatabase": "Restaurar",
|
||
"importDatabaseDesc": "Haz clic para seleccionar y cargar un archivo .db desde tu dispositivo para restaurar tu base de datos desde una copia de seguridad.",
|
||
"importDatabaseSuccess": "La base de datos se ha importado correctamente",
|
||
"importDatabaseError": "Ocurrió un error al importar la base de datos",
|
||
"readDatabaseError": "Ocurrió un error al leer la base de datos",
|
||
"getDatabaseError": "Ocurrió un error al obtener la base de datos",
|
||
"getConfigError": "Ocurrió un error al obtener el archivo de configuración"
|
||
},
|
||
"inbounds": {
|
||
"title": "Entradas",
|
||
"totalDownUp": "Subidas/Descargas Totales",
|
||
"totalUsage": "Uso Total",
|
||
"inboundCount": "Número de Entradas",
|
||
"operate": "Menú",
|
||
"enable": "Habilitar",
|
||
"remark": "Notas",
|
||
"node": "Nodo",
|
||
"deployTo": "Desplegar en",
|
||
"localPanel": "Panel local",
|
||
"fallbacks": {
|
||
"title": "Fallbacks",
|
||
"help": "Cuando una conexión en este inbound no coincide con ningún cliente, redirígela a otro inbound. Elige un hijo abajo y los campos de enrutamiento (SNI / ALPN / Path / xver) se rellenan automáticamente desde su transporte; la mayoría de las configuraciones no necesitan más ajustes. Cada hijo debe escuchar en 127.0.0.1 con security=none.",
|
||
"empty": "Aún no hay fallbacks",
|
||
"add": "Añadir fallback",
|
||
"pickInbound": "Selecciona un inbound",
|
||
"matchAny": "cualquiera",
|
||
"rederive": "Rellenar desde el hijo",
|
||
"rederived": "Rellenado desde el hijo",
|
||
"editAdvanced": "Editar campos de enrutamiento",
|
||
"hideAdvanced": "Ocultar avanzado",
|
||
"quickAddAll": "Añadir todos los elegibles",
|
||
"quickAdded": "Se añadieron {n} fallback(s)",
|
||
"quickAddedNone": "No hay nuevos inbounds elegibles",
|
||
"routesWhen": "Enruta cuando",
|
||
"defaultCatchAll": "Por defecto — captura cualquier otra cosa"
|
||
},
|
||
"protocol": "Protocolo",
|
||
"port": "Puerto",
|
||
"portMap": "Puertos de Destino",
|
||
"traffic": "Tráfico",
|
||
"details": "Detalles",
|
||
"transportConfig": "Transporte",
|
||
"expireDate": "Fecha de Expiración",
|
||
"createdAt": "Creado",
|
||
"updatedAt": "Actualizado",
|
||
"resetTraffic": "Restablecer Tráfico",
|
||
"addInbound": "Agregar Entrada",
|
||
"generalActions": "Acciones Generales",
|
||
"modifyInbound": "Modificar Entrada",
|
||
"deleteInbound": "Eliminar Entrada",
|
||
"deleteInboundContent": "¿Confirmar eliminación de entrada?",
|
||
"deleteClient": "Eliminar cliente",
|
||
"deleteClientContent": "¿Está seguro de que desea eliminar el cliente?",
|
||
"resetTrafficContent": "¿Confirmar restablecimiento de tráfico?",
|
||
"copyLink": "Copiar Enlace",
|
||
"address": "Dirección",
|
||
"network": "Red",
|
||
"destinationPort": "Puerto de Destino",
|
||
"targetAddress": "Dirección de Destino",
|
||
"monitorDesc": "Dejar en blanco por defecto",
|
||
"meansNoLimit": " = illimitata. (unidad: GB)",
|
||
"totalFlow": "Flujo Total",
|
||
"leaveBlankToNeverExpire": "Dejar en Blanco para Nunca Expirar",
|
||
"noRecommendKeepDefault": "No hay requisitos especiales para mantener la configuración predeterminada",
|
||
"certificatePath": "Ruta Cert",
|
||
"certificateContent": "Datos Cert",
|
||
"publicKey": "Clave Pública",
|
||
"privatekey": "Clave Privada",
|
||
"clickOnQRcode": "Haz clic en el Código QR para Copiar",
|
||
"client": "Cliente",
|
||
"export": "Exportar Enlaces",
|
||
"clone": "Clonar",
|
||
"cloneInbound": "Clonar Entradas",
|
||
"cloneInboundContent": "Se aplicarán todas las configuraciones de esta entrada, excepto el Puerto, la IP de Escucha y los Clientes, al clon.",
|
||
"cloneInboundOk": "Clonar",
|
||
"resetAllTraffic": "Restablecer Tráfico de Todas las Entradas",
|
||
"resetAllTrafficTitle": "Restablecer tráfico de todas las entradas",
|
||
"resetAllTrafficContent": "¿Estás seguro de que deseas restablecer el tráfico de todas las entradas?",
|
||
"resetInboundClientTraffics": "Restablecer Tráfico de Clientes",
|
||
"resetInboundClientTrafficTitle": "Restablecer todo el tráfico de clientes",
|
||
"resetInboundClientTrafficContent": "¿Estás seguro de que deseas restablecer todo el tráfico para los clientes de esta entrada?",
|
||
"resetAllClientTraffics": "Restablecer Tráfico de Todos los Clientes",
|
||
"resetAllClientTrafficTitle": "Restablecer todo el tráfico de clientes",
|
||
"resetAllClientTrafficContent": "¿Estás seguro de que deseas restablecer todo el tráfico para todos los clientes?",
|
||
"delDepletedClients": "Eliminar Clientes Agotados",
|
||
"delDepletedClientsTitle": "Eliminar clientes agotados",
|
||
"delDepletedClientsContent": "¿Estás seguro de que deseas eliminar todos los clientes agotados?",
|
||
"email": "Email",
|
||
"emailDesc": "Por favor proporciona una dirección de correo electrónico única.",
|
||
"IPLimit": "Límite de IP",
|
||
"IPLimitDesc": "Desactiva la entrada si la cantidad supera el valor ingresado (ingresa 0 para desactivar el límite de IP).",
|
||
"IPLimitlog": "Registro de IP",
|
||
"IPLimitlogDesc": "Registro de historial de IPs (antes de habilitar la entrada después de que haya sido desactivada por el límite de IP, debes borrar el registro).",
|
||
"IPLimitlogclear": "Limpiar el Registro",
|
||
"setDefaultCert": "Establecer certificado desde el panel",
|
||
"streamTab": "Stream",
|
||
"securityTab": "Seguridad",
|
||
"sniffingTab": "Sniffing",
|
||
"sniffingMetadataOnly": "Solo metadatos",
|
||
"sniffingRouteOnly": "Solo enrutamiento",
|
||
"sniffingIpsExcluded": "IPs excluidas",
|
||
"sniffingDomainsExcluded": "Dominios excluidos",
|
||
"decryption": "Descifrado",
|
||
"encryption": "Cifrado",
|
||
"vlessAuthX25519": "Autenticación X25519",
|
||
"vlessAuthMlkem768": "Autenticación ML-KEM-768",
|
||
"vlessAuthCustom": "Personalizado",
|
||
"vlessAuthSelected": "Seleccionado: {auth}",
|
||
"advanced": {
|
||
"title": "Secciones JSON del inbound",
|
||
"subtitle": "JSON completo del inbound y editores específicos para settings, sniffing y streamSettings.",
|
||
"all": "Todo",
|
||
"allHelp": "Objeto inbound completo con todos los campos en un solo editor.",
|
||
"settings": "Ajustes",
|
||
"settingsHelp": "Envoltorio del bloque settings de Xray:",
|
||
"sniffing": "Sniffing",
|
||
"sniffingHelp": "Envoltorio del bloque sniffing de Xray:",
|
||
"stream": "Stream",
|
||
"streamHelp": "Envoltorio del bloque stream de Xray:",
|
||
"jsonErrorPrefix": "JSON avanzado"
|
||
},
|
||
"telegramDesc": "Por favor, proporciona el ID de Chat de Telegram. (usa el comando '/id' en el bot) o ({'@'}userinfobot)",
|
||
"subscriptionDesc": "Puedes encontrar tu enlace de suscripción en Detalles, también puedes usar el mismo nombre para varias configuraciones.",
|
||
"info": "Info",
|
||
"same": "misma",
|
||
"inboundData": "Datos de entrada",
|
||
"exportInbound": "Exportación entrante",
|
||
"import": "Importar",
|
||
"importInbound": "Importar un entrante",
|
||
"periodicTrafficResetTitle": "Reset de Tráfico",
|
||
"periodicTrafficResetDesc": "Reiniciar automáticamente el contador de tráfico en intervalos especificados",
|
||
"lastReset": "Último reinicio",
|
||
"periodicTrafficReset": {
|
||
"never": "Nunca",
|
||
"daily": "Diariamente",
|
||
"weekly": "Semanalmente",
|
||
"monthly": "Mensualmente",
|
||
"hourly": "Cada hora"
|
||
},
|
||
"toasts": {
|
||
"obtain": "Recibir",
|
||
"updateSuccess": "La actualización fue exitosa",
|
||
"logCleanSuccess": "El registro ha sido limpiado",
|
||
"inboundsUpdateSuccess": "Entradas actualizadas correctamente",
|
||
"inboundUpdateSuccess": "Entrada actualizada correctamente",
|
||
"inboundCreateSuccess": "Entrada creada correctamente",
|
||
"inboundDeleteSuccess": "Entrada eliminada correctamente",
|
||
"inboundClientAddSuccess": "Cliente(s) de entrada añadido(s)",
|
||
"inboundClientDeleteSuccess": "Cliente de entrada eliminado",
|
||
"inboundClientUpdateSuccess": "Cliente de entrada actualizado",
|
||
"delDepletedClientsSuccess": "Todos los clientes con tráfico agotado fueron eliminados",
|
||
"resetAllClientTrafficSuccess": "Todo el tráfico del cliente ha sido reiniciado",
|
||
"resetAllTrafficSuccess": "Todo el tráfico ha sido reiniciado",
|
||
"resetInboundClientTrafficSuccess": "El tráfico ha sido reiniciado",
|
||
"resetInboundTrafficSuccess": "El tráfico de entrada ha sido reiniciado",
|
||
"trafficGetError": "Error al obtener los tráficos",
|
||
"getNewX25519CertError": "Error al obtener el certificado X25519.",
|
||
"getNewmldsa65Error": "Error al obtener el certificado mldsa65.",
|
||
"getNewVlessEncError": "Error al obtener el certificado VlessEnc."
|
||
},
|
||
"stream": {
|
||
"general": {
|
||
"request": "Pedido",
|
||
"response": "Respuesta",
|
||
"name": "Nombre",
|
||
"value": "Valor"
|
||
},
|
||
"tcp": {
|
||
"version": "Versión",
|
||
"method": "Método",
|
||
"path": "Camino",
|
||
"status": "Estado",
|
||
"statusDescription": "Descripción de la Situación",
|
||
"requestHeader": "Encabezado de solicitud",
|
||
"responseHeader": "Encabezado de respuesta"
|
||
}
|
||
}
|
||
},
|
||
"clients": {
|
||
"add": "Añadir cliente",
|
||
"edit": "Editar cliente",
|
||
"submitAdd": "Añadir cliente",
|
||
"submitEdit": "Guardar cambios",
|
||
"clientCount": "Número de clientes",
|
||
"bulk": "Añadir en lote",
|
||
"copyFromInbound": "Copiar clientes desde inbound",
|
||
"copyToInbound": "Copiar clientes a",
|
||
"copySelected": "Copiar selección",
|
||
"copySource": "Origen",
|
||
"copyEmailPreview": "Vista previa del correo resultante",
|
||
"copySelectSourceFirst": "Selecciona primero un inbound de origen.",
|
||
"copyResult": "Resultado de la copia",
|
||
"copyResultSuccess": "Copiado correctamente",
|
||
"copyResultNone": "Nada que copiar: no hay clientes seleccionados o el origen está vacío",
|
||
"copyResultErrors": "Errores de copia",
|
||
"copyFlowLabel": "Flow para clientes nuevos (VLESS)",
|
||
"copyFlowHint": "Se aplica a todos los clientes copiados. Déjalo vacío para omitir.",
|
||
"selectAll": "Seleccionar todo",
|
||
"clearAll": "Limpiar todo",
|
||
"method": "Método",
|
||
"first": "Primero",
|
||
"last": "Último",
|
||
"ipLog": "Registro de IP",
|
||
"prefix": "Prefijo",
|
||
"postfix": "Sufijo",
|
||
"delayedStart": "Iniciar tras el primer uso",
|
||
"expireDays": "Duración",
|
||
"days": "Día(s)",
|
||
"renew": "Renovación automática",
|
||
"renewDesc": "Renovación automática tras la expiración. (0 = desactivado) (unidad: día)",
|
||
"title": "Clientes",
|
||
"actions": "Acciones",
|
||
"totalGB": "Total enviado/recibido (GB)",
|
||
"expiryTime": "Expiración",
|
||
"addClients": "Añadir clientes",
|
||
"limitIp": "Límite de IP",
|
||
"password": "Contraseña",
|
||
"subId": "ID de suscripción",
|
||
"online": "En línea",
|
||
"email": "Correo",
|
||
"comment": "Comentario",
|
||
"traffic": "Tráfico",
|
||
"offline": "Desconectado",
|
||
"addTitle": "Añadir cliente",
|
||
"qrCode": "Código QR",
|
||
"moreInformation": "Más información",
|
||
"delete": "Eliminar",
|
||
"reset": "Restablecer tráfico",
|
||
"editTitle": "Editar cliente",
|
||
"client": "Cliente",
|
||
"enabled": "Habilitado",
|
||
"remaining": "Restante",
|
||
"duration": "Duración",
|
||
"attachedInbounds": "Inbounds asociados",
|
||
"selectInbound": "Selecciona uno o más inbounds",
|
||
"noSubId": "Este cliente no tiene subId, no hay enlace compartible.",
|
||
"noLinks": "No hay enlaces compartibles — asocia primero este cliente a un inbound con protocolo válido.",
|
||
"link": "Enlace",
|
||
"resetNotPossible": "Asocia primero este cliente a un inbound.",
|
||
"general": "General",
|
||
"resetAllTraffics": "Restablecer tráfico de todos los clientes",
|
||
"resetAllTrafficsTitle": "¿Restablecer tráfico de todos los clientes?",
|
||
"resetAllTrafficsContent": "El contador de subida/bajada de cada cliente vuelve a cero. Las cuotas y la expiración no se modifican. Esta acción no se puede deshacer.",
|
||
"empty": "Aún no hay clientes — añade uno para empezar.",
|
||
"deleteConfirmTitle": "¿Eliminar al cliente {email}?",
|
||
"deleteConfirmContent": "Esto elimina al cliente de cada inbound asociado y descarta su registro de tráfico. No se puede deshacer.",
|
||
"deleteSelected": "Eliminar ({count})",
|
||
"bulkDeleteConfirmTitle": "¿Eliminar {count} clientes?",
|
||
"bulkDeleteConfirmContent": "Cada cliente seleccionado se elimina de los inbounds asociados y se descarta su registro de tráfico. No se puede deshacer.",
|
||
"delDepleted": "Eliminar agotados",
|
||
"delDepletedConfirmTitle": "¿Eliminar clientes agotados?",
|
||
"delDepletedConfirmContent": "Elimina todos los clientes con cuota agotada o expirados. No se puede deshacer.",
|
||
"auth": "Auth",
|
||
"hysteriaAuth": "Auth de Hysteria",
|
||
"uuid": "UUID",
|
||
"flow": "Flow",
|
||
"reverseTag": "Reverse tag",
|
||
"reverseTagPlaceholder": "Reverse tag opcional",
|
||
"telegramId": "ID de usuario de Telegram",
|
||
"telegramIdPlaceholder": "ID numérico de usuario de Telegram (0 = ninguno)",
|
||
"created": "Creado",
|
||
"updated": "Actualizado",
|
||
"ipLimit": "Límite de IP",
|
||
"toasts": {
|
||
"deleted": "Cliente eliminado",
|
||
"trafficReset": "Tráfico restablecido",
|
||
"allTrafficsReset": "Tráfico de todos los clientes restablecido",
|
||
"bulkDeleted": "{count} clientes eliminados",
|
||
"bulkDeletedMixed": "{ok} eliminados, {failed} fallidos",
|
||
"bulkCreated": "{count} clientes creados",
|
||
"bulkCreatedMixed": "{ok} creados, {failed} fallidos",
|
||
"delDepleted": "{count} clientes agotados eliminados"
|
||
}
|
||
},
|
||
"nodes": {
|
||
"title": "Nodos",
|
||
"addNode": "Agregar nodo",
|
||
"editNode": "Editar nodo",
|
||
"totalNodes": "Total de nodos",
|
||
"onlineNodes": "En línea",
|
||
"offlineNodes": "Desconectado",
|
||
"avgLatency": "Latencia media",
|
||
"name": "Nombre",
|
||
"namePlaceholder": "p. ej. de-frankfurt-1",
|
||
"addressPlaceholder": "panel.example.com o 1.2.3.4",
|
||
"remark": "Notas",
|
||
"scheme": "Esquema",
|
||
"address": "Dirección",
|
||
"port": "Puerto",
|
||
"basePath": "Ruta base",
|
||
"apiToken": "Token de API",
|
||
"apiTokenPlaceholder": "Token desde la página de Configuración del panel remoto",
|
||
"apiTokenHint": "El panel remoto expone su token de API en Configuración → Token de API.",
|
||
"regenerate": "Regenerar token",
|
||
"regenerateConfirm": "Regenerar invalida el token actual. Cualquier panel central que lo use perderá el acceso hasta que se actualice. ¿Continuar?",
|
||
"allowPrivateAddress": "Permitir dirección privada",
|
||
"allowPrivateAddressHint": "Habilitar solo para nodos en una red privada o VPN.",
|
||
"enable": "Habilitado",
|
||
"status": "Estado",
|
||
"cpu": "CPU",
|
||
"mem": "Memoria",
|
||
"uptime": "Tiempo activo",
|
||
"latency": "Latencia",
|
||
"lastHeartbeat": "Último latido",
|
||
"xrayVersion": "Versión de Xray",
|
||
"panelVersion": "Versión del panel",
|
||
"actions": "Acciones",
|
||
"probe": "Sondear ahora",
|
||
"testConnection": "Probar conexión",
|
||
"connectionOk": "Conexión correcta ({ms} ms)",
|
||
"connectionFailed": "Conexión fallida",
|
||
"never": "nunca",
|
||
"justNow": "ahora mismo",
|
||
"deleteConfirmTitle": "¿Eliminar el nodo \"{name}\"?",
|
||
"deleteConfirmContent": "Esto detiene la monitorización del nodo. El panel remoto en sí no se ve afectado.",
|
||
"statusValues": {
|
||
"online": "En línea",
|
||
"offline": "Desconectado",
|
||
"unknown": "Desconocido"
|
||
},
|
||
"toasts": {
|
||
"list": "Error al cargar los nodos",
|
||
"obtain": "Error al cargar el nodo",
|
||
"add": "Agregar nodo",
|
||
"update": "Actualizar nodo",
|
||
"delete": "Eliminar nodo",
|
||
"deleted": "Nodo eliminado",
|
||
"test": "Probar conexión",
|
||
"fillRequired": "El nombre, la dirección, el puerto y el token de API son obligatorios",
|
||
"probeFailed": "Sondeo fallido"
|
||
}
|
||
},
|
||
"settings": {
|
||
"title": "Configuraciones",
|
||
"save": "Guardar",
|
||
"infoDesc": "Cada cambio realizado aquí debe ser guardado. Por favor, reinicie el panel para aplicar los cambios.",
|
||
"restartPanel": "Reiniciar Panel",
|
||
"restartPanelDesc": "¿Está seguro de que desea reiniciar el panel? Haga clic en Aceptar para reiniciar después de 3 segundos. Si no puede acceder al panel después de reiniciar, por favor, consulte la información de registro del panel en el servidor.",
|
||
"restartPanelSuccess": "El panel se reinició correctamente",
|
||
"actions": "Acciones",
|
||
"resetDefaultConfig": "Restablecer a Configuración Predeterminada",
|
||
"panelSettings": "Configuraciones del Panel",
|
||
"securitySettings": "Configuraciones de Seguridad",
|
||
"TGBotSettings": "Configuraciones de Bot de Telegram",
|
||
"panelListeningIP": "IP de Escucha del Panel",
|
||
"panelListeningIPDesc": "Dejar en blanco por defecto para monitorear todas las IPs.",
|
||
"panelListeningDomain": "Dominio de Escucha del Panel",
|
||
"panelListeningDomainDesc": "Dejar en blanco por defecto para monitorear todos los dominios e IPs.",
|
||
"panelPort": "Puerto del Panel",
|
||
"panelPortDesc": "El puerto utilizado para mostrar este panel.",
|
||
"publicKeyPath": "Ruta del Archivo de Clave Pública del Certificado del Panel",
|
||
"publicKeyPathDesc": "Complete con una ruta absoluta que comience con.",
|
||
"privateKeyPath": "Ruta del Archivo de Clave Privada del Certificado del Panel",
|
||
"privateKeyPathDesc": "Complete con una ruta absoluta que comience con.",
|
||
"panelUrlPath": "Ruta Raíz de la URL del Panel",
|
||
"panelUrlPathDesc": "Debe empezar con '/' y terminar con.",
|
||
"pageSize": "Tamaño de paginación",
|
||
"pageSizeDesc": "Defina el tamaño de página para la tabla de entradas. Establezca 0 para desactivar",
|
||
"remarkModel": "Modelo de observación y carácter de separación",
|
||
"datepicker": "selector de fechas",
|
||
"datepickerPlaceholder": "Seleccionar fecha",
|
||
"datepickerDescription": "El tipo de calendario selector especifica la fecha de vencimiento",
|
||
"sampleRemark": "Observación de muestra",
|
||
"oldUsername": "Nombre de Usuario Actual",
|
||
"currentPassword": "Contraseña Actual",
|
||
"newUsername": "Nuevo Nombre de Usuario",
|
||
"newPassword": "Nueva Contraseña",
|
||
"telegramBotEnable": "Habilitar bot de Telegram",
|
||
"telegramBotEnableDesc": "Conéctese a las funciones de este panel a través del bot de Telegram.",
|
||
"telegramToken": "Token de Telegram",
|
||
"telegramTokenDesc": "Debe obtener el token del administrador de bots de Telegram {'@'}botfather.",
|
||
"telegramProxy": "Socks5 Proxy",
|
||
"telegramProxyDesc": "Si necesita el proxy Socks5 para conectarse a Telegram. Ajuste su configuración según la guía.",
|
||
"telegramAPIServer": "API Server de Telegram",
|
||
"telegramAPIServerDesc": "El servidor API de Telegram a utilizar. Déjelo en blanco para utilizar el servidor predeterminado.",
|
||
"telegramChatId": "IDs de Chat de Telegram para Administradores",
|
||
"telegramChatIdDesc": "IDs de Chat múltiples separados por comas. Use {'@'}userinfobot o use el comando '/id' en el bot para obtener sus IDs de Chat.",
|
||
"telegramNotifyTime": "Hora de Notificación del Bot de Telegram",
|
||
"telegramNotifyTimeDesc": "Usar el formato de tiempo de Crontab.",
|
||
"tgNotifyBackup": "Respaldo de Base de Datos",
|
||
"tgNotifyBackupDesc": "Incluir archivo de respaldo de base de datos con notificación de informe.",
|
||
"tgNotifyLogin": "Notificación de Inicio de Sesión",
|
||
"tgNotifyLoginDesc": "Muestra el nombre de usuario, dirección IP y hora cuando alguien intenta iniciar sesión en su panel.",
|
||
"sessionMaxAge": "Edad Máxima de Sesión",
|
||
"sessionMaxAgeDesc": "La duración de una sesión de inicio de sesión (unidad: minutos).",
|
||
"expireTimeDiff": "Umbral de Expiración para Notificación",
|
||
"expireTimeDiffDesc": "Reciba notificaciones sobre la expiración de la cuenta antes del umbral (unidad: días).",
|
||
"trafficDiff": "Umbral de Tráfico para Notificación",
|
||
"trafficDiffDesc": "Reciba notificaciones sobre el agotamiento del tráfico antes de alcanzar el umbral (unidad: GB).",
|
||
"tgNotifyCpu": "Umbral de Alerta de Porcentaje de CPU",
|
||
"tgNotifyCpuDesc": "Reciba notificaciones si el uso de la CPU supera este umbral (unidad: %).",
|
||
"timeZone": "Zona Horaria",
|
||
"timeZoneDesc": "Las tareas programadas se ejecutan de acuerdo con la hora en esta zona horaria.",
|
||
"subSettings": "Suscripción",
|
||
"subEnable": "Habilitar Servicio",
|
||
"subEnableDesc": "Función de suscripción con configuración separada.",
|
||
"subJsonEnable": "Habilitar/Deshabilitar el endpoint de suscripción JSON de forma independiente.",
|
||
"subTitle": "Título de la Suscripción",
|
||
"subTitleDesc": "Título mostrado en el cliente VPN",
|
||
"subSupportUrl": "URL de soporte",
|
||
"subSupportUrlDesc": "Enlace de soporte técnico mostrado en el cliente VPN",
|
||
"subProfileUrl": "URL del perfil",
|
||
"subProfileUrlDesc": "Un enlace a tu sitio web mostrado en el cliente VPN",
|
||
"subAnnounce": "Anuncio",
|
||
"subAnnounceDesc": "El texto del anuncio mostrado en el cliente VPN",
|
||
"subEnableRouting": "Habilitar enrutamiento",
|
||
"subEnableRoutingDesc": "Configuración global para habilitar el enrutamiento en el cliente VPN. (Solo para Happ)",
|
||
"subRoutingRules": "Reglas de enrutamiento",
|
||
"subRoutingRulesDesc": "Reglas de enrutamiento globales para el cliente VPN. (Solo para Happ)",
|
||
"subListen": "Listening IP",
|
||
"subListenDesc": "Dejar en blanco por defecto para monitorear todas las IPs.",
|
||
"subPort": "Puerto de Suscripción",
|
||
"subPortDesc": "El número de puerto para el servicio de suscripción debe estar sin usar en el servidor.",
|
||
"subCertPath": "Ruta del Archivo de Clave Pública del Certificado de Suscripción",
|
||
"subCertPathDesc": "Complete con una ruta absoluta que comience con '/'",
|
||
"subKeyPath": "Ruta del Archivo de Clave Privada del Certificado de Suscripción",
|
||
"subKeyPathDesc": "Complete con una ruta absoluta que comience con '/'",
|
||
"subPath": "Ruta Raíz de la URL de Suscripción",
|
||
"subPathDesc": "Debe empezar con '/' y terminar con '/'",
|
||
"subDomain": "Dominio de Escucha",
|
||
"subDomainDesc": "Dejar en blanco por defecto para monitorear todos los dominios e IPs.",
|
||
"subUpdates": "Intervalos de Actualización de Suscripción",
|
||
"subUpdatesDesc": "Horas de intervalo entre actualizaciones en la aplicación del cliente.",
|
||
"subEncrypt": "Encriptar configuraciones",
|
||
"subEncryptDesc": "Encriptar las configuraciones devueltas en la suscripción.",
|
||
"subShowInfo": "Mostrar información de uso",
|
||
"subShowInfoDesc": "Mostrar tráfico restante y fecha después del nombre de configuración.",
|
||
"subEmailInRemark": "Incluir Email en el nombre",
|
||
"subEmailInRemarkDesc": "Incluir el correo del cliente en el nombre del perfil de suscripción.",
|
||
"subURI": "URI de proxy inverso",
|
||
"subURIDesc": "Cambiar el URI base de la URL de suscripción para usar detrás de los servidores proxy",
|
||
"externalTrafficInformEnable": "Informe de tráfico externo",
|
||
"externalTrafficInformEnableDesc": "Informar a la API externa sobre cada actualización de tráfico.",
|
||
"externalTrafficInformURI": "URI de información de tráfico externo",
|
||
"externalTrafficInformURIDesc": "Las actualizaciones de tráfico se envían a este URI.",
|
||
"restartXrayOnClientDisable": "Reiniciar Xray tras desactivación automática",
|
||
"restartXrayOnClientDisableDesc": "Cuando un cliente se desactive automáticamente por vencimiento o límite de tráfico, reiniciar Xray.",
|
||
"fragment": "Fragmentación",
|
||
"fragmentDesc": "Habilitar la fragmentación para el paquete de saludo de TLS",
|
||
"fragmentSett": "Configuración de Fragmentación",
|
||
"noisesDesc": "Activar Sonidos",
|
||
"noisesSett": "Configuración de Sonidos",
|
||
"mux": "Mux",
|
||
"muxDesc": "Transmite múltiples flujos de datos independientes dentro de un flujo de datos establecido.",
|
||
"muxSett": "Configuración Mux",
|
||
"direct": "Conexión Directa",
|
||
"directDesc": "Establece conexiones directas con dominios o rangos de IP de un país específico.",
|
||
"notifications": "Notificaciones",
|
||
"certs": "Certificados",
|
||
"externalTraffic": "Tráfico Externo",
|
||
"dateAndTime": "Fecha y Hora",
|
||
"proxyAndServer": "Proxy y Servidor",
|
||
"intervals": "Intervalos",
|
||
"information": "Información",
|
||
"language": "Idioma",
|
||
"telegramBotLanguage": "Idioma del Bot de Telegram",
|
||
"security": {
|
||
"admin": "Credenciales de administrador",
|
||
"twoFactor": "Autenticación de dos factores",
|
||
"twoFactorEnable": "Habilitar 2FA",
|
||
"twoFactorEnableDesc": "Añade una capa adicional de autenticación para mayor seguridad.",
|
||
"twoFactorModalSetTitle": "Activar autenticación de dos factores",
|
||
"twoFactorModalDeleteTitle": "Desactivar autenticación de dos factores",
|
||
"twoFactorModalSteps": "Para configurar la autenticación de dos factores, sigue estos pasos:",
|
||
"twoFactorModalFirstStep": "1. Escanea este código QR en la aplicación de autenticación o copia el token cerca del código QR y pégalo en la aplicación",
|
||
"twoFactorModalSecondStep": "2. Ingresa el código de la aplicación",
|
||
"twoFactorModalRemoveStep": "Ingresa el código de la aplicación para eliminar la autenticación de dos factores.",
|
||
"twoFactorModalChangeCredentialsTitle": "Cambiar credenciales",
|
||
"twoFactorModalChangeCredentialsStep": "Ingrese el código de la aplicación para cambiar las credenciales del administrador.",
|
||
"twoFactorModalSetSuccess": "La autenticación de dos factores se ha establecido con éxito",
|
||
"twoFactorModalDeleteSuccess": "La autenticación de dos factores se ha eliminado con éxito",
|
||
"twoFactorModalError": "Código incorrecto",
|
||
"show": "Mostrar",
|
||
"hide": "Ocultar",
|
||
"apiTokenNew": "Nuevo token",
|
||
"apiTokenName": "Nombre",
|
||
"apiTokenNamePlaceholder": "por ejemplo central-panel-a",
|
||
"apiTokenNameRequired": "El nombre es obligatorio",
|
||
"apiTokenEmpty": "Aún no hay tokens — crea uno para autenticar bots o paneles remotos.",
|
||
"apiTokenDeleteWarning": "Cualquier cliente que use este token dejará de autenticarse inmediatamente."
|
||
},
|
||
"toasts": {
|
||
"modifySettings": "Los parámetros han sido modificados.",
|
||
"getSettings": "Ocurrió un error al obtener los parámetros.",
|
||
"modifyUserError": "Ocurrió un error al cambiar las credenciales del administrador.",
|
||
"modifyUser": "Has cambiado exitosamente las credenciales del administrador.",
|
||
"originalUserPassIncorrect": "Nombre de usuario o contraseña original incorrectos",
|
||
"userPassMustBeNotEmpty": "El nuevo nombre de usuario y la nueva contraseña no pueden estar vacíos",
|
||
"getOutboundTrafficError": "Error al obtener el tráfico saliente",
|
||
"resetOutboundTrafficError": "Error al reiniciar el tráfico saliente"
|
||
}
|
||
},
|
||
"xray": {
|
||
"title": "Xray Configuración",
|
||
"save": "Guardar configuración",
|
||
"restart": "Reiniciar Xray",
|
||
"restartSuccess": "Xray se ha reiniciado correctamente",
|
||
"stopSuccess": "Xray se ha detenido correctamente",
|
||
"restartError": "Ocurrió un error al reiniciar Xray.",
|
||
"stopError": "Ocurrió un error al detener Xray.",
|
||
"basicTemplate": "Perfil Básico",
|
||
"advancedTemplate": "Perfil Avanzado",
|
||
"generalConfigs": "Configuraciones Generales",
|
||
"generalConfigsDesc": "Estas opciones proporcionarán ajustes generales.",
|
||
"logConfigs": "Registro",
|
||
"logConfigsDesc": "Los registros pueden afectar la eficiencia de su servidor. Se recomienda habilitarlos sabiamente solo en caso de sus necesidades.",
|
||
"blockConfigsDesc": "Estas opciones evitarán que los usuarios se conecten a protocolos y sitios web específicos.",
|
||
"basicRouting": "Enrutamiento Básico",
|
||
"blockConnectionsConfigsDesc": "Estas opciones bloquearán el tráfico según el país solicitado específico.",
|
||
"directConnectionsConfigsDesc": "Una conexión directa asegura que el tráfico específico no sea enrutado a través de otro servidor.",
|
||
"blockips": "Bloquear IPs",
|
||
"blockdomains": "Bloquear Dominios",
|
||
"directips": "IPs Directas",
|
||
"directdomains": "Dominios Directos",
|
||
"ipv4Routing": "Enrutamiento IPv4",
|
||
"ipv4RoutingDesc": "Estas opciones solo enrutarán a los dominios objetivo a través de IPv4.",
|
||
"warpRouting": "Enrutamiento WARP",
|
||
"warpRoutingDesc": "Precaución: Antes de usar estas opciones, instale WARP en modo de proxy socks5 en su servidor siguiendo los pasos en el GitHub del panel. WARP enrutará el tráfico a los sitios web a través de los servidores de Cloudflare.",
|
||
"nordRouting": "Enrutamiento NordVPN",
|
||
"nordRoutingDesc": "Estas opciones enrutarán el tráfico basado en un destino específico a través de NordVPN.",
|
||
"Template": "Plantilla de Configuración de Xray",
|
||
"TemplateDesc": "Genera el archivo de configuración final de Xray basado en esta plantilla.",
|
||
"FreedomStrategy": "Configurar Estrategia para el Protocolo Freedom",
|
||
"FreedomStrategyDesc": "Establece la estrategia de salida de la red en el Protocolo Freedom.",
|
||
"RoutingStrategy": "Configurar Estrategia de Enrutamiento de Dominios",
|
||
"RoutingStrategyDesc": "Establece la estrategia general de enrutamiento para la resolución de DNS.",
|
||
"outboundTestUrl": "URL de prueba de outbound",
|
||
"outboundTestUrlDesc": "URL usada al probar la conectividad del outbound",
|
||
"Torrent": "Prohibir Uso de BitTorrent",
|
||
"Inbounds": "Entrante",
|
||
"InboundsDesc": "Cambia la plantilla de configuración para aceptar clientes específicos.",
|
||
"Outbounds": "Salidas",
|
||
"Balancers": "Equilibradores",
|
||
"OutboundsDesc": "Cambia la plantilla de configuración para definir formas de salida para este servidor.",
|
||
"Routings": "Reglas de enrutamiento",
|
||
"RoutingsDesc": "¡La prioridad de cada regla es importante!",
|
||
"completeTemplate": "Todos",
|
||
"logLevel": "Nivel de registro",
|
||
"logLevelDesc": "El nivel de registro para registros de errores, que indica la información que debe registrarse.",
|
||
"accessLog": "Registro de acceso",
|
||
"accessLogDesc": "La ruta del archivo para el registro de acceso. El valor especial 'ninguno' deshabilita los registros de acceso",
|
||
"errorLog": "Registro de Errores",
|
||
"errorLogDesc": "La ruta del archivo para el registro de errores. El valor especial 'none' desactiva los registros de errores.",
|
||
"dnsLog": "Registro DNS",
|
||
"dnsLogDesc": "Si habilitar los registros de consulta DNS",
|
||
"maskAddress": "Enmascarar Dirección",
|
||
"maskAddressDesc": "Máscara de dirección IP, cuando se habilita, reemplazará automáticamente la dirección IP que aparece en el registro.",
|
||
"statistics": "Estadísticas",
|
||
"statsInboundUplink": "Estadísticas de Subida de Entrada",
|
||
"statsInboundUplinkDesc": "Habilita la recopilación de estadísticas para el tráfico ascendente de todos los proxies de entrada.",
|
||
"statsInboundDownlink": "Estadísticas de Bajada de Entrada",
|
||
"statsInboundDownlinkDesc": "Habilita la recopilación de estadísticas para el tráfico descendente de todos los proxies de entrada.",
|
||
"statsOutboundUplink": "Estadísticas de Subida de Salida",
|
||
"statsOutboundUplinkDesc": "Habilita la recopilación de estadísticas para el tráfico ascendente de todos los proxies de salida.",
|
||
"statsOutboundDownlink": "Estadísticas de Bajada de Salida",
|
||
"statsOutboundDownlinkDesc": "Habilita la recopilación de estadísticas para el tráfico descendente de todos los proxies de salida.",
|
||
"rules": {
|
||
"first": "Primero",
|
||
"last": "Último",
|
||
"up": "Arriba",
|
||
"down": "Abajo",
|
||
"source": "Fuente",
|
||
"dest": "Destino",
|
||
"inbound": "Entrante",
|
||
"outbound": "Saliente",
|
||
"balancer": "Equilibrador",
|
||
"info": "Información",
|
||
"add": "Agregar Regla",
|
||
"edit": "Editar Regla",
|
||
"useComma": "Elementos separados por comas"
|
||
},
|
||
"outbound": {
|
||
"addOutbound": "Agregar salida",
|
||
"addReverse": "Agregar reverso",
|
||
"editOutbound": "Editar salida",
|
||
"editReverse": "Editar reverso",
|
||
"reverseTag": "Etiqueta Reverso",
|
||
"reverseTagDesc": "Etiqueta de salida del proxy inverso simple VLESS. Dejar vacío para deshabilitar. Cuando se establece, las conexiones de este cliente pueden usarse como túnel de proxy inverso.",
|
||
"reverseTagPlaceholder": "etiqueta de salida (vacío para deshabilitar)",
|
||
"tag": "Etiqueta",
|
||
"tagDesc": "etiqueta única",
|
||
"address": "Dirección",
|
||
"reverse": "Reverso",
|
||
"domain": "Dominio",
|
||
"type": "Tipo",
|
||
"bridge": "puente",
|
||
"portal": "portal",
|
||
"link": "Enlace",
|
||
"intercon": "Interconexión",
|
||
"settings": "Configuración",
|
||
"accountInfo": "Información de la Cuenta",
|
||
"outboundStatus": "Estado de Salida",
|
||
"sendThrough": "Enviar a través de",
|
||
"test": "Probar",
|
||
"testResult": "Resultado de la prueba",
|
||
"testing": "Probando conexión...",
|
||
"testSuccess": "Prueba exitosa",
|
||
"testFailed": "Prueba fallida",
|
||
"testError": "Error al probar la salida",
|
||
"nordvpn": "NordVPN",
|
||
"accessToken": "Token de acceso",
|
||
"country": "País",
|
||
"server": "Servidor",
|
||
"city": "Ciudad",
|
||
"allCities": "Todas las ciudades",
|
||
"privateKey": "Clave privada",
|
||
"load": "Carga"
|
||
},
|
||
"balancer": {
|
||
"addBalancer": "Agregar equilibrador",
|
||
"editBalancer": "Editar balanceador",
|
||
"balancerStrategy": "Estrategia",
|
||
"balancerSelectors": "Selectores",
|
||
"tag": "Etiqueta",
|
||
"tagDesc": "etiqueta única",
|
||
"balancerDesc": "No es posible utilizar balancerTag y outboundTag al mismo tiempo. Si se utilizan al mismo tiempo, sólo funcionará outboundTag."
|
||
},
|
||
"wireguard": {
|
||
"secretKey": "Llave secreta",
|
||
"publicKey": "Llave pública",
|
||
"allowedIPs": "IP permitidas",
|
||
"endpoint": "Punto final",
|
||
"psk": "Clave precompartida",
|
||
"domainStrategy": "Estrategia de dominio"
|
||
},
|
||
"tun": {
|
||
"nameDesc": "El nombre de la interfaz TUN. El valor predeterminado es 'xray0'",
|
||
"mtuDesc": "Unidad Máxima de Transmisión. El tamaño máximo de los paquetes de datos. El valor predeterminado es 1500",
|
||
"userLevel": "Nivel de Usuario",
|
||
"userLevelDesc": "Todas las conexiones realizadas a través de este entrada utilizarán este nivel de usuario. El valor predeterminado es 0"
|
||
},
|
||
"dns": {
|
||
"enable": "Habilitar DNS",
|
||
"enableDesc": "Habilitar servidor DNS incorporado",
|
||
"tag": "Etiqueta de Entrada DNS",
|
||
"tagDesc": "Esta etiqueta estará disponible como una etiqueta de entrada en las reglas de enrutamiento.",
|
||
"clientIp": "IP del cliente",
|
||
"clientIpDesc": "Se utiliza para notificar al servidor la ubicación IP especificada durante las consultas DNS",
|
||
"disableCache": "Desactivar caché",
|
||
"disableCacheDesc": "Desactiva el almacenamiento en caché de DNS",
|
||
"disableFallback": "Desactivar respaldo",
|
||
"disableFallbackDesc": "Desactiva las consultas DNS de respaldo",
|
||
"disableFallbackIfMatch": "Desactivar respaldo si coincide",
|
||
"disableFallbackIfMatchDesc": "Desactiva las consultas DNS de respaldo cuando se acierta en la lista de dominios coincidentes del servidor DNS",
|
||
"enableParallelQuery": "Habilitar consulta paralela",
|
||
"enableParallelQueryDesc": "Habilitar consultas DNS paralelas a múltiples servidores para una resolución más rápida",
|
||
"strategy": "Estrategia de Consulta",
|
||
"strategyDesc": "Estrategia general para resolver nombres de dominio",
|
||
"add": "Agregar Servidor",
|
||
"edit": "Editar Servidor",
|
||
"domains": "Dominios",
|
||
"expectIPs": "IPs esperadas",
|
||
"unexpectIPs": "IPs inesperadas",
|
||
"useSystemHosts": "Usar Hosts del sistema",
|
||
"useSystemHostsDesc": "Usar el archivo hosts de un sistema instalado",
|
||
"serveStale": "Servir caducados",
|
||
"serveStaleDesc": "Devolver resultados caducados de la caché mientras se actualiza en segundo plano",
|
||
"serveExpiredTTL": "TTL de caducados",
|
||
"serveExpiredTTLDesc": "Validez (segundos) de las entradas caducadas en la caché; 0 = nunca caduca",
|
||
"timeoutMs": "Tiempo de espera (ms)",
|
||
"skipFallback": "Omitir respaldo",
|
||
"finalQuery": "Consulta final",
|
||
"hosts": "Hosts",
|
||
"hostsAdd": "Agregar Host",
|
||
"hostsEmpty": "No hay Hosts definidos",
|
||
"hostsDomain": "Dominio (ej. domain:example.com)",
|
||
"hostsValues": "IP o dominio — escribe y presiona Enter",
|
||
"usePreset": "Usar plantilla",
|
||
"dnsPresetTitle": "Plantillas DNS",
|
||
"dnsPresetFamily": "Familiar",
|
||
"clearAll": "Eliminar todos",
|
||
"clearAllTitle": "¿Eliminar todos los servidores DNS?",
|
||
"clearAllConfirm": "Esto eliminará todos los servidores DNS de la lista. No se puede deshacer."
|
||
},
|
||
"fakedns": {
|
||
"add": "Agregar DNS Falso",
|
||
"edit": "Editar DNS Falso",
|
||
"ipPool": "Subred del grupo de IP",
|
||
"poolSize": "Tamaño del grupo"
|
||
}
|
||
}
|
||
},
|
||
"tgbot": {
|
||
"keyboardClosed": "❌ Teclado cerrado!",
|
||
"noResult": "❗ ¡Sin resultados!",
|
||
"noQuery": "❌ ¡Consulta no encontrada! ¡Por favor, use el comando nuevamente!",
|
||
"wentWrong": "❌ ¡Algo salió mal!",
|
||
"noIpRecord": "❗ ¡No hay registro de IP!",
|
||
"noInbounds": "❗ ¡No se encontraron entradas!",
|
||
"unlimited": "♾ Ilimitado (Restablecer)",
|
||
"add": "Añadir",
|
||
"month": "Mes",
|
||
"months": "Meses",
|
||
"day": "Día",
|
||
"days": "Días",
|
||
"hours": "Horas",
|
||
"minutes": "Minutos",
|
||
"unknown": "Desconocido",
|
||
"inbounds": "Entradas",
|
||
"clients": "Clientes",
|
||
"offline": "🔴 Desconectado",
|
||
"online": "🟢 En línea",
|
||
"commands": {
|
||
"unknown": "❗ Comando desconocido",
|
||
"pleaseChoose": "👇 Por favor elige:\r\n",
|
||
"help": "🤖 ¡Bienvenido a este bot! Está diseñado para ofrecerte datos específicos del servidor y te permite hacer modificaciones según sea necesario.\r\n\r\n",
|
||
"start": "👋 Hola <i>{{ .Firstname }}</i>.\r\n",
|
||
"welcome": "🤖 Bienvenido al bot de gestión de <b>{{ .Hostname }}</b>.\r\n",
|
||
"status": "✅ ¡El bot está bien!",
|
||
"usage": "❗ ¡Por favor proporciona un texto para buscar!",
|
||
"getID": "🆔 Tu ID: <code>{{ .ID }}</code>",
|
||
"helpAdminCommands": "Para reiniciar Xray Core:\r\n<code>/restart</code>\r\n\r\nPara buscar un correo electrónico de cliente:\r\n<code>/usage [Correo electrónico]</code>\r\n\r\nPara buscar entradas (con estadísticas de cliente):\r\n<code>/inbound [Observación]</code>\r\n\r\nID de Chat de Telegram:\r\n<code>/id</code>",
|
||
"helpClientCommands": "Para buscar estadísticas, utiliza el siguiente comando:\r\n<code>/usage [Correo electrónico]</code>\r\n\r\nID de Chat de Telegram:\r\n<code>/id</code>",
|
||
"restartUsage": "\r\n\r\n<code>/restart</code>",
|
||
"restartSuccess": "✅ ¡Operación exitosa!",
|
||
"restartFailed": "❗ Error en la operación.\r\n\r\n<code>Error: {{ .Error }}</code>.",
|
||
"xrayNotRunning": "❗ Xray Core no está en ejecución.",
|
||
"startDesc": "Mostrar el menú principal",
|
||
"helpDesc": "Ayuda del bot",
|
||
"statusDesc": "Comprobar el estado del bot",
|
||
"idDesc": "Mostrar tu ID de Telegram"
|
||
},
|
||
"messages": {
|
||
"cpuThreshold": "🔴 El uso de CPU {{ .Percent }}% es mayor que el umbral {{ .Threshold }}%",
|
||
"selectUserFailed": "❌ ¡Error al seleccionar usuario!",
|
||
"userSaved": "✅ Usuario de Telegram guardado.",
|
||
"loginSuccess": "✅ Has iniciado sesión en el panel con éxito.\r\n",
|
||
"loginFailed": "❗️ Falló el inicio de sesión en el panel.\r\n",
|
||
"2faFailed": "Error de 2FA",
|
||
"report": "🕰 Informes programados: {{ .RunTime }}\r\n",
|
||
"datetime": "⏰ Fecha y Hora: {{ .DateTime }}\r\n",
|
||
"hostname": "💻 Nombre del Host: {{ .Hostname }}\r\n",
|
||
"version": "🚀 Versión de X-UI: {{ .Version }}\r\n",
|
||
"xrayVersion": "📡 Versión de Xray: {{ .XrayVersion }}\r\n",
|
||
"ipv6": "🌐 IPv6: {{ .IPv6 }}\r\n",
|
||
"ipv4": "🌐 IPv4: {{ .IPv4 }}\r\n",
|
||
"ip": "🌐 IP: {{ .IP }}\r\n",
|
||
"ips": "🔢 IPs:\r\n{{ .IPs }}\r\n",
|
||
"serverUpTime": "⏳ Tiempo de actividad del servidor: {{ .UpTime }} {{ .Unit }}\r\n",
|
||
"serverLoad": "📈 Carga del servidor: {{ .Load1 }}, {{ .Load2 }}, {{ .Load3 }}\r\n",
|
||
"serverMemory": "📋 Memoria del servidor: {{ .Current }}/{{ .Total }}\r\n",
|
||
"tcpCount": "🔹 Conteo de TCP: {{ .Count }}\r\n",
|
||
"udpCount": "🔸 Conteo de UDP: {{ .Count }}\r\n",
|
||
"traffic": "🚦 Tráfico: {{ .Total }} (↑{{ .Upload }},↓{{ .Download }})\r\n",
|
||
"xrayStatus": "ℹ️ Estado de Xray: {{ .State }}\r\n",
|
||
"username": "👤 Nombre de usuario: {{ .Username }}\r\n",
|
||
"reason": "❗️ Motivo: {{ .Reason }}\r\n",
|
||
"time": "⏰ Hora: {{ .Time }}\r\n",
|
||
"inbound": "📍 Inbound: {{ .Remark }}\r\n",
|
||
"port": "🔌 Puerto: {{ .Port }}\r\n",
|
||
"expire": "📅 Fecha de Vencimiento: {{ .Time }}\r\n",
|
||
"expireIn": "📅 Vence en: {{ .Time }}\r\n",
|
||
"active": "💡 Activo: {{ .Enable }}\r\n",
|
||
"enabled": "🚨 Habilitado: {{ .Enable }}\r\n",
|
||
"online": "🌐 Estado de conexión: {{ .Status }}\r\n",
|
||
"lastOnline": "🔙 Última conexión: {{ .Time }}\r\n",
|
||
"email": "📧 Email: {{ .Email }}\r\n",
|
||
"upload": "🔼 Subida: ↑{{ .Upload }}\r\n",
|
||
"download": "🔽 Bajada: ↓{{ .Download }}\r\n",
|
||
"total": "📊 Total: ↑↓{{ .UpDown }} / {{ .Total }}\r\n",
|
||
"TGUser": "👤 Usuario de Telegram: {{ .TelegramID }}\r\n",
|
||
"exhaustedMsg": "🚨 Agotado {{ .Type }}:\r\n",
|
||
"exhaustedCount": "🚨 Cantidad de Agotados {{ .Type }}:\r\n",
|
||
"onlinesCount": "🌐 Clientes en línea: {{ .Count }}\r\n",
|
||
"disabled": "🛑 Desactivado: {{ .Disabled }}\r\n",
|
||
"depleteSoon": "🔜 Se agotará pronto: {{ .Deplete }}\r\n\r\n",
|
||
"backupTime": "🗄 Hora de la Copia de Seguridad: {{ .Time }}\r\n",
|
||
"refreshedOn": "\r\n📋🔄 Actualizado en: {{ .Time }}\r\n\r\n",
|
||
"yes": "✅ Sí",
|
||
"no": "❌ No",
|
||
"received_id": "🔑📥 ID actualizado.",
|
||
"received_password": "🔑📥 Contraseña actualizada.",
|
||
"received_email": "📧📥 Correo electrónico actualizado.",
|
||
"received_comment": "💬📥 Comentario actualizado.",
|
||
"id_prompt": "🔑 ID predeterminado: {{ .ClientId }}\n\nIntroduce tu ID.",
|
||
"pass_prompt": "🔑 Contraseña predeterminada: {{ .ClientPassword }}\n\nIntroduce tu contraseña.",
|
||
"email_prompt": "📧 Correo electrónico predeterminado: {{ .ClientEmail }}\n\nIntroduce tu correo electrónico.",
|
||
"comment_prompt": "💬 Comentario predeterminado: {{ .ClientComment }}\n\nIntroduce tu comentario.",
|
||
"inbound_client_data_id": "🔄 Entrada: {{ .InboundRemark }}\n\n🔑 ID: {{ .ClientId }}\n📧 Correo: {{ .ClientEmail }}\n📊 Tráfico: {{ .ClientTraffic }}\n📅 Fecha de expiración: {{ .ClientExp }}\n🌐 Límite de IP: {{ .IpLimit }}\n💬 Comentario: {{ .ClientComment }}\n\n¡Ahora puedes agregar al cliente a la entrada!",
|
||
"inbound_client_data_pass": "🔄 Entrada: {{ .InboundRemark }}\n\n🔑 Contraseña: {{ .ClientPass }}\n📧 Correo: {{ .ClientEmail }}\n📊 Tráfico: {{ .ClientTraffic }}\n📅 Fecha de expiración: {{ .ClientExp }}\n🌐 Límite de IP: {{ .IpLimit }}\n💬 Comentario: {{ .ClientComment }}\n\n¡Ahora puedes agregar al cliente a la entrada!",
|
||
"cancel": "❌ ¡Proceso cancelado! \n\nPuedes /start de nuevo en cualquier momento. 🔄",
|
||
"error_add_client": "⚠️ Error:\n\n {{ .error }}",
|
||
"using_default_value": "Está bien, me quedaré con el valor predeterminado. 😊",
|
||
"incorrect_input": "Tu entrada no es válida.\nLas frases deben ser continuas sin espacios.\nEjemplo correcto: aaaaaa\nEjemplo incorrecto: aaa aaa 🚫",
|
||
"AreYouSure": "¿Estás seguro? 🤔",
|
||
"SuccessResetTraffic": "📧 Correo: {{ .ClientEmail }}\n🏁 Resultado: ✅ Éxito",
|
||
"FailedResetTraffic": "📧 Correo: {{ .ClientEmail }}\n🏁 Resultado: ❌ Fallido \n\n🛠️ Error: [ {{ .ErrorMessage }} ]",
|
||
"FinishProcess": "🔚 Proceso de reinicio de tráfico finalizado para todos los clientes."
|
||
},
|
||
"buttons": {
|
||
"closeKeyboard": "❌ Cerrar Teclado",
|
||
"cancel": "❌ Cancelar",
|
||
"cancelReset": "❌ Cancelar Reinicio",
|
||
"cancelIpLimit": "❌ Cancelar Límite de IP",
|
||
"confirmResetTraffic": "✅ ¿Confirmar Reinicio de Tráfico?",
|
||
"confirmClearIps": "✅ ¿Confirmar Limpiar IPs?",
|
||
"confirmRemoveTGUser": "✅ ¿Confirmar Eliminar Usuario de Telegram?",
|
||
"confirmToggle": "✅ ¿Confirmar habilitar/deshabilitar usuario?",
|
||
"dbBackup": "Obtener Copia de Seguridad de BD",
|
||
"serverUsage": "Uso del Servidor",
|
||
"getInbounds": "Obtener Entradas",
|
||
"depleteSoon": "Pronto se Agotará",
|
||
"clientUsage": "Obtener Uso",
|
||
"onlines": "Clientes en línea",
|
||
"commands": "Comandos",
|
||
"refresh": "🔄 Actualizar",
|
||
"clearIPs": "❌ Limpiar IPs",
|
||
"removeTGUser": "❌ Eliminar Usuario de Telegram",
|
||
"selectTGUser": "👤 Seleccionar Usuario de Telegram",
|
||
"selectOneTGUser": "👤 Selecciona un usuario de telegram:",
|
||
"resetTraffic": "📈 Reiniciar Tráfico",
|
||
"resetExpire": "📅 Cambiar fecha de Vencimiento",
|
||
"ipLog": "🔢 Registro de IP",
|
||
"ipLimit": "🔢 Límite de IP",
|
||
"setTGUser": "👤 Establecer Usuario de Telegram",
|
||
"toggle": "🔘 Habilitar / Deshabilitar",
|
||
"custom": "🔢 Costumbre",
|
||
"confirmNumber": "✅ Confirmar: {{ .Num }}",
|
||
"confirmNumberAdd": "✅ Confirmar agregando: {{ .Num }}",
|
||
"limitTraffic": "🚧 Límite de tráfico",
|
||
"getBanLogs": "Registros de prohibición",
|
||
"allClients": "Todos los Clientes",
|
||
"addClient": "Añadir cliente",
|
||
"submitDisable": "Enviar como deshabilitado ☑️",
|
||
"submitEnable": "Enviar como habilitado ✅",
|
||
"use_default": "🏷️ Usar por defecto",
|
||
"change_id": "⚙️🔑 ID",
|
||
"change_password": "⚙️🔑 Contraseña",
|
||
"change_email": "⚙️📧 Correo electrónico",
|
||
"change_comment": "⚙️💬 Comentario",
|
||
"change_flow": "⚙️🚦 Flujo",
|
||
"ResetAllTraffics": "Reiniciar todo el tráfico",
|
||
"SortedTrafficUsageReport": "Informe de uso de tráfico ordenado"
|
||
},
|
||
"answers": {
|
||
"successfulOperation": "✅ ¡Exitosa!",
|
||
"errorOperation": "❗ Error en la Operación.",
|
||
"getInboundsFailed": "❌ Error al obtener las entradas",
|
||
"getClientsFailed": "❌ No se pudo obtener los clientes.",
|
||
"canceled": "❌ {{ .Email }} : Operación cancelada.",
|
||
"clientRefreshSuccess": "✅ {{ .Email }} : Cliente actualizado exitosamente.",
|
||
"IpRefreshSuccess": "✅ {{ .Email }} : IPs actualizadas exitosamente.",
|
||
"TGIdRefreshSuccess": "✅ {{ .Email }} : Usuario de Telegram del cliente actualizado exitosamente.",
|
||
"resetTrafficSuccess": "✅ {{ .Email }} : Tráfico reiniciado exitosamente.",
|
||
"setTrafficLimitSuccess": "✅ {{ .Email }} : Límite de Tráfico guardado exitosamente.",
|
||
"expireResetSuccess": "✅ {{ .Email }} : Días de vencimiento reiniciados exitosamente.",
|
||
"resetIpSuccess": "✅ {{ .Email }} : Límite de IP {{ .Count }} guardado exitosamente.",
|
||
"clearIpSuccess": "✅ {{ .Email }} : IPs limpiadas exitosamente.",
|
||
"getIpLog": "✅ {{ .Email }} : Obtener Registro de IP.",
|
||
"getUserInfo": "✅ {{ .Email }} : Obtener Información de Usuario de Telegram.",
|
||
"removedTGUserSuccess": "✅ {{ .Email }} : Usuario de Telegram eliminado exitosamente.",
|
||
"enableSuccess": "✅ {{ .Email }} : Habilitado exitosamente.",
|
||
"disableSuccess": "✅ {{ .Email }} : Deshabilitado exitosamente.",
|
||
"askToAddUserId": "¡No se encuentra su configuración!\r\nPor favor, pídale a su administrador que use su ChatID de usuario de Telegram en su(s) configuración(es).\r\n\r\nSu ChatID de usuario: <code>{{ .TgUserID }}</code>",
|
||
"chooseClient": "Elige un Cliente para Inbound {{ .Inbound }}",
|
||
"chooseInbound": "Elige un Inbound"
|
||
}
|
||
}
|
||
} |