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
66 KiB
JSON
1092 lines
No EOL
66 KiB
JSON
{
|
||
"username": "ユーザー名",
|
||
"password": "パスワード",
|
||
"login": "ログイン",
|
||
"confirm": "確認",
|
||
"cancel": "キャンセル",
|
||
"close": "閉じる",
|
||
"save": "保存",
|
||
"logout": "ログアウト",
|
||
"create": "作成",
|
||
"update": "更新",
|
||
"copy": "コピー",
|
||
"copied": "コピー済み",
|
||
"download": "ダウンロード",
|
||
"remark": "備考",
|
||
"enable": "有効化",
|
||
"protocol": "プロトコル",
|
||
"search": "検索",
|
||
"filter": "フィルター",
|
||
"loading": "読み込み中...",
|
||
"refresh": "更新",
|
||
"clear": "クリア",
|
||
"second": "秒",
|
||
"minute": "分",
|
||
"hour": "時間",
|
||
"day": "日",
|
||
"check": "確認",
|
||
"indefinite": "無期限",
|
||
"unlimited": "無制限",
|
||
"none": "なし",
|
||
"qrCode": "QRコード",
|
||
"info": "詳細情報",
|
||
"edit": "編集",
|
||
"delete": "削除",
|
||
"reset": "リセット",
|
||
"noData": "データなし。",
|
||
"copySuccess": "コピー成功",
|
||
"sure": "確定",
|
||
"encryption": "暗号化",
|
||
"useIPv4ForHost": "ホストにIPv4を使用",
|
||
"transmission": "伝送",
|
||
"host": "ホスト",
|
||
"path": "パス",
|
||
"camouflage": "偽装",
|
||
"status": "ステータス",
|
||
"enabled": "有効",
|
||
"disabled": "無効",
|
||
"depleted": "消耗済み",
|
||
"depletingSoon": "間もなく消耗",
|
||
"offline": "オフライン",
|
||
"online": "オンライン",
|
||
"domainName": "ドメイン名",
|
||
"monitor": "監視",
|
||
"certificate": "証明書",
|
||
"fail": "失敗",
|
||
"comment": "コメント",
|
||
"success": "成功",
|
||
"lastOnline": "最終オンライン",
|
||
"getVersion": "バージョン取得",
|
||
"install": "インストール",
|
||
"clients": "クライアント",
|
||
"usage": "利用状況",
|
||
"twoFactorCode": "コード",
|
||
"remained": "残り",
|
||
"security": "セキュリティ",
|
||
"secAlertTitle": "セキュリティアラート",
|
||
"secAlertSsl": "この接続は安全ではありません。TLSを有効にしてデータ保護を行うまで、機密情報を入力しないでください。",
|
||
"secAlertConf": "一部の設定は脆弱です。潜在的な脆弱性を防ぐために、セキュリティプロトコルを強化することをお勧めします。",
|
||
"secAlertSSL": "セキュアな接続がありません。データ保護のためにTLS証明書をインストールしてください。",
|
||
"secAlertPanelPort": "デフォルトのポートにはセキュリティリスクがあります。ランダムなポートまたは特定のポートを設定してください。",
|
||
"secAlertPanelURI": "デフォルトのURIパスは安全ではありません。複雑なURIパスを設定してください。",
|
||
"secAlertSubURI": "サブスクリプションのデフォルトURIパスは安全ではありません。複雑なURIパスを設定してください。",
|
||
"secAlertSubJsonURI": "JSONサブスクリプションのデフォルトURIパスは安全ではありません。複雑なURIパスを設定してください。",
|
||
"emptyDnsDesc": "追加されたDNSサーバーはありません。",
|
||
"emptyFakeDnsDesc": "追加されたFake DNSサーバーはありません。",
|
||
"emptyBalancersDesc": "追加されたバランサーはありません。",
|
||
"emptyReverseDesc": "追加されたリバースプロキシはありません。",
|
||
"somethingWentWrong": "エラーが発生しました",
|
||
"subscription": {
|
||
"title": "サブスクリプション情報",
|
||
"subId": "サブスクリプションID",
|
||
"status": "ステータス",
|
||
"downloaded": "ダウンロード",
|
||
"uploaded": "アップロード",
|
||
"expiry": "有効期限",
|
||
"totalQuota": "合計クォータ",
|
||
"individualLinks": "個別リンク",
|
||
"active": "有効",
|
||
"inactive": "無効",
|
||
"unlimited": "無制限",
|
||
"noExpiry": "期限なし"
|
||
},
|
||
"menu": {
|
||
"theme": "テーマ",
|
||
"dark": "ダーク",
|
||
"ultraDark": "ウルトラダーク",
|
||
"dashboard": "ダッシュボード",
|
||
"inbounds": "インバウンド一覧",
|
||
"clients": "クライアント",
|
||
"nodes": "ノード",
|
||
"settings": "パネル設定",
|
||
"xray": "Xray設定",
|
||
"apiDocs": "API ドキュメント",
|
||
"logout": "ログアウト",
|
||
"link": "リンク管理"
|
||
},
|
||
"pages": {
|
||
"login": {
|
||
"hello": "こんにちは",
|
||
"title": "ようこそ",
|
||
"loginAgain": "ログインセッションが切れました。再度ログインしてください。",
|
||
"toasts": {
|
||
"invalidFormData": "データ形式エラー",
|
||
"emptyUsername": "ユーザー名を入力してください",
|
||
"emptyPassword": "パスワードを入力してください",
|
||
"wrongUsernameOrPassword": "ユーザー名、パスワード、または二段階認証コードが無効です。",
|
||
"successLogin": "アカウントに正常にログインしました。"
|
||
}
|
||
},
|
||
"index": {
|
||
"title": "システムステータス",
|
||
"cpu": "CPU",
|
||
"logicalProcessors": "論理プロセッサ",
|
||
"frequency": "周波数",
|
||
"swap": "スワップ",
|
||
"storage": "ストレージ",
|
||
"memory": "RAM",
|
||
"threads": "スレッド",
|
||
"xrayStatus": "Xray",
|
||
"stopXray": "停止",
|
||
"restartXray": "再起動",
|
||
"xraySwitch": "バージョン",
|
||
"xrayUpdates": "Xrayの更新",
|
||
"xraySwitchClick": "切り替えるバージョンを選択してください",
|
||
"xraySwitchClickDesk": "慎重に選択してください。古いバージョンは現在の設定と互換性がない可能性があります。",
|
||
"updatePanel": "パネルを更新",
|
||
"panelUpdateDesc": "これにより3X-UIが最新リリースに更新され、パネルサービスが再起動されます。",
|
||
"currentPanelVersion": "現在のパネルバージョン",
|
||
"latestPanelVersion": "最新のパネルバージョン",
|
||
"panelUpToDate": "パネルは最新です",
|
||
"upToDate": "最新",
|
||
"xrayStatusUnknown": "不明",
|
||
"xrayStatusRunning": "実行中",
|
||
"xrayStatusStop": "停止",
|
||
"xrayStatusError": "エラー",
|
||
"xrayErrorPopoverTitle": "Xrayの実行中にエラーが発生しました",
|
||
"operationHours": "システム稼働時間",
|
||
"systemHistoryTitle": "システム履歴",
|
||
"charts": "チャート",
|
||
"xrayMetricsTitle": "Xray メトリクス",
|
||
"xrayMetricsDisabled": "Xray メトリクスエンドポイントが設定されていません",
|
||
"xrayMetricsHint": "xray 設定にトップレベルの metrics ブロック(tag: metrics_out、listen: 127.0.0.1:11111)を追加し、xray を再起動してください。",
|
||
"xrayObservatoryEmpty": "Observatory データはまだありません",
|
||
"xrayObservatoryHint": "xray 設定に observatory ブロックを追加し、プローブする outbound タグを列挙してから xray を再起動してください。",
|
||
"xrayObservatoryTagPlaceholder": "Outbound を選択",
|
||
"xrayObservatoryAlive": "稼働中",
|
||
"xrayObservatoryDead": "停止",
|
||
"xrayObservatoryLastSeen": "最終確認",
|
||
"xrayObservatoryLastTry": "最終試行",
|
||
"trendLast2Min": "直近2分",
|
||
"systemLoad": "システム負荷",
|
||
"systemLoadDesc": "過去1、5、15分間のシステム平均負荷",
|
||
"connectionCount": "接続数",
|
||
"ipAddresses": "IPアドレス",
|
||
"toggleIpVisibility": "IPの表示を切り替える",
|
||
"overallSpeed": "全体の速度",
|
||
"upload": "アップロード",
|
||
"download": "ダウンロード",
|
||
"totalData": "総データ量",
|
||
"sent": "送信",
|
||
"received": "受信",
|
||
"documentation": "ドキュメント",
|
||
"xraySwitchVersionDialog": "Xrayのバージョンを本当に変更しますか？",
|
||
"xraySwitchVersionDialogDesc": "Xrayのバージョンが#version#に変更されます。",
|
||
"xraySwitchVersionPopover": "Xrayの更新が成功しました",
|
||
"panelUpdateDialog": "本当にパネルを更新しますか？",
|
||
"panelUpdateDialogDesc": "これにより3X-UIが#version#に更新され、パネルサービスが再起動されます。",
|
||
"panelUpdateCheckPopover": "パネルの更新確認に失敗しました",
|
||
"panelUpdateStartedPopover": "パネルの更新を開始しました",
|
||
"geofileUpdateDialog": "ジオファイルを本当に更新しますか？",
|
||
"geofileUpdateDialogDesc": "これにより#filename#ファイルが更新されます。",
|
||
"geofilesUpdateDialogDesc": "これにより、すべてのファイルが更新されます。",
|
||
"geofilesUpdateAll": "すべて更新",
|
||
"geofileUpdatePopover": "ジオファイルの更新が成功しました",
|
||
"customGeoTitle": "カスタム GeoSite / GeoIP",
|
||
"customGeoAdd": "追加",
|
||
"customGeoType": "種類",
|
||
"customGeoAlias": "エイリアス",
|
||
"customGeoUrl": "URL",
|
||
"customGeoEnabled": "有効",
|
||
"customGeoLastUpdated": "最終更新",
|
||
"customGeoExtColumn": "ルーティング (ext:…)",
|
||
"customGeoToastUpdateAll": "すべてのカスタムソースを更新しました",
|
||
"customGeoActions": "操作",
|
||
"customGeoEdit": "編集",
|
||
"customGeoDelete": "削除",
|
||
"customGeoDownload": "今すぐ更新",
|
||
"customGeoModalAdd": "カスタム geo を追加",
|
||
"customGeoModalEdit": "カスタム geo を編集",
|
||
"customGeoModalSave": "保存",
|
||
"customGeoDeleteConfirm": "このカスタム geo ソースを削除しますか？",
|
||
"customGeoRoutingHint": "ルーティングでは値を ext:ファイル.dat:タグ（タグを置換）として使います。",
|
||
"customGeoInvalidId": "無効なリソース ID",
|
||
"customGeoAliasesError": "カスタム geo エイリアスの読み込みに失敗しました",
|
||
"customGeoValidationAlias": "エイリアスは小文字・数字・- と _ のみ使用できます",
|
||
"customGeoValidationUrl": "URL は http:// または https:// で始めてください",
|
||
"customGeoAliasPlaceholder": "a-z 0-9 _ -",
|
||
"customGeoAliasLabelSuffix": "（カスタム）",
|
||
"customGeoToastList": "カスタム geo 一覧",
|
||
"customGeoToastAdd": "カスタム geo を追加",
|
||
"customGeoToastUpdate": "カスタム geo を更新",
|
||
"customGeoToastDelete": "カスタム geofile「{{ .fileName }}」を削除しました",
|
||
"customGeoToastDownload": "geofile「{{ .fileName }}」を更新しました",
|
||
"customGeoErrInvalidType": "種類は geosite または geoip である必要があります",
|
||
"customGeoErrAliasRequired": "エイリアスが必要です",
|
||
"customGeoErrAliasPattern": "エイリアスに使用できない文字が含まれています",
|
||
"customGeoErrAliasReserved": "このエイリアスは予約されています",
|
||
"customGeoErrUrlRequired": "URL が必要です",
|
||
"customGeoErrInvalidUrl": "URL が無効です",
|
||
"customGeoErrUrlScheme": "URL は http または https を使用してください",
|
||
"customGeoErrUrlHost": "URL のホストが無効です",
|
||
"customGeoErrDuplicateAlias": "この種類ですでにこのエイリアスが使われています",
|
||
"customGeoErrNotFound": "カスタム geo ソースが見つかりません",
|
||
"customGeoErrDownload": "ダウンロードに失敗しました",
|
||
"customGeoErrUpdateAllIncomplete": "カスタム geo ソースの 1 件以上を更新できませんでした",
|
||
"customGeoEmpty": "カスタム geo ソースはまだありません — 「追加」をクリックして作成してください",
|
||
"dontRefresh": "インストール中、このページをリロードしないでください",
|
||
"logs": "ログ",
|
||
"config": "設定",
|
||
"backup": "バックアップ",
|
||
"backupTitle": "バックアップと復元",
|
||
"exportDatabase": "バックアップ",
|
||
"exportDatabaseDesc": "クリックして、現在のデータベースのバックアップを含む .db ファイルをデバイスにダウンロードします。",
|
||
"importDatabase": "復元",
|
||
"importDatabaseDesc": "クリックして、デバイスから .db ファイルを選択し、アップロードしてバックアップからデータベースを復元します。",
|
||
"importDatabaseSuccess": "データベースのインポートに成功しました",
|
||
"importDatabaseError": "データベースのインポート中にエラーが発生しました",
|
||
"readDatabaseError": "データベースの読み取り中にエラーが発生しました",
|
||
"getDatabaseError": "データベースの取得中にエラーが発生しました",
|
||
"getConfigError": "設定ファイルの取得中にエラーが発生しました"
|
||
},
|
||
"inbounds": {
|
||
"title": "インバウンド一覧",
|
||
"totalDownUp": "総アップロード / ダウンロード",
|
||
"totalUsage": "総使用量",
|
||
"inboundCount": "インバウンド数",
|
||
"operate": "メニュー",
|
||
"enable": "有効化",
|
||
"remark": "備考",
|
||
"node": "ノード",
|
||
"deployTo": "デプロイ先",
|
||
"localPanel": "ローカルパネル",
|
||
"fallbacks": {
|
||
"title": "フォールバック",
|
||
"help": "このインバウンドへの接続がどのクライアントにも一致しない場合、別のインバウンドへルーティングします。下から子インバウンドを選ぶと、ルーティング項目（SNI / ALPN / Path / xver）はその子のトランスポートから自動的に埋められます — ほとんどの構成で追加の調整は不要です。各子インバウンドは 127.0.0.1 で security=none をリッスンする必要があります。",
|
||
"empty": "フォールバックはまだありません",
|
||
"add": "フォールバックを追加",
|
||
"pickInbound": "インバウンドを選択",
|
||
"matchAny": "任意",
|
||
"rederive": "子から再取得",
|
||
"rederived": "子から再取得しました",
|
||
"editAdvanced": "ルーティング項目を編集",
|
||
"hideAdvanced": "詳細を隠す",
|
||
"quickAddAll": "対象のインバウンドをすべて一括追加",
|
||
"quickAdded": "{n} 件のフォールバックを追加しました",
|
||
"quickAddedNone": "追加可能な新規インバウンドはありません",
|
||
"routesWhen": "次の条件でルーティング",
|
||
"defaultCatchAll": "デフォルト — その他すべてを捕捉"
|
||
},
|
||
"protocol": "プロトコル",
|
||
"port": "ポート",
|
||
"portMap": "ポートマッピング",
|
||
"traffic": "トラフィック",
|
||
"details": "詳細情報",
|
||
"transportConfig": "トランスポート設定",
|
||
"expireDate": "有効期限",
|
||
"createdAt": "作成",
|
||
"updatedAt": "更新",
|
||
"resetTraffic": "トラフィックリセット",
|
||
"addInbound": "インバウンド追加",
|
||
"generalActions": "一般操作",
|
||
"modifyInbound": "インバウンド修正",
|
||
"deleteInbound": "インバウンド削除",
|
||
"deleteInboundContent": "インバウンドを削除してもよろしいですか？",
|
||
"deleteClient": "クライアント削除",
|
||
"deleteClientContent": "クライアントを削除してもよろしいですか？",
|
||
"resetTrafficContent": "トラフィックをリセットしてもよろしいですか？",
|
||
"copyLink": "リンクをコピー",
|
||
"address": "アドレス",
|
||
"network": "ネットワーク",
|
||
"destinationPort": "宛先ポート",
|
||
"targetAddress": "宛先アドレス",
|
||
"monitorDesc": "空白にするとすべてのIPを監視",
|
||
"meansNoLimit": "= 無制限（単位：GB）",
|
||
"totalFlow": "総トラフィック",
|
||
"leaveBlankToNeverExpire": "空白にすると期限なし",
|
||
"noRecommendKeepDefault": "デフォルト値を保持することをお勧めします",
|
||
"certificatePath": "ファイルパス",
|
||
"certificateContent": "ファイル内容",
|
||
"publicKey": "公開鍵",
|
||
"privatekey": "秘密鍵",
|
||
"clickOnQRcode": "QRコードをクリックしてコピー",
|
||
"client": "クライアント",
|
||
"export": "リンクエクスポート",
|
||
"clone": "複製",
|
||
"cloneInbound": "複製",
|
||
"cloneInboundContent": "このインバウンドルールは、ポート（Port）、リスニングIP（Listening IP）、クライアント（Clients）を除くすべての設定がクローンされます",
|
||
"cloneInboundOk": "クローン作成",
|
||
"resetAllTraffic": "すべてのインバウンドトラフィックをリセット",
|
||
"resetAllTrafficTitle": "すべてのインバウンドトラフィックをリセット",
|
||
"resetAllTrafficContent": "すべてのインバウンドトラフィックをリセットしてもよろしいですか？",
|
||
"resetInboundClientTraffics": "クライアントトラフィックをリセット",
|
||
"resetInboundClientTrafficTitle": "すべてのクライアントトラフィックをリセット",
|
||
"resetInboundClientTrafficContent": "このインバウンドクライアントのすべてのトラフィックをリセットしてもよろしいですか？",
|
||
"resetAllClientTraffics": "すべてのクライアントトラフィックをリセット",
|
||
"resetAllClientTrafficTitle": "すべてのクライアントトラフィックをリセット",
|
||
"resetAllClientTrafficContent": "すべてのクライアントのトラフィックをリセットしてもよろしいですか？",
|
||
"delDepletedClients": "トラフィックが尽きたクライアントを削除",
|
||
"delDepletedClientsTitle": "トラフィックが尽きたクライアントを削除",
|
||
"delDepletedClientsContent": "トラフィックが尽きたすべてのクライアントを削除してもよろしいですか？",
|
||
"email": "メールアドレス",
|
||
"emailDesc": "メールアドレスは一意でなければなりません",
|
||
"IPLimit": "IP制限",
|
||
"IPLimitDesc": "設定値を超えるとインバウンドトラフィックが無効になります。（0 = 無効）",
|
||
"IPLimitlog": "IPログ",
|
||
"IPLimitlogDesc": "IP履歴ログ（無効なインバウンドトラフィックを有効にするには、ログをクリアしてください）",
|
||
"IPLimitlogclear": "ログをクリア",
|
||
"setDefaultCert": "パネル設定から証明書を設定",
|
||
"streamTab": "ストリーム",
|
||
"securityTab": "セキュリティ",
|
||
"sniffingTab": "スニッフィング",
|
||
"sniffingMetadataOnly": "メタデータのみ",
|
||
"sniffingRouteOnly": "ルーティングのみ",
|
||
"sniffingIpsExcluded": "除外する IP",
|
||
"sniffingDomainsExcluded": "除外するドメイン",
|
||
"decryption": "復号",
|
||
"encryption": "暗号化",
|
||
"vlessAuthX25519": "X25519 認証",
|
||
"vlessAuthMlkem768": "ML-KEM-768 認証",
|
||
"vlessAuthCustom": "カスタム",
|
||
"vlessAuthSelected": "選択中: {auth}",
|
||
"advanced": {
|
||
"title": "インバウンド JSON セクション",
|
||
"subtitle": "インバウンド全体の JSON と、settings、sniffing、streamSettings 用の専用エディター。",
|
||
"all": "すべて",
|
||
"allHelp": "すべてのフィールドを含むインバウンドオブジェクト全体を 1 つのエディターで編集します。",
|
||
"settings": "設定",
|
||
"settingsHelp": "Xray settings ブロックのラッパー:",
|
||
"sniffing": "スニッフィング",
|
||
"sniffingHelp": "Xray sniffing ブロックのラッパー:",
|
||
"stream": "ストリーム",
|
||
"streamHelp": "Xray stream ブロックのラッパー:",
|
||
"jsonErrorPrefix": "高度な JSON"
|
||
},
|
||
"telegramDesc": "TelegramチャットIDを提供してください。（ボットで'/id'コマンドを使用）または（{'@'}userinfobot）",
|
||
"subscriptionDesc": "サブスクリプションURLを見つけるには、“詳細情報”に移動してください。また、複数のクライアントに同じ名前を使用することができます。",
|
||
"info": "情報",
|
||
"same": "同じ",
|
||
"inboundData": "インバウンドデータ",
|
||
"exportInbound": "インバウンドルールをエクスポート",
|
||
"import": "インポート",
|
||
"importInbound": "インバウンドルールをインポート",
|
||
"periodicTrafficResetTitle": "トラフィックリセット",
|
||
"periodicTrafficResetDesc": "指定された間隔でトラフィックカウンタを自動的にリセット",
|
||
"lastReset": "最後のリセット",
|
||
"periodicTrafficReset": {
|
||
"never": "なし",
|
||
"daily": "毎日",
|
||
"weekly": "毎週",
|
||
"monthly": "毎月",
|
||
"hourly": "毎時"
|
||
},
|
||
"toasts": {
|
||
"obtain": "取得",
|
||
"updateSuccess": "更新が成功しました",
|
||
"logCleanSuccess": "ログがクリアされました",
|
||
"inboundsUpdateSuccess": "インバウンドが正常に更新されました",
|
||
"inboundUpdateSuccess": "インバウンドが正常に更新されました",
|
||
"inboundCreateSuccess": "インバウンドが正常に作成されました",
|
||
"inboundDeleteSuccess": "インバウンドが正常に削除されました",
|
||
"inboundClientAddSuccess": "インバウンドクライアントが追加されました",
|
||
"inboundClientDeleteSuccess": "インバウンドクライアントが削除されました",
|
||
"inboundClientUpdateSuccess": "インバウンドクライアントが更新されました",
|
||
"delDepletedClientsSuccess": "すべての枯渇したクライアントが削除されました",
|
||
"resetAllClientTrafficSuccess": "クライアントのすべてのトラフィックがリセットされました",
|
||
"resetAllTrafficSuccess": "すべてのトラフィックがリセットされました",
|
||
"resetInboundClientTrafficSuccess": "トラフィックがリセットされました",
|
||
"resetInboundTrafficSuccess": "受信トラフィックがリセットされました",
|
||
"trafficGetError": "トラフィックの取得中にエラーが発生しました",
|
||
"getNewX25519CertError": "X25519証明書の取得中にエラーが発生しました。",
|
||
"getNewmldsa65Error": "mldsa65証明書の取得中にエラーが発生しました。",
|
||
"getNewVlessEncError": "VlessEnc証明書の取得中にエラーが発生しました。"
|
||
},
|
||
"stream": {
|
||
"general": {
|
||
"request": "リクエスト",
|
||
"response": "レスポンス",
|
||
"name": "名前",
|
||
"value": "値"
|
||
},
|
||
"tcp": {
|
||
"version": "バージョン",
|
||
"method": "方法",
|
||
"path": "パス",
|
||
"status": "ステータス",
|
||
"statusDescription": "ステータス説明",
|
||
"requestHeader": "リクエストヘッダー",
|
||
"responseHeader": "レスポンスヘッダー"
|
||
}
|
||
}
|
||
},
|
||
"clients": {
|
||
"add": "クライアントを追加",
|
||
"edit": "クライアントを編集",
|
||
"submitAdd": "クライアントを追加",
|
||
"submitEdit": "変更を保存",
|
||
"clientCount": "クライアント数",
|
||
"bulk": "一括追加",
|
||
"copyFromInbound": "インバウンドからクライアントをコピー",
|
||
"copyToInbound": "コピー先",
|
||
"copySelected": "選択をコピー",
|
||
"copySource": "コピー元",
|
||
"copyEmailPreview": "生成されるメールのプレビュー",
|
||
"copySelectSourceFirst": "まずコピー元のインバウンドを選択してください。",
|
||
"copyResult": "コピー結果",
|
||
"copyResultSuccess": "コピーに成功しました",
|
||
"copyResultNone": "コピーする対象がありません。クライアントが選択されていないか、コピー元が空です",
|
||
"copyResultErrors": "コピーエラー",
|
||
"copyFlowLabel": "新規クライアントの Flow (VLESS)",
|
||
"copyFlowHint": "コピーされる全クライアントに適用されます。空欄でスキップします。",
|
||
"selectAll": "すべて選択",
|
||
"clearAll": "すべてクリア",
|
||
"method": "メソッド",
|
||
"first": "最初",
|
||
"last": "最後",
|
||
"ipLog": "IP ログ",
|
||
"prefix": "プレフィックス",
|
||
"postfix": "サフィックス",
|
||
"delayedStart": "初回使用から開始",
|
||
"expireDays": "期間",
|
||
"days": "日",
|
||
"renew": "自動更新",
|
||
"renewDesc": "有効期限切れ後に自動更新します。(0 = 無効) (単位: 日)",
|
||
"title": "クライアント",
|
||
"actions": "操作",
|
||
"totalGB": "送受信合計 (GB)",
|
||
"expiryTime": "有効期限",
|
||
"addClients": "クライアントを追加",
|
||
"limitIp": "IP 制限",
|
||
"password": "パスワード",
|
||
"subId": "サブスクリプション ID",
|
||
"online": "オンライン",
|
||
"email": "メール",
|
||
"comment": "コメント",
|
||
"traffic": "トラフィック",
|
||
"offline": "オフライン",
|
||
"addTitle": "クライアントを追加",
|
||
"qrCode": "QR コード",
|
||
"moreInformation": "詳細情報",
|
||
"delete": "削除",
|
||
"reset": "トラフィックをリセット",
|
||
"editTitle": "クライアントを編集",
|
||
"client": "クライアント",
|
||
"enabled": "有効",
|
||
"remaining": "残量",
|
||
"duration": "期間",
|
||
"attachedInbounds": "関連付けされたインバウンド",
|
||
"selectInbound": "1 つ以上のインバウンドを選択",
|
||
"noSubId": "このクライアントには subId がなく、共有可能なリンクはありません。",
|
||
"noLinks": "共有可能なリンクがありません — まずこのクライアントを対応するプロトコルのインバウンドに関連付けてください。",
|
||
"link": "リンク",
|
||
"resetNotPossible": "まずこのクライアントをインバウンドに関連付けてください。",
|
||
"general": "一般",
|
||
"resetAllTraffics": "すべてのクライアントのトラフィックをリセット",
|
||
"resetAllTrafficsTitle": "すべてのクライアントのトラフィックをリセットしますか?",
|
||
"resetAllTrafficsContent": "すべてのクライアントの送受信カウンターがゼロにリセットされます。クォータと有効期限には影響しません。元に戻せません。",
|
||
"empty": "クライアントはまだいません — 1 つ追加して始めましょう。",
|
||
"deleteConfirmTitle": "クライアント {email} を削除しますか?",
|
||
"deleteConfirmContent": "クライアントを関連付けされたすべてのインバウンドから削除し、トラフィック記録も破棄します。元に戻せません。",
|
||
"deleteSelected": "削除 ({count})",
|
||
"bulkDeleteConfirmTitle": "{count} 件のクライアントを削除しますか?",
|
||
"bulkDeleteConfirmContent": "選択された各クライアントを関連付けされたすべてのインバウンドから削除し、トラフィック記録も破棄します。元に戻せません。",
|
||
"delDepleted": "使い切ったクライアントを削除",
|
||
"delDepletedConfirmTitle": "使い切ったクライアントを削除しますか?",
|
||
"delDepletedConfirmContent": "トラフィック上限に達したか有効期限が切れたクライアントをすべて削除します。元に戻せません。",
|
||
"auth": "Auth",
|
||
"hysteriaAuth": "Auth (Hysteria)",
|
||
"uuid": "UUID",
|
||
"flow": "Flow",
|
||
"reverseTag": "Reverse tag",
|
||
"reverseTagPlaceholder": "任意の Reverse tag",
|
||
"telegramId": "Telegram ユーザー ID",
|
||
"telegramIdPlaceholder": "数値の Telegram ユーザー ID (0 = なし)",
|
||
"created": "作成日",
|
||
"updated": "更新日",
|
||
"ipLimit": "IP 制限",
|
||
"toasts": {
|
||
"deleted": "クライアントを削除しました",
|
||
"trafficReset": "トラフィックをリセットしました",
|
||
"allTrafficsReset": "すべてのクライアントのトラフィックをリセットしました",
|
||
"bulkDeleted": "{count} 件のクライアントを削除しました",
|
||
"bulkDeletedMixed": "{ok} 件削除、{failed} 件失敗",
|
||
"bulkCreated": "{count} 件のクライアントを作成しました",
|
||
"bulkCreatedMixed": "{ok} 件作成、{failed} 件失敗",
|
||
"delDepleted": "使い切った {count} 件のクライアントを削除しました"
|
||
}
|
||
},
|
||
"nodes": {
|
||
"title": "ノード",
|
||
"addNode": "ノードを追加",
|
||
"editNode": "ノードを編集",
|
||
"totalNodes": "ノード総数",
|
||
"onlineNodes": "オンライン",
|
||
"offlineNodes": "オフライン",
|
||
"avgLatency": "平均レイテンシ",
|
||
"name": "名前",
|
||
"namePlaceholder": "例: de-frankfurt-1",
|
||
"addressPlaceholder": "panel.example.com または 1.2.3.4",
|
||
"remark": "備考",
|
||
"scheme": "スキーム",
|
||
"address": "アドレス",
|
||
"port": "ポート",
|
||
"basePath": "ベースパス",
|
||
"apiToken": "APIトークン",
|
||
"apiTokenPlaceholder": "リモートパネルの設定ページから取得したトークン",
|
||
"apiTokenHint": "リモートパネルでは、設定 → APIトークン でAPIトークンを確認できます。",
|
||
"regenerate": "トークンを再生成",
|
||
"regenerateConfirm": "再生成すると現在のトークンは無効になります。これを使用しているすべての中央パネルは更新されるまでアクセスできなくなります。続行しますか？",
|
||
"allowPrivateAddress": "プライベートアドレスを許可",
|
||
"allowPrivateAddressHint": "プライベートネットワークまたはVPN上のノードにのみ有効にします。",
|
||
"enable": "有効",
|
||
"status": "ステータス",
|
||
"cpu": "CPU",
|
||
"mem": "メモリ",
|
||
"uptime": "稼働時間",
|
||
"latency": "レイテンシ",
|
||
"lastHeartbeat": "最後のハートビート",
|
||
"xrayVersion": "Xrayバージョン",
|
||
"panelVersion": "パネルのバージョン",
|
||
"actions": "操作",
|
||
"probe": "今すぐプローブ",
|
||
"testConnection": "接続テスト",
|
||
"connectionOk": "接続OK ({ms} ms)",
|
||
"connectionFailed": "接続に失敗しました",
|
||
"never": "なし",
|
||
"justNow": "たった今",
|
||
"deleteConfirmTitle": "ノード「{name}」を削除しますか？",
|
||
"deleteConfirmContent": "ノードの監視を停止します。リモートパネル自体には影響しません。",
|
||
"statusValues": {
|
||
"online": "オンライン",
|
||
"offline": "オフライン",
|
||
"unknown": "不明"
|
||
},
|
||
"toasts": {
|
||
"list": "ノードの読み込みに失敗しました",
|
||
"obtain": "ノードの読み込みに失敗しました",
|
||
"add": "ノードを追加",
|
||
"update": "ノードを更新",
|
||
"delete": "ノードを削除",
|
||
"deleted": "ノードを削除しました",
|
||
"test": "接続テスト",
|
||
"fillRequired": "名前、アドレス、ポート、APIトークンは必須です",
|
||
"probeFailed": "プローブに失敗しました"
|
||
}
|
||
},
|
||
"settings": {
|
||
"title": "パネル設定",
|
||
"save": "保存",
|
||
"infoDesc": "ここでのすべての変更は、保存してパネルを再起動する必要があります",
|
||
"restartPanel": "パネル再起動",
|
||
"restartPanelDesc": "パネルを再起動してもよろしいですか？再起動後にパネルにアクセスできない場合は、サーバーでパネルログを確認してください",
|
||
"restartPanelSuccess": "パネルの再起動に成功しました",
|
||
"actions": "操作",
|
||
"resetDefaultConfig": "デフォルト設定にリセット",
|
||
"panelSettings": "一般",
|
||
"securitySettings": "セキュリティ設定",
|
||
"TGBotSettings": "Telegramボット設定",
|
||
"panelListeningIP": "パネル監視IP",
|
||
"panelListeningIPDesc": "デフォルトではすべてのIPを監視する",
|
||
"panelListeningDomain": "パネル監視ドメイン",
|
||
"panelListeningDomainDesc": "デフォルトで空白の場合、すべてのドメインとIPアドレスを監視する",
|
||
"panelPort": "パネル監視ポート",
|
||
"panelPortDesc": "再起動で有効",
|
||
"publicKeyPath": "パネル証明書公開鍵ファイルパス",
|
||
"publicKeyPathDesc": "'/'で始まる絶対パスを入力",
|
||
"privateKeyPath": "パネル証明書秘密鍵ファイルパス",
|
||
"privateKeyPathDesc": "'/'で始まる絶対パスを入力",
|
||
"panelUrlPath": "パネルURLルートパス",
|
||
"panelUrlPathDesc": "'/'で始まり、'/'で終わる必要があります",
|
||
"pageSize": "ページサイズ",
|
||
"pageSizeDesc": "インバウンドテーブルのページサイズを定義します。0を設定すると無効化されます",
|
||
"remarkModel": "備考モデルと区切り記号",
|
||
"datepicker": "日付ピッカー",
|
||
"datepickerPlaceholder": "日付を選択",
|
||
"datepickerDescription": "日付選択カレンダーで有効期限を指定する",
|
||
"sampleRemark": "備考の例",
|
||
"oldUsername": "旧ユーザー名",
|
||
"currentPassword": "旧パスワード",
|
||
"newUsername": "新しいユーザー名",
|
||
"newPassword": "新しいパスワード",
|
||
"telegramBotEnable": "Telegramボットを有効にする",
|
||
"telegramBotEnableDesc": "Telegramボット機能を有効にする",
|
||
"telegramToken": "Telegramボットトークン",
|
||
"telegramTokenDesc": "'{'@'}BotFather'から取得したTelegramボットトークン",
|
||
"telegramProxy": "SOCKS5プロキシ",
|
||
"telegramProxyDesc": "SOCKS5プロキシを有効にしてTelegramに接続する（ガイドに従って設定を調整）",
|
||
"telegramAPIServer": "Telegram APIサーバー",
|
||
"telegramAPIServerDesc": "使用するTelegram APIサーバー。空白の場合はデフォルトサーバーを使用する",
|
||
"telegramChatId": "管理者チャットID",
|
||
"telegramChatIdDesc": "Telegram管理者チャットID（複数の場合はカンマで区切る）{'@'}userinfobotで取得するか、ボットで'/id'コマンドを使用して取得する",
|
||
"telegramNotifyTime": "通知時間",
|
||
"telegramNotifyTimeDesc": "定期的なTelegramボット通知時間を設定する（crontab時間形式を使用）",
|
||
"tgNotifyBackup": "データベースバックアップ",
|
||
"tgNotifyBackupDesc": "レポート付きのデータベースバックアップファイルを送信",
|
||
"tgNotifyLogin": "ログイン通知",
|
||
"tgNotifyLoginDesc": "誰かがパネルにログインしようとしたときに、ユーザー名、IPアドレス、時間を表示する",
|
||
"sessionMaxAge": "セッション期間",
|
||
"sessionMaxAgeDesc": "ログイン状態を保持する期間（単位：分）",
|
||
"expireTimeDiff": "有効期限通知のしきい値",
|
||
"expireTimeDiffDesc": "このしきい値に達した場合、有効期限に関する通知を受け取る（単位：日）",
|
||
"trafficDiff": "トラフィック消耗しきい値",
|
||
"trafficDiffDesc": "このしきい値に達した場合、トラフィック消耗に関する通知を受け取る（単位：GB）",
|
||
"tgNotifyCpu": "CPU負荷通知しきい値",
|
||
"tgNotifyCpuDesc": "CPU負荷がこのしきい値を超えた場合、通知を受け取る（単位：%）",
|
||
"timeZone": "タイムゾーン",
|
||
"timeZoneDesc": "定時タスクはこのタイムゾーンの時間に従って実行される",
|
||
"subSettings": "サブスクリプション設定",
|
||
"subEnable": "サブスクリプションサービスを有効にする",
|
||
"subEnableDesc": "サブスクリプションサービス機能を有効にする",
|
||
"subJsonEnable": "JSON サブスクリプションのエンドポイントを個別に有効/無効にする。",
|
||
"subTitle": "サブスクリプションタイトル",
|
||
"subTitleDesc": "VPNクライアントに表示されるタイトル",
|
||
"subSupportUrl": "サポートURL",
|
||
"subSupportUrlDesc": "VPNクライアントに表示されるテクニカルサポートへのリンク",
|
||
"subProfileUrl": "プロフィールURL",
|
||
"subProfileUrlDesc": "VPNクライアントに表示されるWebサイトへのリンク",
|
||
"subAnnounce": "お知らせ",
|
||
"subAnnounceDesc": "VPNクライアントに表示されるお知らせのテキスト",
|
||
"subEnableRouting": "ルーティングを有効化",
|
||
"subEnableRoutingDesc": "VPNクライアントでルーティングを有効にするためのグローバル設定。(Happのみ)",
|
||
"subRoutingRules": "ルーティングルール",
|
||
"subRoutingRulesDesc": "VPNクライアントのグローバルルーティングルール。(Happのみ)",
|
||
"subListen": "監視IP",
|
||
"subListenDesc": "サブスクリプションサービスが監視するIPアドレス（空白にするとすべてのIPを監視）",
|
||
"subPort": "監視ポート",
|
||
"subPortDesc": "サブスクリプションサービスが監視するポート番号（使用されていないポートである必要があります）",
|
||
"subCertPath": "公開鍵パス",
|
||
"subCertPathDesc": "サブスクリプションサービスで使用する公開鍵ファイルのパス（'/'で始まる）",
|
||
"subKeyPath": "秘密鍵パス",
|
||
"subKeyPathDesc": "サブスクリプションサービスで使用する秘密鍵ファイルのパス（'/'で始まる）",
|
||
"subPath": "URIパス",
|
||
"subPathDesc": "サブスクリプションサービスで使用するURIパス（'/'で始まり、'/'で終わる）",
|
||
"subDomain": "監視ドメイン",
|
||
"subDomainDesc": "サブスクリプションサービスが監視するドメイン（空白にするとすべてのドメインとIPを監視）",
|
||
"subUpdates": "更新間隔",
|
||
"subUpdatesDesc": "クライアントアプリケーションでサブスクリプションURLの更新間隔（単位：時間）",
|
||
"subEncrypt": "エンコード",
|
||
"subEncryptDesc": "サブスクリプションサービスが返す内容をBase64エンコードする",
|
||
"subShowInfo": "利用情報を表示",
|
||
"subShowInfoDesc": "クライアントアプリで残りのトラフィックと日付情報を表示する",
|
||
"subEmailInRemark": "名前にメールを含める",
|
||
"subEmailInRemarkDesc": "サブスクリプションプロファイル名にクライアントのメールアドレスを含めます。",
|
||
"subURI": "リバースプロキシURI",
|
||
"subURIDesc": "プロキシ後ろのサブスクリプションURLのURIパスに使用する",
|
||
"externalTrafficInformEnable": "外部トラフィック情報",
|
||
"externalTrafficInformEnableDesc": "トラフィックの更新ごとに外部 API に通知します。",
|
||
"externalTrafficInformURI": "外部トラフィック通知 URI",
|
||
"externalTrafficInformURIDesc": "トラフィックの更新ごとに外部 API に通知します。",
|
||
"restartXrayOnClientDisable": "自動無効化後に Xray を再起動",
|
||
"restartXrayOnClientDisableDesc": "有効期限切れまたはトラフィック上限でクライアントが自動的に無効化されたとき、Xray を再起動します。",
|
||
"fragment": "フラグメント",
|
||
"fragmentDesc": "TLS helloパケットのフラグメントを有効にする",
|
||
"fragmentSett": "設定",
|
||
"noisesDesc": "Noisesを有効にする",
|
||
"noisesSett": "Noises設定",
|
||
"mux": "マルチプレクサ",
|
||
"muxDesc": "確立されたストリーム内で複数の独立したストリームを伝送する",
|
||
"muxSett": "マルチプレクサ設定",
|
||
"direct": "直接接続",
|
||
"directDesc": "特定の国のドメインまたはIP範囲に直接接続する",
|
||
"notifications": "通知",
|
||
"certs": "証明書",
|
||
"externalTraffic": "外部トラフィック",
|
||
"dateAndTime": "日付と時刻",
|
||
"proxyAndServer": "プロキシとサーバー",
|
||
"intervals": "間隔",
|
||
"information": "情報",
|
||
"language": "言語",
|
||
"telegramBotLanguage": "Telegram Botの言語",
|
||
"security": {
|
||
"admin": "管理者の資格情報",
|
||
"twoFactor": "二段階認証",
|
||
"twoFactorEnable": "2FAを有効化",
|
||
"twoFactorEnableDesc": "セキュリティを強化するために追加の認証層を追加します。",
|
||
"twoFactorModalSetTitle": "二段階認証を有効にする",
|
||
"twoFactorModalDeleteTitle": "二段階認証を無効にする",
|
||
"twoFactorModalSteps": "二段階認証を設定するには、次の手順を実行してください:",
|
||
"twoFactorModalFirstStep": "1. 認証アプリでこのQRコードをスキャンするか、QRコード近くのトークンをコピーしてアプリに貼り付けます",
|
||
"twoFactorModalSecondStep": "2. アプリからコードを入力してください",
|
||
"twoFactorModalRemoveStep": "二段階認証を削除するには、アプリからコードを入力してください。",
|
||
"twoFactorModalChangeCredentialsTitle": "認証情報の変更",
|
||
"twoFactorModalChangeCredentialsStep": "管理者の認証情報を変更するには、アプリケーションからコードを入力してください。",
|
||
"twoFactorModalSetSuccess": "二要素認証が正常に設定されました",
|
||
"twoFactorModalDeleteSuccess": "二要素認証が正常に削除されました",
|
||
"twoFactorModalError": "コードが間違っています",
|
||
"show": "表示",
|
||
"hide": "非表示",
|
||
"apiTokenNew": "新規トークン",
|
||
"apiTokenName": "名前",
|
||
"apiTokenNamePlaceholder": "例: central-panel-a",
|
||
"apiTokenNameRequired": "名前は必須です",
|
||
"apiTokenEmpty": "トークンがまだありません — ボットやリモートパネルを認証するために作成してください。",
|
||
"apiTokenDeleteWarning": "このトークンを使用しているクライアントは直ちに認証できなくなります。"
|
||
},
|
||
"toasts": {
|
||
"modifySettings": "パラメーターが変更されました。",
|
||
"getSettings": "パラメーターの取得中にエラーが発生しました",
|
||
"modifyUserError": "管理者認証情報の変更中にエラーが発生しました。",
|
||
"modifyUser": "管理者の認証情報を正常に変更しました。",
|
||
"originalUserPassIncorrect": "旧ユーザー名または旧パスワードが間違っています",
|
||
"userPassMustBeNotEmpty": "新しいユーザー名と新しいパスワードは空にできません",
|
||
"getOutboundTrafficError": "送信トラフィックの取得エラー",
|
||
"resetOutboundTrafficError": "送信トラフィックのリセットエラー"
|
||
}
|
||
},
|
||
"xray": {
|
||
"title": "Xray 設定",
|
||
"save": "保存",
|
||
"restart": "Xray 再起動",
|
||
"restartSuccess": "Xrayの再起動に成功しました",
|
||
"stopSuccess": "Xrayが正常に停止しました",
|
||
"restartError": "Xrayの再起動中にエラーが発生しました。",
|
||
"stopError": "Xrayの停止中にエラーが発生しました。",
|
||
"basicTemplate": "基本設定",
|
||
"advancedTemplate": "高度な設定",
|
||
"generalConfigs": "一般設定",
|
||
"generalConfigsDesc": "これらのオプションは一般設定を決定します",
|
||
"logConfigs": "ログ",
|
||
"logConfigsDesc": "ログはサーバーのパフォーマンスに影響を与える可能性があるため、必要な場合にのみ有効にすることをお勧めします",
|
||
"blockConfigsDesc": "これらのオプションは、特定のプロトコルやウェブサイトへのユーザー接続をブロックします",
|
||
"basicRouting": "基本ルーティング",
|
||
"blockConnectionsConfigsDesc": "これらのオプションにより、特定のリクエスト元の国に基づいてトラフィックをブロックします。",
|
||
"directConnectionsConfigsDesc": "直接接続により、特定のトラフィックが他のサーバーを経由しないようにします。",
|
||
"blockips": "IPをブロック",
|
||
"blockdomains": "ドメインをブロック",
|
||
"directips": "直接IP",
|
||
"directdomains": "直接ドメイン",
|
||
"ipv4Routing": "IPv4 ルーティング",
|
||
"ipv4RoutingDesc": "このオプションはIPv4のみを介してターゲットドメインへルーティングします",
|
||
"warpRouting": "WARP ルーティング",
|
||
"warpRoutingDesc": "注意：これらのオプションを使用する前に、パネルのGitHubの手順に従って、サーバーにsocks5プロキシモードでWARPをインストールしてください。WARPはCloudflareサーバー経由でトラフィックをウェブサイトにルーティングします。",
|
||
"nordRouting": "NordVPN ルーティング",
|
||
"nordRoutingDesc": "これらのオプションはNordVPN経由で特定の宛先にトラフィックをルーティングします。",
|
||
"Template": "高度なXray設定テンプレート",
|
||
"TemplateDesc": "最終的なXray設定ファイルはこのテンプレートに基づいて生成されます",
|
||
"FreedomStrategy": "Freedom プロトコル戦略",
|
||
"FreedomStrategyDesc": "Freedomプロトコル内のネットワークの出力戦略を設定する",
|
||
"RoutingStrategy": "ルーティングドメイン戦略設定",
|
||
"RoutingStrategyDesc": "DNS解決の全体的なルーティング戦略を設定する",
|
||
"outboundTestUrl": "アウトバウンドテスト URL",
|
||
"outboundTestUrlDesc": "アウトバウンド接続テストに使用する URL。既定値",
|
||
"Torrent": "BitTorrent プロトコルをブロック",
|
||
"Inbounds": "インバウンドルール",
|
||
"InboundsDesc": "特定のクライアントからのトラフィックを受け入れる",
|
||
"Outbounds": "アウトバウンドルール",
|
||
"Balancers": "負荷分散",
|
||
"OutboundsDesc": "アウトバウンドトラフィックの送信方法を設定する",
|
||
"Routings": "ルーティングルール",
|
||
"RoutingsDesc": "各ルールの優先順位が重要です",
|
||
"completeTemplate": "すべて",
|
||
"logLevel": "ログレベル",
|
||
"logLevelDesc": "エラーログのレベルを指定し、記録する情報を示します",
|
||
"accessLog": "アクセスログ",
|
||
"accessLogDesc": "アクセスログのファイルパス。特殊値 'none' はアクセスログを無効にします",
|
||
"errorLog": "エラーログ",
|
||
"errorLogDesc": "エラーログのファイルパス。特殊値 'none' はエラーログを無効にします",
|
||
"dnsLog": "DNS ログ",
|
||
"dnsLogDesc": "DNSクエリのログを有効にするかどうか",
|
||
"maskAddress": "アドレスをマスク",
|
||
"maskAddressDesc": "IPアドレスをマスクし、有効にするとログに表示されるIPアドレスを自動的に置き換えます",
|
||
"statistics": "統計",
|
||
"statsInboundUplink": "インバウンドアップロード統計",
|
||
"statsInboundUplinkDesc": "すべてのインバウンドプロキシのアップストリームトラフィックの統計収集を有効にします。",
|
||
"statsInboundDownlink": "インバウンドダウンロード統計",
|
||
"statsInboundDownlinkDesc": "すべてのインバウンドプロキシのダウンストリームトラフィックの統計収集を有効にします。",
|
||
"statsOutboundUplink": "アウトバウンドアップロード統計",
|
||
"statsOutboundUplinkDesc": "すべてのアウトバウンドプロキシのアップストリームトラフィックの統計収集を有効にします。",
|
||
"statsOutboundDownlink": "アウトバウンドダウンロード統計",
|
||
"statsOutboundDownlinkDesc": "すべてのアウトバウンドプロキシのダウンストリームトラフィックの統計収集を有効にします。",
|
||
"rules": {
|
||
"first": "最初",
|
||
"last": "最後",
|
||
"up": "上へ",
|
||
"down": "下へ",
|
||
"source": "ソース",
|
||
"dest": "宛先アドレス",
|
||
"inbound": "インバウンド",
|
||
"outbound": "アウトバウンド",
|
||
"balancer": "負荷分散",
|
||
"info": "情報",
|
||
"add": "ルール追加",
|
||
"edit": "ルール編集",
|
||
"useComma": "カンマ区切りの項目"
|
||
},
|
||
"outbound": {
|
||
"addOutbound": "アウトバウンド追加",
|
||
"addReverse": "リバース追加",
|
||
"editOutbound": "アウトバウンド編集",
|
||
"editReverse": "リバース編集",
|
||
"reverseTag": "リバースタグ",
|
||
"reverseTagDesc": "VLESSシンプルリバースプロキシのアウトバウンドタグ。無効にするには空欄にしてください。",
|
||
"reverseTagPlaceholder": "アウトバウンドタグ（空欄で無効）",
|
||
"tag": "タグ",
|
||
"tagDesc": "一意のタグ",
|
||
"address": "アドレス",
|
||
"reverse": "リバース",
|
||
"domain": "ドメイン",
|
||
"type": "タイプ",
|
||
"bridge": "ブリッジ",
|
||
"portal": "ポータル",
|
||
"link": "リンク",
|
||
"intercon": "インターコネクション",
|
||
"settings": "設定",
|
||
"accountInfo": "アカウント情報",
|
||
"outboundStatus": "アウトバウンドステータス",
|
||
"sendThrough": "送信経路",
|
||
"test": "テスト",
|
||
"testResult": "テスト結果",
|
||
"testing": "接続をテスト中...",
|
||
"testSuccess": "テスト成功",
|
||
"testFailed": "テスト失敗",
|
||
"testError": "アウトバウンドのテストに失敗しました",
|
||
"nordvpn": "NordVPN",
|
||
"accessToken": "アクセストークン",
|
||
"country": "国",
|
||
"server": "サーバー",
|
||
"city": "都市",
|
||
"allCities": "すべての都市",
|
||
"privateKey": "秘密鍵",
|
||
"load": "負荷"
|
||
},
|
||
"balancer": {
|
||
"addBalancer": "負荷分散追加",
|
||
"editBalancer": "負荷分散編集",
|
||
"balancerStrategy": "戦略",
|
||
"balancerSelectors": "セレクター",
|
||
"tag": "タグ",
|
||
"tagDesc": "一意のタグ",
|
||
"balancerDesc": "balancerTagとoutboundTagは同時に使用できません。同時に使用された場合、outboundTagのみが有効になります。"
|
||
},
|
||
"wireguard": {
|
||
"secretKey": "シークレットキー",
|
||
"publicKey": "公開鍵",
|
||
"allowedIPs": "許可されたIP",
|
||
"endpoint": "エンドポイント",
|
||
"psk": "共有キー",
|
||
"domainStrategy": "ドメイン戦略"
|
||
},
|
||
"tun": {
|
||
"nameDesc": "TUN インターフェースの名前。デフォルトは 'xray0' です",
|
||
"mtuDesc": "最大伝送単位。データパケットの最大サイズ。デフォルトは 1500 です",
|
||
"userLevel": "ユーザーレベル",
|
||
"userLevelDesc": "このインバウンドを通じて確立されたすべての接続は、このユーザーレベルを使用します。デフォルトは 0 です"
|
||
},
|
||
"dns": {
|
||
"enable": "DNSを有効にする",
|
||
"enableDesc": "組み込みDNSサーバーを有効にする",
|
||
"tag": "DNSインバウンドタグ",
|
||
"tagDesc": "このタグはルーティングルールでインバウンドタグとして使用できます",
|
||
"clientIp": "クライアントIP",
|
||
"clientIpDesc": "DNSクエリ中に指定されたIPの位置をサーバーに通知するために使用されます",
|
||
"disableCache": "キャッシュを無効にする",
|
||
"disableCacheDesc": "DNSキャッシュを無効にします",
|
||
"disableFallback": "フォールバックを無効にする",
|
||
"disableFallbackDesc": "フォールバックDNSクエリを無効にします",
|
||
"disableFallbackIfMatch": "一致した場合にフォールバックを無効にする",
|
||
"disableFallbackIfMatchDesc": "DNSサーバーの一致するドメインリストにヒットした場合、フォールバックDNSクエリを無効にします",
|
||
"enableParallelQuery": "並列クエリを有効にする",
|
||
"enableParallelQueryDesc": "複数のサーバーへの並列DNSクエリを有効にして、より高速な解決を実現",
|
||
"strategy": "クエリ戦略",
|
||
"strategyDesc": "ドメイン名解決の全体的な戦略",
|
||
"add": "サーバー追加",
|
||
"edit": "サーバー編集",
|
||
"domains": "ドメイン",
|
||
"expectIPs": "期待されるIP",
|
||
"unexpectIPs": "予期しないIP",
|
||
"useSystemHosts": "システムのHostsを使用",
|
||
"useSystemHostsDesc": "インストール済みシステムのhostsファイルを使用する",
|
||
"serveStale": "期限切れキャッシュを使用",
|
||
"serveStaleDesc": "バックグラウンドで更新中に期限切れキャッシュ結果を返す",
|
||
"serveExpiredTTL": "期限切れTTL",
|
||
"serveExpiredTTLDesc": "期限切れキャッシュエントリの有効期間（秒）。0 = 無期限",
|
||
"timeoutMs": "タイムアウト (ms)",
|
||
"skipFallback": "フォールバックをスキップ",
|
||
"finalQuery": "最終クエリ",
|
||
"hosts": "Hosts",
|
||
"hostsAdd": "Host を追加",
|
||
"hostsEmpty": "Host が定義されていません",
|
||
"hostsDomain": "ドメイン (例: domain:example.com)",
|
||
"hostsValues": "IP またはドメイン — 入力して Enter",
|
||
"usePreset": "テンプレートを使用",
|
||
"dnsPresetTitle": "DNSテンプレート",
|
||
"dnsPresetFamily": "ファミリー",
|
||
"clearAll": "すべて削除",
|
||
"clearAllTitle": "すべての DNS サーバを削除しますか？",
|
||
"clearAllConfirm": "リストからすべての DNS サーバが削除されます。この操作は元に戻せません。"
|
||
},
|
||
"fakedns": {
|
||
"add": "フェイクDNS追加",
|
||
"edit": "フェイクDNS編集",
|
||
"ipPool": "IPプールサブネット",
|
||
"poolSize": "プールサイズ"
|
||
}
|
||
}
|
||
},
|
||
"tgbot": {
|
||
"keyboardClosed": "❌ キーボードを閉じました！",
|
||
"noResult": "❗ 結果がありません！",
|
||
"noQuery": "❌ クエリが見つかりません！コマンドを再利用してください！",
|
||
"wentWrong": "❌ 何かがうまくいかなかった！",
|
||
"noIpRecord": "❗ IPレコードがありません！",
|
||
"noInbounds": "❗ インバウンドが見つかりません！",
|
||
"unlimited": "♾ 無制限（リセット）",
|
||
"add": "追加",
|
||
"month": "月",
|
||
"months": "ヶ月",
|
||
"day": "日",
|
||
"days": "日間",
|
||
"hours": "時間",
|
||
"minutes": "分",
|
||
"unknown": "不明",
|
||
"inbounds": "インバウンド",
|
||
"clients": "クライアント",
|
||
"offline": "🔴 オフライン",
|
||
"online": "🟢 オンライン",
|
||
"commands": {
|
||
"unknown": "❗ 不明なコマンド",
|
||
"pleaseChoose": "👇 選択してください：\r\n",
|
||
"help": "🤖 このボットをご利用いただきありがとうございます！サーバーから特定のデータを提供し、必要な変更を行うことができます。\r\n\r\n",
|
||
"start": "👋 こんにちは、<i>{{ .Firstname }}</i>。\r\n",
|
||
"welcome": "🤖 <b>{{ .Hostname }}</b> 管理ボットへようこそ。\r\n",
|
||
"status": "✅ ボットは正常に動作しています！",
|
||
"usage": "❗ 検索するテキストを入力してください！",
|
||
"getID": "🆔 あなたのIDは：<code>{{ .ID }}</code>",
|
||
"helpAdminCommands": "Xray Coreを再起動するには：\r\n<code>/restart</code>\r\n\r\nクライアントの電子メールを検索するには：\r\n<code>/usage [電子メール]</code>\r\n\r\nインバウンド（クライアントの統計情報を含む）を検索するには：\r\n<code>/inbound [備考]</code>\r\n\r\nTelegramチャットID：\r\n<code>/id</code>",
|
||
"helpClientCommands": "統計情報を検索するには、次のコマンドを使用してください：\r\n<code>/usage [電子メール]</code>\r\n\r\nTelegramチャットID：\r\n<code>/id</code>",
|
||
"restartUsage": "\r\n\r\n<code>/restart</code>",
|
||
"restartSuccess": "✅ 操作成功！",
|
||
"restartFailed": "❗ 操作エラー。\r\n\r\n<code>エラー: {{ .Error }}</code>",
|
||
"xrayNotRunning": "❗ Xray Core は動作していません。",
|
||
"startDesc": "メインメニューを表示",
|
||
"helpDesc": "ボットのヘルプ",
|
||
"statusDesc": "ボットの状態を確認",
|
||
"idDesc": "Telegram IDを表示"
|
||
},
|
||
"messages": {
|
||
"cpuThreshold": "🔴 CPU使用率は{{ .Percent }}%、しきい値{{ .Threshold }}%を超えました",
|
||
"selectUserFailed": "❌ ユーザーの選択に失敗しました！",
|
||
"userSaved": "✅ Telegramユーザーが保存されました。",
|
||
"loginSuccess": "✅ パネルに正常にログインしました。\r\n",
|
||
"loginFailed": "❗️ パネルのログインに失敗しました。\r\n",
|
||
"2faFailed": "2FAエラー",
|
||
"report": "🕰 定期報告：{{ .RunTime }}\r\n",
|
||
"datetime": "⏰ 日時：{{ .DateTime }}\r\n",
|
||
"hostname": "💻 ホスト名：{{ .Hostname }}\r\n",
|
||
"version": "🚀 X-UI バージョン：{{ .Version }}\r\n",
|
||
"xrayVersion": "📡 Xray バージョン: {{ .XrayVersion }}\r\n",
|
||
"ipv6": "🌐 IPv6：{{ .IPv6 }}\r\n",
|
||
"ipv4": "🌐 IPv4：{{ .IPv4 }}\r\n",
|
||
"ip": "🌐 IP：{{ .IP }}\r\n",
|
||
"ips": "🔢 IPアドレス：\r\n{{ .IPs }}\r\n",
|
||
"serverUpTime": "⏳ サーバー稼働時間：{{ .UpTime }} {{ .Unit }}\r\n",
|
||
"serverLoad": "📈 サーバー負荷：{{ .Load1 }}, {{ .Load2 }}, {{ .Load3 }}\r\n",
|
||
"serverMemory": "📋 サーバーメモリ：{{ .Current }}/{{ .Total }}\r\n",
|
||
"tcpCount": "🔹 TCP接続数：{{ .Count }}\r\n",
|
||
"udpCount": "🔸 UDP接続数：{{ .Count }}\r\n",
|
||
"traffic": "🚦 トラフィック：{{ .Total }} (↑{{ .Upload }},↓{{ .Download }})\r\n",
|
||
"xrayStatus": "ℹ️ Xrayステータス：{{ .State }}\r\n",
|
||
"username": "👤 ユーザー名：{{ .Username }}\r\n",
|
||
"reason": "❗️ 理由：{{ .Reason }}\r\n",
|
||
"time": "⏰ 時間：{{ .Time }}\r\n",
|
||
"inbound": "📍 インバウンド：{{ .Remark }}\r\n",
|
||
"port": "🔌 ポート：{{ .Port }}\r\n",
|
||
"expire": "📅 有効期限：{{ .Time }}\r\n",
|
||
"expireIn": "📅 残り時間：{{ .Time }}\r\n",
|
||
"active": "💡 有効：{{ .Enable }}\r\n",
|
||
"enabled": "🚨 有効化済み：{{ .Enable }}\r\n",
|
||
"online": "🌐 接続ステータス：{{ .Status }}\r\n",
|
||
"lastOnline": "🔙 最終オンライン: {{ .Time }}\r\n",
|
||
"email": "📧 メール：{{ .Email }}\r\n",
|
||
"upload": "🔼 アップロード↑：{{ .Upload }}\r\n",
|
||
"download": "🔽 ダウンロード↓：{{ .Download }}\r\n",
|
||
"total": "📊 合計：{{ .UpDown }} / {{ .Total }}\r\n",
|
||
"TGUser": "👤 Telegramユーザー：{{ .TelegramID }}\r\n",
|
||
"exhaustedMsg": "🚨 消耗済みの {{ .Type }}：\r\n",
|
||
"exhaustedCount": "🚨 消耗済みの {{ .Type }} 数量：\r\n",
|
||
"onlinesCount": "🌐 オンラインクライアント：{{ .Count }}\r\n",
|
||
"disabled": "🛑 無効化：{{ .Disabled }}\r\n",
|
||
"depleteSoon": "🔜 間もなく消耗：{{ .Deplete }}\r\n\r\n",
|
||
"backupTime": "🗄 バックアップ時間：{{ .Time }}\r\n",
|
||
"refreshedOn": "\r\n📋🔄 更新時間：{{ .Time }}\r\n\r\n",
|
||
"yes": "✅ はい",
|
||
"no": "❌ いいえ",
|
||
"received_id": "🔑📥 IDが更新されました。",
|
||
"received_password": "🔑📥 パスワードが更新されました。",
|
||
"received_email": "📧📥 メールが更新されました。",
|
||
"received_comment": "💬📥 コメントが更新されました。",
|
||
"id_prompt": "🔑 デフォルトID: {{ .ClientId }}\n\nIDを入力してください。",
|
||
"pass_prompt": "🔑 デフォルトパスワード: {{ .ClientPassword }}\n\nパスワードを入力してください。",
|
||
"email_prompt": "📧 デフォルトメール: {{ .ClientEmail }}\n\nメールを入力してください。",
|
||
"comment_prompt": "💬 デフォルトコメント: {{ .ClientComment }}\n\nコメントを入力してください。",
|
||
"inbound_client_data_id": "🔄 インバウンド: {{ .InboundRemark }}\n\n🔑 ID: {{ .ClientId }}\n📧 メール: {{ .ClientEmail }}\n📊 トラフィック: {{ .ClientTraffic }}\n📅 有効期限: {{ .ClientExp }}\n🌐 IP制限: {{ .IpLimit }}\n💬 コメント: {{ .ClientComment }}\n\n今すぐこのクライアントをインバウンドに追加できます！",
|
||
"inbound_client_data_pass": "🔄 インバウンド: {{ .InboundRemark }}\n\n🔑 パスワード: {{ .ClientPass }}\n📧 メール: {{ .ClientEmail }}\n📊 トラフィック: {{ .ClientTraffic }}\n📅 有効期限: {{ .ClientExp }}\n🌐 IP制限: {{ .IpLimit }}\n💬 コメント: {{ .ClientComment }}\n\n今すぐこのクライアントをインバウンドに追加できます！",
|
||
"cancel": "❌ プロセスがキャンセルされました！\n\nいつでも /start で再開できます。 🔄",
|
||
"error_add_client": "⚠️ エラー:\n\n {{ .error }}",
|
||
"using_default_value": "わかりました、デフォルト値を使用します。 😊",
|
||
"incorrect_input": "入力が無効です。\nフレーズはスペースなしで続けて入力してください。\n正しい例: aaaaaa\n間違った例: aaa aaa 🚫",
|
||
"AreYouSure": "本当にいいですか？🤔",
|
||
"SuccessResetTraffic": "📧 メール: {{ .ClientEmail }}\n🏁 結果: ✅ 成功",
|
||
"FailedResetTraffic": "📧 メール: {{ .ClientEmail }}\n🏁 結果: ❌ 失敗 \n\n🛠️ エラー: [ {{ .ErrorMessage }} ]",
|
||
"FinishProcess": "🔚 すべてのクライアントのトラフィックリセットが完了しました。"
|
||
},
|
||
"buttons": {
|
||
"closeKeyboard": "❌ キーボードを閉じる",
|
||
"cancel": "❌ キャンセル",
|
||
"cancelReset": "❌ リセットをキャンセル",
|
||
"cancelIpLimit": "❌ IP制限をキャンセル",
|
||
"confirmResetTraffic": "✅ トラフィックをリセットしますか？",
|
||
"confirmClearIps": "✅ IPをクリアしますか？",
|
||
"confirmRemoveTGUser": "✅ Telegramユーザーを削除しますか？",
|
||
"confirmToggle": "✅ ユーザーを有効/無効にしますか？",
|
||
"dbBackup": "データベースバックアップを取得",
|
||
"serverUsage": "サーバーの使用状況",
|
||
"getInbounds": "インバウンド情報を取得",
|
||
"depleteSoon": "間もなく消耗",
|
||
"clientUsage": "使用状況を取得",
|
||
"onlines": "オンラインクライアント",
|
||
"commands": "コマンド",
|
||
"refresh": "🔄 更新",
|
||
"clearIPs": "❌ IPをクリア",
|
||
"removeTGUser": "❌ Telegramユーザーを削除",
|
||
"selectTGUser": "👤 Telegramユーザーを選択",
|
||
"selectOneTGUser": "👤 1人のTelegramユーザーを選択：",
|
||
"resetTraffic": "📈 トラフィックをリセット",
|
||
"resetExpire": "📅 有効期限を変更",
|
||
"ipLog": "🔢 IPログ",
|
||
"ipLimit": "🔢 IP制限",
|
||
"setTGUser": "👤 Telegramユーザーを設定",
|
||
"toggle": "🔘 有効/無効",
|
||
"custom": "🔢 カスタム",
|
||
"confirmNumber": "✅ 確認: {{ .Num }}",
|
||
"confirmNumberAdd": "✅ 追加を確認：{{ .Num }}",
|
||
"limitTraffic": "🚧 トラフィック制限",
|
||
"getBanLogs": "禁止ログ",
|
||
"allClients": "すべてのクライアント",
|
||
"addClient": "クライアントを追加",
|
||
"submitDisable": "無効として送信 ☑️",
|
||
"submitEnable": "有効として送信 ✅",
|
||
"use_default": "🏷️ デフォルトを使用",
|
||
"change_id": "⚙️🔑 ID",
|
||
"change_password": "⚙️🔑 パスワード",
|
||
"change_email": "⚙️📧 メールアドレス",
|
||
"change_comment": "⚙️💬 コメント",
|
||
"change_flow": "⚙️🚦 フロー",
|
||
"ResetAllTraffics": "すべてのトラフィックをリセット",
|
||
"SortedTrafficUsageReport": "ソートされたトラフィック使用レポート"
|
||
},
|
||
"answers": {
|
||
"successfulOperation": "✅ 成功！",
|
||
"errorOperation": "❗ 操作エラー。",
|
||
"getInboundsFailed": "❌ インバウンド情報の取得に失敗しました。",
|
||
"getClientsFailed": "❌ クライアントの取得に失敗しました。",
|
||
"canceled": "❌ {{ .Email }}：操作がキャンセルされました。",
|
||
"clientRefreshSuccess": "✅ {{ .Email }}：クライアントが正常に更新されました。",
|
||
"IpRefreshSuccess": "✅ {{ .Email }}：IPが正常に更新されました。",
|
||
"TGIdRefreshSuccess": "✅ {{ .Email }}：クライアントのTelegramユーザーが正常に更新されました。",
|
||
"resetTrafficSuccess": "✅ {{ .Email }}：トラフィックが正常にリセットされました。",
|
||
"setTrafficLimitSuccess": "✅ {{ .Email }}：トラフィック制限が正常に保存されました。",
|
||
"expireResetSuccess": "✅ {{ .Email }}：有効期限の日数が正常にリセットされました。",
|
||
"resetIpSuccess": "✅ {{ .Email }}：IP制限数が正常に保存されました：{{ .Count }}。",
|
||
"clearIpSuccess": "✅ {{ .Email }}：IPが正常にクリアされました。",
|
||
"getIpLog": "✅ {{ .Email }}：IPログの取得。",
|
||
"getUserInfo": "✅ {{ .Email }}：Telegramユーザー情報の取得。",
|
||
"removedTGUserSuccess": "✅ {{ .Email }}：Telegramユーザーが正常に削除されました。",
|
||
"enableSuccess": "✅ {{ .Email }}：正常に有効化されました。",
|
||
"disableSuccess": "✅ {{ .Email }}：正常に無効化されました。",
|
||
"askToAddUserId": "設定が見つかりませんでした！\r\n管理者に問い合わせて、設定にTelegramユーザーのChatIDを使用してください。\r\n\r\nあなたのユーザーChatID：<code>{{ .TgUserID }}</code>",
|
||
"chooseClient": "インバウンド {{ .Inbound }} のクライアントを選択",
|
||
"chooseInbound": "インバウンドを選択"
|
||
}
|
||
}
|
||
} |